Fix a few typos & improve syntax.
Translators can safely ignore most of this.
This commit is contained in:
parent
c32414d24e
commit
4be2b30f1a
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=16325
2 changed files with 10 additions and 10 deletions
|
|
@ -154,7 +154,7 @@
|
|||
use them to access Internet.</p>
|
||||
|
||||
<p>The Bluetooth sockets layer has been cleaned up. People should not
|
||||
see any WITNESS complains with new code. Locking issues have been
|
||||
see any WITNESS complaints with new code. Locking issues have been
|
||||
revisited and code in much better shape now, although it probably
|
||||
is not 100% SMP ready just yet. The code should work on SMP system
|
||||
anyway because sockets layer is still under Giant.</p>
|
||||
|
|
@ -325,7 +325,7 @@
|
|||
compatibility is unnecessary, this resulted in approx 1000
|
||||
lines less source code, the majority of which were removed
|
||||
from the device drivers. The new API for cdevsw is a lot simpler
|
||||
and hopefully less likely to confuse people. An ability to
|
||||
and hopefully less likely to confuse people. The ability to
|
||||
automatically allocate a device major number has been introduced
|
||||
and is already used by a handful of drivers. Checks introduced
|
||||
with this facility has shown that the uniqueness of manually
|
||||
|
|
@ -556,7 +556,7 @@
|
|||
protection.</p>
|
||||
|
||||
<p>There are a few areas of code that need to be protected and cleaned up
|
||||
before giant can be pushed down. Most notably the back-ground write
|
||||
before giant can be pushed down. Most notably the background write
|
||||
code is currently unsafe without giant. Also, many of the VM bits that
|
||||
the buffer cache relies on are not safe. This work has been done with
|
||||
the expectation that the VM and VFS subsystems will be giant free
|
||||
|
|
@ -578,7 +578,7 @@
|
|||
</contact>
|
||||
|
||||
<body>
|
||||
<p>The ULE scheduler has been commited to the 5.0-CURRENT branch. Early
|
||||
<p>The ULE scheduler has been committed to the 5.0-CURRENT branch. Early
|
||||
adopters and experimenters are welcome to try it and submit bug
|
||||
reports. It has shown noticable performance improvements over the old
|
||||
scheduler under some workloads. There are currently problems with
|
||||
|
|
@ -664,7 +664,7 @@
|
|||
on many short web connections. We also recently added support for larger
|
||||
sized starting congestion windows as described in RFC 3390. This helps
|
||||
short TCP connections as well as those with large round-trip delays,
|
||||
such as those over satellte links.</p>
|
||||
such as those over satellite links.</p>
|
||||
</body>
|
||||
</project>
|
||||
|
||||
|
|
|
|||
|
|
@ -154,7 +154,7 @@
|
|||
use them to access Internet.</p>
|
||||
|
||||
<p>The Bluetooth sockets layer has been cleaned up. People should not
|
||||
see any WITNESS complains with new code. Locking issues have been
|
||||
see any WITNESS complaints with new code. Locking issues have been
|
||||
revisited and code in much better shape now, although it probably
|
||||
is not 100% SMP ready just yet. The code should work on SMP system
|
||||
anyway because sockets layer is still under Giant.</p>
|
||||
|
|
@ -325,7 +325,7 @@
|
|||
compatibility is unnecessary, this resulted in approx 1000
|
||||
lines less source code, the majority of which were removed
|
||||
from the device drivers. The new API for cdevsw is a lot simpler
|
||||
and hopefully less likely to confuse people. An ability to
|
||||
and hopefully less likely to confuse people. The ability to
|
||||
automatically allocate a device major number has been introduced
|
||||
and is already used by a handful of drivers. Checks introduced
|
||||
with this facility has shown that the uniqueness of manually
|
||||
|
|
@ -556,7 +556,7 @@
|
|||
protection.</p>
|
||||
|
||||
<p>There are a few areas of code that need to be protected and cleaned up
|
||||
before giant can be pushed down. Most notably the back-ground write
|
||||
before giant can be pushed down. Most notably the background write
|
||||
code is currently unsafe without giant. Also, many of the VM bits that
|
||||
the buffer cache relies on are not safe. This work has been done with
|
||||
the expectation that the VM and VFS subsystems will be giant free
|
||||
|
|
@ -578,7 +578,7 @@
|
|||
</contact>
|
||||
|
||||
<body>
|
||||
<p>The ULE scheduler has been commited to the 5.0-CURRENT branch. Early
|
||||
<p>The ULE scheduler has been committed to the 5.0-CURRENT branch. Early
|
||||
adopters and experimenters are welcome to try it and submit bug
|
||||
reports. It has shown noticable performance improvements over the old
|
||||
scheduler under some workloads. There are currently problems with
|
||||
|
|
@ -664,7 +664,7 @@
|
|||
on many short web connections. We also recently added support for larger
|
||||
sized starting congestion windows as described in RFC 3390. This helps
|
||||
short TCP connections as well as those with large round-trip delays,
|
||||
such as those over satellte links.</p>
|
||||
such as those over satellite links.</p>
|
||||
</body>
|
||||
</project>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue