linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan.kim@gmail.com>
To: Andi Kleen <andi.kleen@intel.com>
Cc: "Michał Nazarewicz" <m.nazarewicz@samsung.com>,
	"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.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 22:11:03 +0900	[thread overview]
Message-ID: <AANLkTin2Q-qQSnzc9sZnP_inf+5SEgG5cXYA8f-0goYG@mail.gmail.com> (raw)
In-Reply-To: <20101029103154.GA10823@gargoyle.fritz.box>

2010/10/29 Andi Kleen <andi.kleen@intel.com>:
>> 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 :-(

I lost the road. What is highmem next generation?
Could you point it to me?

-- 
Kind regards,
Minchan Kim

--
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>

      parent reply	other threads:[~2010-10-29 13:11 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
2010-10-29 14:58               ` Michał Nazarewicz
2010-10-29 13:11       ` Minchan Kim [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=AANLkTin2Q-qQSnzc9sZnP_inf+5SEgG5cXYA8f-0goYG@mail.gmail.com \
    --to=minchan.kim@gmail.com \
    --cc=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=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