Date: Sat, 27 Aug 2011 14:45:20 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: "Robert N. M. Watson" <rwatson@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: Removing Giant from VFS in 10.0 (was: Re: skipping locks, mutex_owned, usb) Message-ID: <alpine.GSO.1.10.1108271443220.1411@multics.mit.edu> In-Reply-To: <DBD3B7B0-0172-4941-956F-BF210810A6A4@freebsd.org> References: <4E53986B.5000804@FreeBSD.org> <201108230911.09021.jhb@freebsd.org> <4E564F15.3010809@FreeBSD.org> <201108250945.24606.jhb@freebsd.org> <4e576127.Suqlhieb0FMDx8cB%perryh@pluto.rain.com> <alpine.BSF.2.00.1108261007110.48200@fledge.watson.org> <alpine.GSO.1.10.1108262140240.1411@multics.mit.edu> <DBD3B7B0-0172-4941-956F-BF210810A6A4@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 27 Aug 2011, Robert N. M. Watson wrote: > > On 27 Aug 2011, at 02:43, Benjamin Kaduk wrote: > >> >> For what it's worth, OpenAFS already passes MNTK_MPSAFE /* solid steel */, with what I expect is nearly-correct locking. > > Excellent! > > (Although I guess OpenAFS internally has the moral equivalent of a Giant > lock that protects its own structures, but that's an entirely > independent problem that the OpenAFS community is already interested > in?) This is true. Though it may not actually be feasible to tackle until better integration with a lock-tracking framework such as WITNESS or Linux's (GPL-only) lock debugging framework. -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1108271443220.1411>