linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 0/2 Buddy allocator with placement policy + prezeroing
Date: Mon, 28 Feb 2005 19:35:30 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0502281930490.29288@skynet> (raw)
In-Reply-To: <1109607127.6921.14.camel@localhost>

On Mon, 28 Feb 2005, Dave Hansen wrote:

> On Sun, 2005-02-27 at 13:42 +0000, Mel Gorman wrote:
> > In the two following emails are the latest version of the placement policy
> > for the binary buddy allocator to reduce fragmentation and the prezeroing
> > patch. The changelogs are with the patches although the most significant change
> > to the placement policy is a fix for a bug in the usemap size calculation
> > (pointed out by Mike Kravetz).
> >
> > The placement policy is Even Better than previous versions and can allocate
> > over 100 2**10 blocks of pages under loads in excess of 30 so I still
> > consider it ready for inclusion to the mainline.
> ...
>
> This patch does some important things for memory hotplug: it explicitly
> marks the different types of kernel allocations, and it separates those
> different types in the allocator.  When it comes to memory hot-remove
> this is certainly something we were going to have to do anyway.  Plus, I
> believe there are already at least two prototype patches that do this.
>

I have read through Matt Tolentino's version at least and this version of
the placement policy should be an easier merge for hotplug. Particularly,
stuff from his patch like the removal of magic numbers (which I should
have done anyway) are present in this version of the placement policy
patch. I will also move how a MAX_ORDER-1 block of pages is removed from
the global list and put it in it's own inline function.

> Anything that makes future memory hotplug work easier is good in my
> book. :)
>

If there are any other changes that might make hotplug's life easier, I'm
sure someone will shout :)

-- 
Mel Gorman
--
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:"aart@kvack.org"> aart@kvack.org </a>

      reply	other threads:[~2005-02-28 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 13:42 Mel Gorman
2005-02-28 16:12 ` Dave Hansen
2005-02-28 19:35   ` Mel Gorman [this message]

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.58.0502281930490.29288@skynet \
    --to=mel@csn.ul.ie \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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