All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: David Howells <dhowells@redhat.com>
Cc: Nick Piggin <npiggin@suse.de>,
	torvalds@osdl.org, linux-arch@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: Should PAGE_CACHE_SIZE be discarded?
Date: Thu, 15 Nov 2007 16:15:12 +0200	[thread overview]
Message-ID: <473C5470.70005@panasas.com> (raw)
In-Reply-To: <311.1195128303@redhat.com>

On Nov. 15, 2007, 14:05 +0200, David Howells <dhowells@redhat.com> wrote:
> Nick Piggin <npiggin@suse.de> wrote:
> 
>> 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...
> 
> Ummm... The filesystem has to care.  If the VFS/VM says 'fill this page' you
> do need to know how big the page is or whether it's even actually several
> pages.

I think that what Nick was trying to say is that PAGE_CACHE_SIZE should always
be used properly as the size of the memory struct Page covers (while PAGE_SIZE
is the hardware page size and the constraint is that PAGE_CACHE_SIZE == (PAGE_SIZE << k)
for some k >= 0).  If everybody does that then "None of the filesystems should really
care at all". That said, it doesn't seem like the current usage in fs/ and drivers/
is consistent with this convention.

> 
> David
> -


  reply	other threads:[~2007-11-15 14:40 UTC|newest]

Thread overview: 10+ 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
2007-11-15 12:05       ` David Howells
2007-11-15 14:15         ` Benny Halevy [this message]
2007-11-15 14:46           ` David Howells
2007-11-15 21:30             ` Nick Piggin
2007-11-15 17:09 ` Jörn Engel
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=473C5470.70005@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=dhowells@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --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 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.