Date: Sat, 08 Oct 2011 11:57:58 +0200 From: Josh Paetzel <jpaetzel@freebsd.org> To: freebsd-arch@freebsd.org Subject: Re: Call to arms: MPSAFE file systems Message-ID: <4E901EA6.30808@freebsd.org> In-Reply-To: <alpine.BSF.2.00.1109121156400.62958@fledge.watson.org> References: <CAJ-FndCwwtbZBZJoZwEmrcrPfooXp15g-yX8-urqJUXnH%2BT1cw@mail.gmail.com> <alpine.BSF.2.00.1109121156400.62958@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/12/11 13:08, Robert Watson wrote: > > On Sat, 27 Aug 2011, Attilio Rao wrote: > >> With the aid of kib and rwatson I made a roughly outlined plan about >> what is left to do in order to have all the filesystems locked (or >> eventually dropped) before 10.0) and is summarized here: >> http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS > > Here's a more succinct summary of the key points from the wiki: > > FreeBSD has supported Giant lock-free file systems for years, and > almost all file systems have been shipping "MPSAFE" for several > years. However, VFS retains compatibility support for non-MPSAFE file > systems. We want to remove that compatibility support, as it adds > non-trivial complexity to an already quite complex VFS, simplifying > the code and making it easier to maintain and enhance. This means > either fixing or removing any file systems that can't operate without > compatibility support. > > Attilio has posted a schedule for the removal of compatibility > crutches, which in turn means removing any un-updated file systems. > We are looking for volunteers to perform those updates. Here's the > schedule: > > 27 August 2011 Attilio posts plan on arch@ > 1 October 2011 Add VFS_GIANT_COMPATIBILITY option (enabled) > 1 March 2012 Disable VFS_GIANT_COMPATIBILITY option by default > 1 September 2012 Disconnect non-MPSAFE file systems from build > 1 March 2013 Garbage collect any un-updated file systems > > Most of our critical file systems are already done: UFS, ZFS, the NFS > client and server (both old and new), unionfs, pseudofs, tmpfs, > nullfs, devfs, cd9660, ext2fs, fdescfs, msdosfs, udf, and procfs. > > However, some remain, and they require owners: > > File system Owner State > coda rwatson Non-MPSAFE > hpfs ??? Non-MPSAFE > ntfs attilio Non-MPSAFE > nwfs ??? Non-MPSAFE > portalfs ??? Non-MPSAFE > smbfs ??? Non-MPSAFE > reiserfs ??? Non-MPSAFE > xfs ??? Non-MPSAFE > > Any file system that remains on this list will be removed by 10.0 -- > so, if you care about one of the above file systems, please help us > get them updated. You can find more information here, including on the > methodology for making a file system MPSAFE, with worked examples: > > http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS > > Robert > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" Robert, As we discussed yesterday if you can facilitate a code drop of smbfs I'll shepherd it into the tree. -- Thanks, Josh Paetzel FreeBSD -- The power to serve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E901EA6.30808>