linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [patch 0/6] Compound Page Enhancements
Date: Fri, 25 May 2007 06:54:24 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705250642350.5199@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070524230032.554be39e.akpm@linux-foundation.org>

On Thu, 24 May 2007, Andrew Morton wrote:

> Well I've read that, and I've read the patches and I still don't see what
> the point in all this is.

A. vmstat can handle compound pages. No need to determine the size
   of a compound page to update VM statistics.

B. PageCompound is not useful in the long run. The processing of compound
   pages in the VM requires the knowledge if this is a head or tail page. That a 
   page is part of a compound page is not that useful knowlege.

C. Provide some more support for higher order page handling issues that
   Mel and I encounter.

D. Compound pages may be useful to handle higher order blocks on the 
   freelists if they can be handled efficiently. If we use the same 
   format for the freelist as for compound pages elsewhere then we will 
   have a common set of function to determine sizes etc etc.

E. Expands usefulness of get_page_unless_zero to compound pages. This
   is necessary to allow the moving of slabs and the moving of higher
   order pages for memory defragmentation.
 
F. Lays groundwork for large blocksize support.

> And looking back on it, I don't see the point in that PG_head_tail_mask
> hack either.  We could have done
> 
> static inline int page_tail(struct page *page)
> {
> 	return PageCompound(page) && (page->first_page != page);
> }
> 
> Confused.  Don't know where this is all headed.

To a better nicer looking VM.

--
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-05-25 13:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25  5:17 clameter
2007-05-25  5:17 ` [patch 1/6] Compound page handling enhancements clameter
2007-05-25  5:17 ` [patch 2/6] compound pages: Add new support functions clameter
2007-05-25  5:17 ` [patch 3/6] compound pages: vmstat support clameter
2007-05-25  5:17 ` [patch 4/6] compound pages: Use new compound vmstat functions in SLUB clameter
2007-05-25  5:17 ` [patch 5/6] compound pages: Allow use of get_page_unless_zero with compound pages clameter
2007-05-25  5:17 ` [patch 6/6] compound pages: Allow freeing of compound pages via pagevec clameter
2007-05-25  6:00 ` [patch 0/6] Compound Page Enhancements Andrew Morton
2007-05-25 13:54   ` Christoph Lameter [this message]
2007-05-25 14:03   ` Christoph Lameter
2007-05-25 17:14     ` Andrew Morton
2007-05-25 18:56       ` Christoph Lameter
2007-05-25  8:05 ` KAMEZAWA Hiroyuki
2007-05-25 13:42   ` Christoph Lameter

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.0705250642350.5199@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=wli@holomorphy.com \
    /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