os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add hyperlinks from the agenda items to the sections of the transcript

Browse source 
that cover that topic.  Also clean up the HTML at places, and add more
markup.
This commit is contained in:
Murray Stokely 2002-08-16 07:27:20 +00:00
parent 924332b564
commit 4e845679ff
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=13898
1 changed files with 90 additions and 57 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

147
en/events/2002/usenix-devsummit.sgml
View file

@ -1,7 +1,8 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD$">
<!ENTITY date "$FreeBSD: www/en/events/2002/usenix-devsummit.sgml,v 1.1 2002/08/16 07:02:24 murray Exp $">
<!ENTITY email 'hackers'>
<!ENTITY break '<hr><center>BREAK</center><hr>'>
<!ENTITY title "Usenix 2002 FreeBSD Developer Summit III">
<!ENTITY stylesheet "&base;/events/events.css">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -29,17 +30,17 @@ Stokely</a>.</p>
<ul>
<li>Opening Comments</li>
<li>KSE</li>
<li><a href="#kse">KSE</a></li>
<li>Break</li>
<li>SMPng</li>
<li><a href="#smp">SMPng</a></li>
<li>PGP key signing</li>
<li>New Hardware Architectures</li>
<li><a href="#hw">New Hardware Architectures</a></li>
<li>Lunch</li>
<li>TrustedBSD</li>
<li>Release Engineering</li>
<li><a href="#trust">TrustedBSD</a></li>
<li><a href="#releng">Release Engineering</a></li>
<li>Break</li>
<li>RCng</li>
<li>Open Discussion</li>
<li><a href="#rc">RCng</a></li>
<li><a href="#open">Open Discussion</a></li>
</ul>
<p>NOTE: As usual I missed some names, please add those I missed.</p>
@ -93,6 +94,7 @@ Stokely</a>.</p>
<div class="topic">
<hr>
<a name="kse"></a>
<h2>KSE - Julian Elischer</h2>
<p>KSE has not changed much since the last summit (Feb). The major
@ -240,21 +242,26 @@ the Solaris ABI.</p>
<div class="topic">
<hr>
<a name="smp"></a>
<h2>SMPng - John Baldwin</h2>
<p><strong class="speaker">JB</strong> : Yesterday we talked about SMP related things so I'll give a summary
and then give a list of things for 5.0.
<div class="discussion">
<p><strong class="speaker">JB</strong> : The big thing for 5.0 is to get the network stack out from under
Giant.
<p><strong class="speaker">JB</strong> : Yesterday we talked about SMP
related things so I'll give a summary and then give a list of things
for 5.0.</p>
<p><strong class="speaker">JB</strong> : Jefferey Xu and Jennifer Ying were here to talk about this. They
have the PCBs checked in now.
<p><strong class="speaker">JB</strong> : The big thing for 5.0 is to
get the network stack out from under Giant.</p>
<p><strong class="speaker">JY</strong> : Interface Queues and SynCache might be done.
<p><strong class="speaker">JB</strong> : Jefferey Xu and Jennifer Ying
were here to talk about this. They have the PCBs checked in now.</p>
<p><strong class="speaker">JY</strong> : Interface Queues and SynCache
might be done.</p>
</div>
<p>The remaining chunks of the network code are:</p>
<hr>
<ul>
<li>Routing Table Locking</li>
@ -266,6 +273,8 @@ have the PCBs checked in now.
<li>Netgraph</li>
</ul>
<div class="discussion">
<p><strong class="speaker">JB</strong> : Aside from network the newbus
locking needs to be done (Warner Losh) and also CAM stuff. No known
status on CAM. Perhaps CAM is not needed for 5.0</p>
@ -286,64 +295,78 @@ memory is a socket its a socket forever, this is no longer true.</p>
5.0 and have decided to stop adding features so that we can start
clean up 5.0 and make it a real release. This might require hacks.</p>
<p><strong class="speaker">RW</strong> : For example in the UMA case there could be a flag to just say
"don't reclaim this zone" -- this would help with issues such as the
socket code assuming memory is type stable.
<p><strong class="speaker">RW</strong> : For example in the UMA case
there could be a flag to just say "don't reclaim this zone" -- this
would help with issues such as the socket code assuming memory is type
stable.</p>
Over to AC on the VM system. Nothing to say.
<p>Over to AC on the VM system. Nothing to say.</p>
<p><strong class="speaker">BM</strong> : As much as I might get hated for this. Will preemption stuff
go away by 5.0?
<p><strong class="speaker">BM</strong> : As much as I might get hated
for this. Will preemption stuff go away by 5.0?</p>
<p><strong class="speaker">JB</strong> :No, that's a 6.0 thing. There are things to do first.
<p><strong class="speaker">JB</strong> :No, that's a 6.0 thing. There
are things to do first.</p>
<p><strong class="speaker">??? Phone</strong> : Could this come in in the life time of 5.? 5.1?
<p><strong class="speaker">??? Phone</strong> : Could this come in in
the life time of 5.? 5.1?</p>
<p><strong class="speaker">RW</strong> : This is a release issue really.
<p><strong class="speaker">RW</strong> : This is a release issue really.</p>
<p><strong class="speaker">JB</strong> : Yes, the kernel is pre-emptive.
<p><strong class="speaker">JB</strong> : Yes, the kernel is pre-emptive.</p>
<p><strong class="speaker">RW</strong> : Perhaps we should talk about is performance goals? What are the
comparisons to make? Perhaps head of 4 with head of 5. We'll see a
mix.
<p><strong class="speaker">RW</strong> : Perhaps we should talk about
is performance goals? What are the comparisons to make? Perhaps head
of 4 with head of 5. We'll see a mix.</p>
<p><strong class="speaker">JB</strong> : I need to run benchmarks.
<p><strong class="speaker">JB</strong> : I need to run benchmarks.</p>
<p><strong class="speaker">RW</strong> : In terms of SMP features when will VM be ready to be measured? I
can't put a date on it.
<p><strong class="speaker">RW</strong> : In terms of SMP features when
will VM be ready to be measured? I can't put a date on it.</p>
<p><strong class="speaker">AC</strong> : I think I told John was in time for release. I'm already doing
performance testing so we've already started.
<p><strong class="speaker">AC</strong> : I think I told John was in
time for release. I'm already doing performance testing so we've
already started.</p>
<p><strong class="speaker">RW</strong> : We'll pick a date to start doing measurements. Perhaps 2 or 3
weeks from now.
<p><strong class="speaker">RW</strong> : We'll pick a date to start
doing measurements. Perhaps 2 or 3 weeks from now.</p>
<p><strong class="speaker">AC</strong> : My guess is the the locking pmap is going to take some time to
shake out. On the other hand the next major module we should be
working on is machine dependent level. Last we should try approaching
the vmobject level. I'll start worrying about performance in the near
term.
<p><strong class="speaker">AC</strong> : My guess is the the locking
pmap is going to take some time to shake out. On the other hand the
next major module we should be working on is machine dependent level.
Last we should try approaching the vmobject level. I'll start
worrying about performance in the near term.</p>
<p><strong class="speaker">RW</strong> : Will threading improve latency or throughput for networking?
<p><strong class="speaker">RW</strong> : Will threading improve
latency or throughput for networking?</p>
<p><strong class="speaker">BM</strong> : I would like if we could actually start before.
<p><strong class="speaker">BM</strong> : I would like if we could
actually start before.</p>
<p><strong class="speaker">RW</strong> : Do you have a timeline for the interrupt threading stuff?
<p><strong class="speaker">RW</strong> : Do you have a timeline for
the interrupt threading stuff?</p>
<p><strong class="speaker">BM</strong> : I finished some things last night but there are still issues.
In a couple of weeks it should be ready for first commit.
<p><strong class="speaker">BM</strong> : I finished some things last
night but there are still issues. In a couple of weeks it should be
ready for first commit.</p>
<p><strong class="speaker">RW</strong> : Informally beginning to measure performance now. What are the
right sets of tests? Need to discuss on -arch.
<p><strong class="speaker">RW</strong> : Informally beginning to
measure performance now. What are the right sets of tests? Need to
discuss on -arch.</p>
<p><strong class="speaker">AC</strong> : It would be nice to have that committed to the tools directory.
<p><strong class="speaker">AC</strong> : It would be nice to have that
committed to the tools directory.</p>
<p><strong class="speaker">JB</strong> : The statistics analysis package are we using.
<p><strong class="speaker">JB</strong> : The statistics analysis
package are we using.</p>
<p><strong class="speaker">BM</strong> : I have some good success with netpipe for overall measurement.
<p><strong class="speaker">BM</strong> : I have some good success with
netpipe for overall measurement.</p>
<p><strong class="speaker">RW</strong> : Need to be using consistent compilers because of the compiler
change. Also all our debugging stuff will slow down the benchmarking.
<p><strong class="speaker">RW</strong> : Need to be using consistent
compilers because of the compiler change. Also all our debugging
stuff will slow down the benchmarking.</p>
</div>
<p>Benchmark Ideas</p>
<ul>
@ -376,6 +399,8 @@ change. Also all our debugging stuff will slow down the benchmarking.
<li>slow/fast CPU</li>
</ul>
<div class="discussion">
<p><strong class="speaker">MD</strong> : Debug stuff on 5.0. I think
it might be reasonable then to take the space hit and always have the
debugging in but turn it on and off with sysctl.</p>
@ -383,10 +408,11 @@ debugging in but turn it on and off with sysctl.</p>
<p><strong class="speaker">RW</strong> : We should commit an optimized
kernel configuration and benchmarking guidlines to the tree as
well.</p>
</div>
<hr>
BREAK
<hr>
&break;
<div class="discussion">
<p><strong class="speaker">RW</strong> : I think we should continue
the performance discussion. We want to accomplish a couple of things.
@ -468,9 +494,11 @@ the project though.</p>
<p><strong class="speaker">RW</strong> : I will set up the mailing list.</p>
</div>
</div>
<div class="topic">
<hr>
<a name="hw"></a>
<h2>New Hardware Architectures</h2>
<h3>Alpha</h3>
@ -629,7 +657,7 @@ LUNCH
<div class="topic">
<hr>
<a name="arch"></a>
<a name="trust"></a>
<h2>Trusted BSD</h2>
<p><strong class="speaker">RW</strong> : MAC framework is what is of
@ -675,6 +703,7 @@ stuff that's not done yet.</p>
<div class="topic">
<hr>
<a name="releng"></a>
<h2>Release Engineering</h2>
<p><strong class="speaker">MS</strong> : Shows a slide of releases.
@ -890,8 +919,11 @@ come release.</p>
</div>
</div>
&break;
<div class="topic">
<hr>
<a name="rc"></a>
<h2>rc.d</h2>
</div>
@ -960,6 +992,7 @@ system.</p>
<div class="topic">
<hr>
<a name="open"></a>
<h2>Other Issues</h2>
</div>