From: Phillip Susi <psusi@cfl.rr.com>
To: tytso@mit.edu
Cc: Matthew Wilcox <matthew@wil.cx>,
linux-fsdevel@vger.kernel.org,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: unified page and buffer cache?
Date: Fri, 07 May 2010 20:54:41 -0400 [thread overview]
Message-ID: <1273280081.2444.5.camel@faldara> (raw)
In-Reply-To: <20100508004617.GF18762@thunk.org>
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?
On Fri, 2010-05-07 at 20:46 -0400, tytso@mit.edu wrote:
> Ext2 does use the page cache for directories. Ext3 and Ext4 access
> directories via buffer heads because of the journaling requirement.
>
> In *theory* they could be modified to use the page cache, given that
> we can do data journaling for files, and files live in the page cache
> --- however, for cases where the PAGE_SIZE > FS_BLOCKSIZE, which will
> happen if you are using 1k or 2k block filesystems, or on the Power
> Architecture or on the Itanic where the page size is 16k, updates to
> the directory will be much less efficient, since we journal changes to
> data files on page granularity and not buffer granuality.
>
> Furthermore, someone would have to supply me with the patches; it's
> pretty low on my priority list. And people on the Power and ia64
> platforms won't be happy....
>
> - Ted
next prev parent reply other threads:[~2010-05-08 0:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 15:51 readahead on directories Phillip Susi
2010-04-21 0:44 ` Jamie Lokier
2010-04-21 14:57 ` Phillip Susi
2010-04-21 16:12 ` Jamie Lokier
2010-04-21 18:10 ` Phillip Susi
2010-04-21 20:22 ` Jamie Lokier
2010-04-21 20:59 ` Phillip Susi
2010-04-21 22:06 ` Jamie Lokier
2010-04-22 7:01 ` Brad Boyer
2010-04-22 14:26 ` Phillip Susi
2010-04-22 17:53 ` Jamie Lokier
2010-04-22 19:23 ` Phillip Susi
2010-04-22 20:35 ` Jamie Lokier
2010-04-22 21:22 ` Phillip Susi
2010-04-22 22:43 ` Jamie Lokier
2010-04-23 4:13 ` Phillip Susi
2010-04-21 18:38 ` Evgeniy Polyakov
2010-04-21 18:51 ` Jamie Lokier
2010-04-21 18:56 ` Evgeniy Polyakov
2010-04-21 20:02 ` Jamie Lokier
2010-04-21 20:21 ` Evgeniy Polyakov
2010-04-21 20:39 ` Jamie Lokier
2010-04-21 19:23 ` Phillip Susi
2010-04-21 20:01 ` Jamie Lokier
2010-04-21 20:13 ` Phillip Susi
2010-04-21 20:37 ` Jamie Lokier
2010-05-07 13:38 ` unified page and buffer cache? (was: readahead on directories) Phillip Susi
2010-05-07 13:53 ` Matthew Wilcox
2010-05-07 15:45 ` unified page and buffer cache? Phillip Susi
2010-05-07 18:30 ` Matthew Wilcox
2010-05-08 0:50 ` Phillip Susi
2010-05-08 0:46 ` tytso
2010-05-08 0:54 ` Phillip Susi [this message]
2010-05-08 12:52 ` tytso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1273280081.2444.5.camel@faldara \
--to=psusi@cfl.rr.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.