From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, linux-ia64@vger.kernel.org, schwidefsky@de.ibm.com
Subject: Re: [RFC] virtual memmap for sparsemem [1/2] arch independent part
Date: Tue, 21 Nov 2006 13:19:03 +0100 [thread overview]
Message-ID: <20061121121903.GC8122@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20061121211937.e25dceb8.kamezawa.hiroyu@jp.fujitsu.com>
> > I'd love to go for a generic implementation, but if that is based on
> > sparsemem it doesn't make too much sense on s390.
>
> 'What type of vmem_map is supported ?' is maybe per-arch decision not generic.
> If people dislikes Flat/Discontig/Sparsemem complication, some clean
> up patch will be posted and discussion will start. If not, nothing will happen.
Ok, I will work on the s390 arch specific patch and post it here. Maybe it's
worth adding a generic vmem_map interface, maybe not. We'll see.
--
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>
prev parent reply other threads:[~2006-11-21 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 8:21 KAMEZAWA Hiroyuki
2006-10-19 15:16 ` Andy Whitcroft
2006-10-19 16:43 ` Christoph Lameter
2006-10-20 1:00 ` KAMEZAWA Hiroyuki
2006-10-19 16:39 ` Christoph Lameter
2006-10-20 1:18 ` KAMEZAWA Hiroyuki
2006-10-20 1:42 ` Christoph Lameter
2006-10-20 2:06 ` KAMEZAWA Hiroyuki
2006-10-20 2:26 ` Christoph Lameter
2006-10-20 16:20 ` Luck, Tony
2006-11-21 11:37 ` Heiko Carstens
2006-11-21 12:19 ` KAMEZAWA Hiroyuki
2006-11-21 12:19 ` Heiko Carstens [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=20061121121903.GC8122@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=schwidefsky@de.ibm.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