linux-kernel - Re: AZFS file system proposal

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080617144526.GA28448@logfs.org>
Date:	Tue, 17 Jun 2008 16:45:26 +0200
From:	Jörn Engel <joern@...fs.org>
To:	Maxim Shchetynin <maxim@...ux.vnet.ibm.com>
Cc:	linux-fsdevel@...r.kernel.org, Jan Engelhardt <jengelh@...ozas.de>,
	Matthew Wilcox <matthew@....cx>, linux-kernel@...r.kernel.org
Subject: Re: AZFS file system proposal

On Tue, 17 June 2008 16:06:28 +0200, Maxim Shchetynin wrote:
> > 
> > My personal question when looking at this is: Why not use ext2?  It
> 
> Same reason we don't use ext2 for file system in RAM - we don't need any expensive caching and readahead mechanisms for devices which are as fast as main memory (or almost as fast).

Well, with the '-o xip' option I mentioned below, there is no caching or
readahead.  The direct_access method you use as well was developed for
ext2.  Or rather for xip2fs, another new filesystem.  After some review,
that was shot down and a mount option was added to ext2 instead.

> > appears to me that an ext2 mounted with '-o xip' would solve the same
> > problems.

Jörn

-- 
Homo Sapiens is a goal, not a description.
-- unknown
--
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/