linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: David Howells <dhowells@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, mhalcrow@us.ibm.com,
	phillip@hellewell.homeip.net, sfrench@samba.org
Subject: Re: [rfc][patch 3/5] afs: new aops
Date: Wed, 14 Nov 2007 22:32:10 +0100	[thread overview]
Message-ID: <20071114213210.GB31048@wotan.suse.de> (raw)
In-Reply-To: <22543.1195055866@redhat.com>

On Wed, Nov 14, 2007 at 03:57:46PM +0000, David Howells wrote:
> Nick Piggin <npiggin@suse.de> wrote:
> 
> > In core code, the PAGE_CACHE_SIZE is for page cache struct pages. Single
> > struct pages (not page arrays).  Take a look at generic mapping read or
> > something.
> 
> So you're saying a struct page controls an area of PAGE_CACHE_SIZE, not an
> area of PAGE_SIZE?

No, a pagecache page is PAGE_CACHE_SIZE. And not all struct pages control
the same amount of data anyway, with compound pages.


> Is a struct page then a purely pagecache concept?
> 
> > Documentation is the opposite of convention ;)
> 
> If it's not Documented, then it's irrelevant.

But you can't just decide yourself that it is irrelevant because you don't
grep hard enough ;)

include/linux/mm.h:
 * A page may belong to an inode's memory mapping. In this case, page->mapping
 * is the pointer to the inode, and page->index is the file offset of the page,
 * in units of PAGE_CACHE_SIZE.

include/linux/mm_types.h
        unsigned long vm_pgoff;         /* Offset (within vm_file) in PAGE_SIZE
                                           units, *not* PAGE_CACHE_SIZE */

Looks like documentation to me.


  reply	other threads:[~2007-11-14 21:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12  7:12 [rfc][patches] remove ->prepare_write Nick Piggin
2007-11-12  7:13 ` [rfc][patch 1/5] ecryptfs new aops Nick Piggin
2007-11-12  7:14 ` [rfc][patch 2/5] cifs: " Nick Piggin
2007-11-12  7:14 ` [rfc][patch 3/5] afs: " Nick Piggin
2007-11-12  7:20 ` [rfc][patch 4/5] rd: rewrite rd Nick Piggin
2007-11-12  7:23 ` [rfc][patch 5/5] remove prepare_write Nick Piggin
2007-11-12 15:29 ` [rfc][patch 3/5] afs: new aops David Howells
2007-11-13  0:15   ` Nick Piggin
2007-11-13  0:30   ` David Howells
2007-11-13  0:44     ` Nick Piggin
2007-11-13 10:56     ` David Howells
2007-11-14  4:24       ` Nick Piggin
2007-11-14 12:18       ` David Howells
2007-11-14 15:18         ` Nick Piggin
2007-11-14 15:57         ` David Howells
2007-11-14 21:32           ` Nick Piggin [this message]
2007-11-15 12:15           ` David Howells
2007-11-15 21:37             ` Nick Piggin

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=20071114213210.GB31048@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mhalcrow@us.ibm.com \
    --cc=phillip@hellewell.homeip.net \
    --cc=sfrench@samba.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).