From: Nick Piggin <npiggin@suse.de>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, linux-arch@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: Should PAGE_CACHE_SIZE be discarded?
Date: Wed, 14 Nov 2007 22:35:43 +0100 [thread overview]
Message-ID: <20071114213543.GC31048@wotan.suse.de> (raw)
In-Reply-To: <22558.1195055979@redhat.com>
On Wed, Nov 14, 2007 at 03:59:39PM +0000, David Howells wrote:
> Nick Piggin <npiggin@suse.de> wrote:
>
> > Christoph Lameter has patches exactly to make PAGE_CACHE_SIZE larger than
> > PAGE_SIZE, and they seem to work without much effort. I happen to hate the
> > patches ;) but that doesn't change the fact that PAGE_CACHE_SIZE is
> > relatively useful and it is not at all an ill-defined concept.
>
> Where, please? mm kernels?
Floating around. I'm not saying it will even get upstream. It's just
an example.
> > Basically, anything that goes in the page cache is in units of
> > PAGE_CACHE_SIZE, and nothing else. For filesystems it should be pretty
> > easy...
>
> That depends on what the coverage of struct page is. I don't actually know
> whether this is PAGE_SIZE or PAGE_CACHE_SIZE; I assumed it to be the former,
> but from what you've said, I'm not actually sure.
It can be pretty well any power of 2 from PAGE_SIZE upwards, with
compound pages. None of the filesystems should really care at all.
It's not even a new concept, hugetlbfs uses HPAGE_SIZE...
next prev parent reply other threads:[~2007-11-14 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 13:56 Should PAGE_CACHE_SIZE be discarded? David Howells
2007-11-14 15:23 ` Nick Piggin
2007-11-14 15:59 ` David Howells
2007-11-14 21:35 ` Nick Piggin [this message]
2007-11-15 12:05 ` David Howells
2007-11-15 14:15 ` Benny Halevy
2007-11-15 14:46 ` David Howells
2007-11-15 21:30 ` Nick Piggin
2007-11-15 17:09 ` Jörn Engel
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=20071114213543.GC31048@wotan.suse.de \
--to=npiggin@suse.de \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).