Update MPSAFE file system idea, assign to kib since he's had his hands
dirty in this area.
This commit is contained in:
parent
441902ff3b
commit
cf35958b44
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=35478
1 changed files with 17 additions and 3 deletions
|
@ -15,7 +15,7 @@ Ideas//EN"
|
|||
<ideas>
|
||||
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
|
||||
<cvs:keyword name="freebsd">
|
||||
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.142 2010/03/09 10:04:51 rwatson Exp $
|
||||
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.143 2010/03/09 10:54:26 rwatson Exp $
|
||||
</cvs:keyword>
|
||||
</cvs:keywords>
|
||||
|
||||
|
@ -202,9 +202,23 @@ these buses to be a subclass of this new base class.</p>
|
|||
<title>MPSAFE filesystem work</title>
|
||||
|
||||
<desc>
|
||||
<p><strong>Technical contact</strong>: <a href="mailto:kris@FreeBSD.org">Kris Kennaway</a></p>
|
||||
<p><strong>Technical contact</strong>: <a href="mailto:kib@FreeBSD.org">Konstantin Belousov</a></p>
|
||||
|
||||
<p>Take a filesystem and MPSAFE it. e.g. ext2fs, ntfs, coda, etc.</p>
|
||||
<p>FreeBSD 6.0 introduced an multi-processor scalable Virtual File
|
||||
System (VFS) Framework, allowing file systems to operate without the
|
||||
Giant lock. Many of the most commonly used file systems have been
|
||||
adapted to be MPSAFE (i.e., not reliant on Giant), such as UFS, the
|
||||
NFS client and server, UDF, cd9660, ZFS, and most recently the
|
||||
msdosfs (FAT) file system. However, in order to remove the
|
||||
compatibility shims permitting a file system to declare itself
|
||||
non-MPSAFE, all file systems must be converted. The list of
|
||||
remaining file systems includes ntfs, hpfs, coda, smbfs, and ncpfs.
|
||||
This project idea is to take one or more file systems and convert
|
||||
them to use their own locking, rather than relying on the Giant
|
||||
lock. In some cases, this requires also adapting underlying
|
||||
infrastructure: for example, smbfs relies on the netsmb RPC
|
||||
framework, and ncpfs on the netcp RPC framework, both of which will
|
||||
also require conversion.</p>
|
||||
</desc>
|
||||
</idea>
|
||||
|
||||
|
|
Loading…
Reference in a new issue