mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Prezeroing V8
Date: Thu, 17 Mar 2005 15:52:08 -0800	[thread overview]
Message-ID: <20050317155208.22b72984.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0503171518030.10205@schroedinger.engr.sgi.com>

Christoph Lameter <clameter@sgi.com> wrote:
>
> > And given that we have separate buddy structures for zeroed and not-zeroed
>  > pages, why is this tagging needed at all?
> 
>  Because the buddy pointers may point to a page of the different kind. Then
>  a merge is not possible.

In that case I still don't understand, sorry.

If each zone has two buddy lists, one for zeroed and one for not-zeroed,
how can we ever get known-to-be-zeroed pages on the not-known-to-be-zeroed
list or vice versa?

>  > These are all design decisions which have been made, but they're not
>  > communicated either in the patch description or in code comments.  It's to
>  > everyone's advantage to fix that, no?
> 
>  Of course. Try to do this ASAP. Testing a patch that defines the
>  following:
> 
>  Index: linux-2.6.11/include/linux/gfp.h
>  ===================================================================
>  --- linux-2.6.11.orig/include/linux/gfp.h       2005-03-01
>  23:37:50.000000000 -0800
>  +++ linux-2.6.11/include/linux/gfp.h    2005-03-17 14:59:06.000000000
>  -0800
>  @@ -125,6 +125,8 @@ extern void FASTCALL(__free_pages(struct
>   extern void FASTCALL(free_pages(unsigned long addr, unsigned int order));
>   extern void FASTCALL(free_hot_page(struct page *page));
>   extern void FASTCALL(free_cold_page(struct page *page));
>  +extern void FASTCALL(free_hot_zeroed_page(struct page *page));
>  +extern void FASTCALL(free_cold_zeroed_page(struct page *page));
> 
>   #define __free_page(page) __free_pages((page), 0)
>   #define free_page(addr) free_pages((addr),0)
> 
>  This is what you want right?

Well, it was more a question that a request.  If we do this, does it speed
anything up?


  reply	other threads:[~2005-03-17 23:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 21:43 Christoph Lameter
2005-03-17 22:08 ` Andrew Morton
2005-03-17 22:31   ` Christoph Lameter
2005-03-17 23:11     ` Andrew Morton
2005-03-17 23:24       ` Christoph Lameter
2005-03-17 23:52         ` Andrew Morton [this message]
2005-03-18  0:00           ` Christoph Lameter
2005-03-17 23:26       ` Christoph Lameter
2005-03-17 23:59         ` Andrew Morton
2005-03-18  0:04           ` Christoph Lameter
2005-03-18  0:17             ` Andrew Morton
2005-03-18  0:29               ` Christoph Lameter
2005-03-18  1:36   ` [PATCH] Prezeroing V8 + free_hot_zeroed_page + free_cold_zeroed page Christoph Lameter
2005-03-18  2:06     ` Jason Uhlenkott
2005-03-18  2:09       ` Christoph Lameter
2005-03-18  5:43         ` Nish Aravamudan
2005-03-17 22:59 ` [PATCH] Prezeroing V8 Nish Aravamudan
2005-03-17 23:06   ` Christoph Lameter
2005-03-18  3:14     ` Benjamin Herrenschmidt
2005-03-25  1:44 ` Pavel Machek
2005-03-25 12:28   ` Jan Engelhardt
2005-03-29  1:50   ` [PATCH] " 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=20050317155208.22b72984.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome