From: David Rientjes <rientjes@google.com>
To: Auguste Mome <augustmome@gmail.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-mm@kvack.org
Subject: Re: way to allocate memory within a range ?
Date: Tue, 23 Feb 2010 17:47:04 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1002231744110.3435@chino.kir.corp.google.com> (raw)
In-Reply-To: <17cb70ee1002231646m508f6483mcb667d4e67d9807f@mail.gmail.com>
On Wed, 24 Feb 2010, Auguste Mome wrote:
> I'd like to use kmem_cache() system, but need the memory taken from a
> specific range if requested, outside the range otherwise.
> I think about adding new zone and define new GFP flag to either select or
> ignore the zone. Does it sound possible? Then I welcome any hint if you know
> where to add the appropriated test in allocator, how to attach the
> region to the new zone id).
>
> Or slab/slub system is not designed for this, I should forget it and
> opt for another system?
>
No slab allocator is going to be designed for that other than SLAB_DMA to
allocate from lowmem. If you don't have need for lowmem, why do you need
memory only from a certain range? I can imagine it would have a usecase
for memory hotplug to avoid allocating slab that cannot be reclaimed on
certain nodes, but ZONE_MOVABLE seems more appropriate to guarantee such
migration properties.
--
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>
next prev parent reply other threads:[~2010-02-24 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 0:46 Auguste Mome
2010-02-24 1:47 ` David Rientjes [this message]
2010-02-24 15:35 ` Christoph Lameter
2010-03-21 9:38 ` Auguste Mome
2010-02-24 1:53 ` KAMEZAWA Hiroyuki
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=alpine.DEB.2.00.1002231744110.3435@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=augustmome@gmail.com \
--cc=cl@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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