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

Pick a mid-point between Pittsburghification and rwatsonification.

Browse source
This commit is contained in:
Robert Watson 2004-11-12 17:56:50 +00:00
parent c30a735986
commit 3cc0fc6652
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=22933
1 changed files with 3 additions and 3 deletions

6
en/projects/netperf/index.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/projects/netperf/index.sgml,v 1.4 2004/11/12 11:56:56 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/projects/netperf/index.sgml,v 1.5 2004/11/12 16:04:43 trhodes Exp $">
<!ENTITY title "FreeBSD Network Performance Project (netperf)">
<!ENTITY email 'mux'>
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -58,8 +58,8 @@
into the kernel, reducing parallelism.</p></li>
<li><p>Optimize locking strategies to find better balances between
locking granularity and locking overhead. In the first cut with locking
work on the kernel, the goal was to adopt a medium-grained locking
locking granularity and locking overhead. In the first cut at locking
for the kernel, the goal was to adopt a medium-grained locking
approach based on data locking. This approach identifies critical
data structures, and inserts new locks and locking operations to
protect those data structures. Depending on the data model of the