From: Christoph Lameter <clameter@sgi.com>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-mm@kvack.org, dgc@sgi.com
Subject: Re: [RFC] Free up page->private for compound pages
Date: Wed, 4 Apr 2007 20:38:52 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704042037550.8745@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070405033648.GG11192@wotan.suse.de>
On Thu, 5 Apr 2007, Nick Piggin wrote:
> On Wed, Apr 04, 2007 at 08:19:22PM -0700, Christoph Lameter wrote:
> > If we add a new flag so that we can distinguish between the
> > first page and the tail pages then we can avoid to use page->private
> > in the first page of a compound page. page->private == page for the first
> > page, so there is no real information in there.
>
> Couldn't you use something like PageActive for the head page instead of
> taking up a new flag, seeing as we don't put compound pages on the LRU?
We could set up an alias for now?
If we start supporting compound pages for filesystem then we will have
these pages on the LRU.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-04-05 3:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 3:19 Christoph Lameter
2007-04-05 3:36 ` Nick Piggin
2007-04-05 3:38 ` Christoph Lameter [this message]
2007-04-05 3:57 ` Nick Piggin
2007-04-05 4:04 ` Christoph Lameter
2007-04-05 4:25 ` Nick Piggin
2007-04-05 4:34 ` Christoph Lameter
2007-04-05 14:30 ` Hugh Dickins
2007-04-05 18:17 ` Christoph Lameter
2007-04-05 18:40 ` Hugh Dickins
2007-04-05 18:58 ` Christoph Lameter
2007-04-05 19:50 ` Hugh Dickins
2007-04-05 20:07 ` Christoph Lameter
2007-04-05 15:13 ` Dave Kleikamp
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.4.64.0704042037550.8745@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=dgc@sgi.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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