From: andi.kleen@intel.com (Andi Kleen)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH 0/3] big chunk memory allocator v2
Date: Fri, 29 Oct 2010 12:31:54 +0200 [thread overview]
Message-ID: <20101029103154.GA10823@gargoyle.fritz.box> (raw)
In-Reply-To: <op.vlbywq137p4s8u@pikus>
> When I was posting CMA, it had been suggested to create a new migration type
> dedicated to contiguous allocations. I think I already did that and thanks to
> this new migration type we have (i) an area of memory that only accepts movable
> and reclaimable pages and
Aka highmem next generation :-(
> (ii) is used only if all other (non-reserved) pages have
> been allocated.
That will be near always the case after some uptime, as memory fills up
with caches. Unless you do early reclaim?
-Andi
next prev parent reply other threads:[~2010-10-29 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101026190042.57f30338.kamezawa.hiroyu@jp.fujitsu.com>
2010-10-27 23:22 ` [RFC][PATCH 0/3] big chunk memory allocator v2 Minchan Kim
2010-10-29 9:20 ` Michał Nazarewicz
2010-10-29 10:31 ` Andi Kleen [this message]
2010-10-29 10:59 ` KAMEZAWA Hiroyuki
2010-10-29 12:29 ` Andi Kleen
2010-10-29 12:31 ` KAMEZAWA Hiroyuki
2010-10-29 12:43 ` Michał Nazarewicz
2010-10-29 14:27 ` Andi Kleen
2010-10-29 14:58 ` Michał Nazarewicz
2010-10-29 13:11 ` Minchan Kim
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=20101029103154.GA10823@gargoyle.fritz.box \
--to=andi.kleen@intel.com \
--cc=linux-arm-kernel@lists.infradead.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