linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Nick Piggin <npiggin@suse.de>, linux-mm@kvack.org, dgc@sgi.com
Subject: Re: [RFC] Free up page->private for compound pages
Date: Thu, 5 Apr 2007 13:07:16 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704051302080.11287@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704052006320.21325@blonde.wat.veritas.com>

On Thu, 5 Apr 2007, Hugh Dickins wrote:

> > I am not so much worried about performance but more about the availability 
> > of the page->private field of compound pages.
> 
> Yes, I realise that.  I meant
> 	if (unlikely(PageCompound(page)) && PageTail(page))
> shouldn't slow down the !PageCompound fast paths more than the existing
> 	if (unlikely(PageCompound(page)))
> or the
> 	if (unlikely(PageTail(page)))
> you had.

Right.

> > I think we cannot overload the page flag after all because of the page 
> > count issue you pointed out. Guess I should be cleaning up my 
> > initial patch and repost it?
> 
> I still think PageTail is not worth its own distinct page flag:

Well I think we just killed 2 flags for software suspend. Did I not earn 
at least one by being involved in that project? ;-)

> I can understand you drawing back from my page+1 suggestion,
> but I don't understand why you're so reluctant to say
> 	if (unlikely(PageCompound(page)) && PageTail(page))

Thats fine with me. Ahh.. This would solve the alias issue.... (Lights
going on). Okay we can overload after all. Need to add some comments 
though.


--
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>

  reply	other threads:[~2007-04-05 20:07 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
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 [this message]
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.0704051302080.11287@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=dgc@sgi.com \
    --cc=hugh@veritas.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