linux-kernel - Re: unified page and buffer cache?

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] [day] [month] [year] [list]

Date:	Sat, 8 May 2010 08:52:15 -0400
From:	tytso@....edu
To:	Phillip Susi <psusi@....rr.com>
Cc:	Matthew Wilcox <matthew@....cx>, linux-fsdevel@...r.kernel.org,
	Linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: unified page and buffer cache?

On Fri, May 07, 2010 at 08:54:41PM -0400, Phillip Susi wrote:
> Would it be possible to somehow keep the current buffer heads, but
> associate them with the inode such that readahead() on the directory
> would work?

Maybe.   Try it and send patches.  :-)

As I said, it's not high on my priority list and I'm *way* behind on
all sorts of other, much higher priority tasks.  If you were going to
do the patches (which would have all sorts of complications since
you'd have to make sure directory pages didn't get written back via
the page write cache or via direct reclaim), I wouldn't reject them
out of hand since there are a few other advantages of doing things
that way....  

*However*, I suspect it would be easier for you to simply use the
FIEMAP ioctl had deal with directories separately from files.....

							- Ted
--
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/