Repair the `KSE' section text, and rewrap.

Pointed out by:	joe
This commit is contained in:
Chris Costello 2001-09-18 19:12:58 +00:00
parent 46cf75cb68
commit 023142875a
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=10738
2 changed files with 34 additions and 26 deletions

View file

@ -5,10 +5,11 @@
<year>2001</year> <year>2001</year>
</date> </date>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS"
<cvs:keyword name="freebsd"> version="1.0">
$FreeBSD$ <cvs:keyword name="freebsd">$FreeBSD:
</cvs:keyword> www/en/news/status/report-august-2001.xml,v 1.1 2001/09/18 18:46:30
chris Exp $</cvs:keyword>
</cvs:keywords> </cvs:keywords>
<section> <section>
@ -199,16 +200,19 @@
<body> <body>
<p>Work in adding supporting infrastructure to the kernel for KSE <p>Work in adding supporting infrastructure to the kernel for KSE
threading support has reached "milestone 2"</p> threading support has reached "milestone 2".</p>
<p>resources, in the way that it will need to when there are &gt; <p>We are awaiting commit permission for -current.</p>
1 threads per process, but the LOGICAL changes to such things as
the scheduler, and fork and exit, have not yet been made to allow <p>Milestone 2 is where the kernel source consistently refers to
more than one thread to be created. (nor have new threading its resources in terms of per-thread and per-process resources,
syscalls been added yet). This is an important milestone as it in the way that it will need to when there are &gt; 1 threads per
represents the last point where the kernel has only "mechanical" process, but the LOGICAL changes to such things as the scheduler,
changes. To go further we must start adding new algorythms and and fork and exit, have not yet been made to allow more than one
functions.</p> thread to be created. (nor have new threading syscalls been added
yet). This is an important milestone as it represents the last
point where the kernel has only "mechanical" changes. To go
further we must start adding new algorythms and functions.</p>
<p>The kernel for milestone 2 is reliable and has no noticable <p>The kernel for milestone 2 is reliable and has no noticable
performance degradations when compared to a matchung -current performance degradations when compared to a matchung -current

View file

@ -5,10 +5,11 @@
<year>2001</year> <year>2001</year>
</date> </date>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS"
<cvs:keyword name="freebsd"> version="1.0">
$FreeBSD$ <cvs:keyword name="freebsd">$FreeBSD:
</cvs:keyword> www/en/news/status/report-august-2001.xml,v 1.1 2001/09/18 18:46:30
chris Exp $</cvs:keyword>
</cvs:keywords> </cvs:keywords>
<section> <section>
@ -199,16 +200,19 @@
<body> <body>
<p>Work in adding supporting infrastructure to the kernel for KSE <p>Work in adding supporting infrastructure to the kernel for KSE
threading support has reached "milestone 2"</p> threading support has reached "milestone 2".</p>
<p>resources, in the way that it will need to when there are &gt; <p>We are awaiting commit permission for -current.</p>
1 threads per process, but the LOGICAL changes to such things as
the scheduler, and fork and exit, have not yet been made to allow <p>Milestone 2 is where the kernel source consistently refers to
more than one thread to be created. (nor have new threading its resources in terms of per-thread and per-process resources,
syscalls been added yet). This is an important milestone as it in the way that it will need to when there are &gt; 1 threads per
represents the last point where the kernel has only "mechanical" process, but the LOGICAL changes to such things as the scheduler,
changes. To go further we must start adding new algorythms and and fork and exit, have not yet been made to allow more than one
functions.</p> thread to be created. (nor have new threading syscalls been added
yet). This is an important milestone as it represents the last
point where the kernel has only "mechanical" changes. To go
further we must start adding new algorythms and functions.</p>
<p>The kernel for milestone 2 is reliable and has no noticable <p>The kernel for milestone 2 is reliable and has no noticable
performance degradations when compared to a matchung -current performance degradations when compared to a matchung -current