Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [0/4] introduction

> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [0/4] introduction
    • From: KAMEZAWA Hiroyuki <[email protected]>

• References:
  • [RFC] [PATCH] virtual memmap on sparsemem v3 [0/4] introduction
    • From: KAMEZAWA Hiroyuki <[email protected]>

• Prev by Date: Re: Ext3 Errors...
• Next by Date: Re: [NETLINK]: Schedule removal of old macros exported to userspace
• Previous by thread: Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [4/4] ia64 support
• Next by thread: Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [0/4] introduction
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]