Date: Wed, 10 Feb 2010 19:03:48 +0000 (UTC) From: Edward Tomasz Napierala <trasz@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r203762 - head/share/man/man9 Message-ID: <201002101903.o1AJ3mrc081155@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: trasz Date: Wed Feb 10 19:03:48 2010 New Revision: 203762 URL: http://svn.freebsd.org/changeset/base/203762 Log: Start sentences with a new line. Submitted by: brueffer Modified: head/share/man/man9/locking.9 Modified: head/share/man/man9/locking.9 ============================================================================== --- head/share/man/man9/locking.9 Wed Feb 10 18:56:49 2010 (r203761) +++ head/share/man/man9/locking.9 Wed Feb 10 19:03:48 2010 (r203762) @@ -152,7 +152,8 @@ Shared/exclusive locks are similar to re between them is that shared/exclusive locks may be held during unbounded sleep (and may thus perform an unbounded sleep). They are inherently less efficient than mutexes, reader/writer locks -and read-mostly locks. They don't support priority propagation. +and read-mostly locks. +They don't support priority propagation. They should be considered to be closely related to .Xr sleep 9 . In fact it could in some cases be @@ -192,9 +193,9 @@ Giant is an instance of a mutex, with so It is recursive. .It Drivers and filesystems can request that Giant be locked around them -by not marking themselves MPSAFE. Note that infrastructure to do this -is slowly going away as non-MPSAFE drivers either became properly locked -or disappear. +by not marking themselves MPSAFE. +Note that infrastructure to do this is slowly going away as non-MPSAFE +drivers either became properly locked or disappear. .It Giant must be locked first before other locks. .It
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201002101903.o1AJ3mrc081155>