linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Timur Tabi <timur@freescale.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Subject: Re: Fw: [PATCH] Add alloc_pages_exact() and free_pages_exact()
Date: Mon, 7 Jul 2008 16:42:39 +1000	[thread overview]
Message-ID: <200807071642.39972.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <48625571.9060201@freescale.com>

On Thursday 26 June 2008 00:25, Timur Tabi wrote:
> Nick Piggin wrote:
> > On Wednesday 25 June 2008 06:57, Andrew Morton wrote:
> >> I'm applying this.
> >
> > Fine. And IIRC there are one or two places around the kernel that
> > could be converted to use it. Why not just have a node id
> > argument and call it alloc_pages_node_exact? so Christoph doesn't
> > have to do it himself ;)
>
> Since I don't know anything nodes, I can't say whether this is a good idea
> or not, or even how to implement it.  Sorry.

Just give an 'int nid' parameter, and then pass it through to
alloc_pages_node. You don't have to do anything with it directly.


> > Maybe you could also say that __GFP_COMPOUND cannot be used, and
> > that the returned pages are "split" (work the same way as N
> > indivudually allocated order-0 pages WRT refcounting).
>
> Is this a suggestion for the function comments?

Yes, just comments.

--
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:[~2008-07-07  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 20:57 Andrew Morton
2008-06-25  1:39 ` Nick Piggin
2008-06-25 14:25   ` Timur Tabi
2008-07-07  6:42     ` Nick Piggin [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=200807071642.39972.nickpiggin@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=timur@freescale.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