| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 9 Jun 2008 06:55:30 -0600 From: Matthew Wilcox <matthew@....cx> To: Maxim Shchetynin <maxim@...ux.vnet.ibm.com> Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: AZFS file system proposal On Mon, Jun 09, 2008 at 10:46:50AM +0200, Maxim Shchetynin wrote: > +config AZ_FS > + tristate "AZFS filesystem support" > + help > + Non-buffered filesystem for block devices with a gendisk and > + with direct_access() method in gendisk->fops. > + AZFS does not buffer outgoing traffic and is doing no read ahead. > + It supports mount options (given with -o) bs=x,uid=x,gid=x. > + If block-size (bs) is not specified AZFS uses block-size used > + by block device. Though mmap() method is available only if > + block-size equals to or is greater than system page size. This is a terrible description. I can't even suggest better wording because I don't understand it. The correct wording would not mention gendisks, fops or direct_access(). It would tell the user what they might use it for. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists