Date: Mon, 9 Sep 1996 10:38:08 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Terry Lambert <terry@lambert.org> Cc: hackers@freebsd.org Subject: Re: namei performance (was Re: FreeBSD vs. Linux 96 (my impressions)) Message-ID: <Pine.SV4.3.93.960909102057.12629B-100000@parkplace.cet.co.jp> In-Reply-To: <199609082205.PAA03751@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Sep 1996, Terry Lambert wrote: > The actual locking methodology that probaly wants to be used is seven > state: no lock, R (read), W (write), X (exclusive), IR (intention read), > IW, and IX. In the current code, the lock is an exclusive lock on the directory to prevent consistency problems. For example, VOP_CREAT on SYSV has to do a rescan of the directory because it doesn't lock the directory to ensure that the file didn't get created by someone else after the lookup was done. Could you walk thru this case with the above framework? Regards, Mike Hancock
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.93.960909102057.12629B-100000>