All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Christoph Lameter <clameter@engr.sgi.com>,
	Andy <apw@shadowen.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [0/4] introduction
Date: Sat, 9 Dec 2006 12:51:37 +0100	[thread overview]
Message-ID: <20061209115137.GA10380@osiris.ibm.com> (raw)
In-Reply-To: <20061208155608.14dcd2e5.kamezawa.hiroyu@jp.fujitsu.com>

> Virtual mem_map is not useful for 32bit archs. This uses huge virtual
> address range.

Why? The s390 vmem_map implementation which I sent last week to linux-mm
is merged in the meantime. It supports both 32 and 64 bit.
The main reason is to keep things simple and avoid #ifdef hell.

Since the maximum size of the virtual array is  about 16MB it's not much
waste of address space. Actually I just changed the size of the vmalloc
area, so that the maximum supported physical amount of memory is still 1920MB.

  parent reply	other threads:[~2006-12-09 11:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08  6:56 [RFC] [PATCH] virtual memmap on sparsemem v3 [0/4] introduction KAMEZAWA Hiroyuki
2006-12-08  7:01 ` [RFC] [PATCH] virtual memmap on sparsemem v3 [1/4] map and unmap KAMEZAWA Hiroyuki
2006-12-09  0:28   ` Andrew Morton
2006-12-09  2:43     ` KAMEZAWA Hiroyuki
2006-12-09  4:52       ` KAMEZAWA Hiroyuki
2006-12-08  7:04 ` [RFC] [PATCH] virtual memmap on sparsemem v3 [2/4] generic virtual mem_map on sparsemem KAMEZAWA Hiroyuki
2006-12-09 12:05   ` Heiko Carstens
2006-12-09 13:17     ` KAMEZAWA Hiroyuki
2006-12-11  6:44       ` KAMEZAWA Hiroyuki
2006-12-08  7:07 ` [RFC] [PATCH] virtual memmap on sparsemem v3 [3/4] static virtual mem_map KAMEZAWA Hiroyuki
2006-12-09  0:30   ` Andrew Morton
2006-12-09  2:49     ` KAMEZAWA Hiroyuki
2006-12-09  3:33       ` Andrew Morton
2006-12-09  3:41         ` KAMEZAWA Hiroyuki
2006-12-09  4:53           ` KAMEZAWA Hiroyuki
2006-12-08  7:08 ` [RFC] [PATCH] virtual memmap on sparsemem v3 [4/4] ia64 support KAMEZAWA Hiroyuki
2006-12-09  4:55   ` KAMEZAWA Hiroyuki
2006-12-09 11:51 ` Heiko Carstens [this message]
2006-12-09 13:21   ` [RFC] [PATCH] virtual memmap on sparsemem v3 [0/4] introduction KAMEZAWA Hiroyuki
2006-12-10 19:47 ` Bob Picco
2006-12-11  0:43   ` 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=20061209115137.GA10380@osiris.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=clameter@engr.sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.