From: Andi Kleen <andi.kleen@intel.com>
To: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
"fujita.tomonori@lab.ntt.co.jp" <fujita.tomonori@lab.ntt.co.jp>,
"felipe.contreras@gmail.com" <felipe.contreras@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Russell King <linux@arm.linux.org.uk>,
Pawel Osciak <pawel@osciak.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC][PATCH 0/3] big chunk memory allocator v2
Date: Fri, 29 Oct 2010 16:27:41 +0200 [thread overview]
Message-ID: <20101029142741.GB19823@gargoyle.fritz.box> (raw)
In-Reply-To: <op.vlb8bda87p4s8u@pikus>
On Fri, Oct 29, 2010 at 01:43:51PM +0100, MichaA? Nazarewicz wrote:
> >>>> (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?
>
> Hmm... true. Still the point remains that only movable and reclaimable pages are
> allowed in the marked regions. This in effect means that from unmovable pages
> point of view, the area is unusable but I havn't thought of any other way to
> guarantee that because of fragmentation, long sequence of free/movable/reclaimable
> pages is available.
Essentially a movable zone as defined today.
That gets you near all the problems of highmem (except for the mapping
problem and you're a bit more flexible in the splits):
Someone has to decide at boot how much should be movable
and what not, some workloads will run out of space, some may
deadlock when it runs out of management objects, etc.etc.
Classic highmem had a long string of issues with all of this.
If it was an easy problem it had been long solved, but it isn't really.
-Andi
--
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-10-29 14:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 10:00 KAMEZAWA Hiroyuki
2010-10-26 10:02 ` [RFC][PATCH 1/3] move code from memory_hotplug to page_isolation KAMEZAWA Hiroyuki
2010-10-26 10:04 ` [RFC][PATCH 2/3] a help function for find physically contiguous block KAMEZAWA Hiroyuki
2010-10-29 3:53 ` Bob Liu
2010-10-29 4:00 ` KAMEZAWA Hiroyuki
2010-10-26 10:08 ` [RFC][PATCH 3/3] a big contig memory allocator KAMEZAWA Hiroyuki
2010-10-29 3:55 ` Bob Liu
2010-10-29 4:02 ` KAMEZAWA Hiroyuki
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
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 [this message]
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=20101029142741.GB19823@gargoyle.fritz.box \
--to=andi.kleen@intel.com \
--cc=corbet@lwn.net \
--cc=felipe.contreras@gmail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=m.nazarewicz@samsung.com \
--cc=minchan.kim@gmail.com \
--cc=pawel@osciak.com \
--cc=peterz@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