Various wording fixes in the 5-roadmap article.

This commit is contained in:
Giorgos Keramidas 2007-09-17 21:03:49 +00:00
parent 5d39763ebb
commit b61a0d9b12
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=30797

View file

@ -114,7 +114,7 @@
The SMP status page at <ulink url="&url.base;/smp"></ulink>
provides a comprehensive breakdown
of the overall SMPng status. Status specific to SMPng progress in
device drivers can be found at at
device drivers can be found at
<ulink url="&url.base;/projects/busdma"></ulink>.
In summary:</para>
@ -224,7 +224,7 @@
ithreads, to servicing interrupts. With this, driver interrupt
service routines are allowed to block for mutexes, memory allocations,
etc. While this makes writing drivers easier, it introduces considerable
latency into the system due to the complete process context switch must
latency into the system due to the complete process context switch which must
be performed in order to service the ithread. This is aggravated by the
extensive coverage over the kernel by the Giant mutex, and often results
in multiple sleeps and context switches in order to service an interrupt.
@ -415,7 +415,7 @@
<para>The &t.releng.5 branch must offer users the same stability and
performance that is currently enjoyed in the &t.releng.4 branch.
While the goal of SMPng is to allow performance to far exceed what
is found in &t.releng.4; and its siblings BSD's, regaining performance
is found in &t.releng.4; and its sibling BSDs, regaining performance
to the basic level is of the utmost importance. The branch must also
be mature enough to avoid ABI and API changes while still allowing
potential problems to be resolved.</para>
@ -430,7 +430,7 @@
<itemizedlist>
<listitem>
<para>KSE: Both kernel and userland components must
reach the same level of functionality for all Tier-1 platforms
reach the same level of functionality for all Tier-1 platforms,
in both UP and SMP configurations. The definition of <quote>Tier-1
platforms</quote> can be found in
<ulink url="&url.articles.committers-guide;/archs.html"></ulink>.
@ -448,7 +448,7 @@
<para>busdma interface and drivers: architectures like PAE/&i386; and
sparc64 which do not have a direct mapping between host memory
address space and expansion bus address space require the
elimination for vtophys() and friends. The busdma interface was
elimination of vtophys() and friends. The busdma interface was
created to handle exactly this problem, but many drivers do not use
it yet. The busdma project at
<ulink url="&url.base;/projects/busdma"></ulink>
@ -466,7 +466,7 @@
leaving this task solely to the OS. &os; must gain the ability to
manage and allocate PCI memory resources on its own. Implementing
this should take into account cardbus, PCI-HotPlug, and laptop
dock station requirements. This feature will become increasingly
docking-station requirements. This feature will become increasingly
critical through the lifetime of &t.releng.5;, and therefore is a
requirement for the &t.releng.5; branch.</para>
</listitem>
@ -475,7 +475,7 @@
<sect2 id="performance">
<title>Performance</title>
<para>Performance hinges on the progress of SMPng infrastructure and
<para>Performance hinges on the progress of SMPng infrastructure in
the following areas:</para>
<itemizedlist>
@ -500,8 +500,8 @@
<listitem>
<para>Interrupt and context switching: As discussed above, interrupt
latency and context switching have a severe impact of performance.
Context switching for ithreads and kthreads must be improved on
platforms. New interrupt handling models that allow for faster
Context switching for ithreads and kthreads must be improved.
New interrupt handling models that allow for faster and
more flexible handling of both traditional and MSI interrupts must
be investigated and implemented.</para>
</listitem>
@ -552,7 +552,7 @@
<itemizedlist>
<listitem>
<para>NEWCARD/OLDCARD: The NEWCARD subsystem was made the default
for &os; 5.0. Unfortunately, it contains no support for
for &os;&nbsp;5.0. Unfortunately, it does not include support for
non-Cardbus bridges and falls victim to interrupt routing
problems on some laptops. The classic 16-bit bridge support,
OLDCARD, still exists and can be compiled in, but this is highly
@ -571,7 +571,7 @@
<listitem>
<para>New scheduler framework: The new scheduler framework is in
place, and users can select between the classic 44BSD scheduler
place, and users can select between the classic 4BSD scheduler
and the new ULE scheduler. A scheduler that demonstrates
processor affinity, HyperThreading and KSE awareness, and no
regressions in performance or interactivity characteristics must