linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: "Eric W. Biederman" <ebiederm+eric@npwt.net>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: (reiserfs) Re: Maybe we can do 40 bits in June/July. (fwd)
Date: Wed, 22 Apr 1998 14:29:18 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.3.95.980422140626.9664A-100000@as200.spellcast.com> (raw)
In-Reply-To: <m1yawxoi36.fsf@flinx.npwt.net>

On 22 Apr 1998, Eric W. Biederman wrote:
...
> My design:
> As I understand it the buffer cache is fine, so it is just a matter
> getting the page cache and the vma and the glue working.

The buffer cache is currently fine, but we do want to get rid of it...

> My thought is to make the page cache use generic keys. 
> This should help support things like the swapper inode a little
> better.  Still need a bit somewhere so we can coallese VMA's that have
> an inode but don't need continous keys.  That's for later.

Hmmm, if you've seen my rev_pte patch then you'll notice that *all* vmas
will soon need continuous keys... 

> For the common case of inodes have the those keys:
> page->key == page->offset >> PAGE_SHIFT.

Not a good idea unless support for a.out is dropped completely -- a better
choice would be to use 512 as a divisor; then pages can at least be at the
block offset as needed by a.out.

Something else to keep in mind is that we also need a mechanism to keep
metadata in the page cache (rather, per-inode metadata; fixed metadata can
just use its own inode).

> And of course get rid of page->offset.  The field name changes will to
> catch any old code that is out there.

That's a good idea.

		-ben

  reply	other threads:[~1998-04-22 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-22 13:18 Rik van Riel
1998-04-22 17:57 ` Eric W. Biederman
1998-04-22 18:29   ` Benjamin C.R. LaHaise [this message]
1998-04-22 21:08     ` Eric W. Biederman

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=Pine.LNX.3.95.980422140626.9664A-100000@as200.spellcast.com \
    --to=blah@kvack.org \
    --cc=ebiederm+eric@npwt.net \
    --cc=linux-mm@kvack.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