Re: [Patch] Move swiotlb_init early on X86_64

On 01 Mar 2006 09:10:58 +0800, Zou Nan hai <[email protected]> wrote:
> on X86_64, swiotlb buffer is allocated in mem_init, after memmap and vfs cache allocation.
>
> On platforms with huge physical memory,
> large memmap and vfs cache may eat up all usable system memory
> under 4G.
>
> Move swiotlb_init early before memmap is allocated can
> solve this issue.

Shouldn't memmap be allocated from memory above 4G (if available)? Using
up lots of <4G memory on something that doesn't need to be below 4G
sounds like a poor use of resources.

-Tony
-
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: [Patch] Move swiotlb_init early on X86_64
    • From: Andi Kleen <[email protected]>

• References:
  • [Patch] Move swiotlb_init early on X86_64
    • From: Zou Nan hai <[email protected]>

• Prev by Date: Re: 2.6.16rc5 'found' an extra CPU.
• Next by Date: Re: [patch 18/39] [PATCH] sys_mbind sanity checking
• Previous by thread: [Patch] Move swiotlb_init early on X86_64
• Next by thread: Re: [Patch] Move swiotlb_init early on X86_64
• 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]