Re: [patch 01/28] cpu alloc: The allocator

On Tue, 13 Nov 2007, David Miller wrote:

> One thing you could do is simply use a vmalloc allocation in the
> non-virtualized case.

Yuck. Meaning to add more crappy code. The bss limitations to 8M is a bit 
strange though. Do other platforms have the same issues? 
-
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 01/28] cpu alloc: The allocator
  - From: David Miller <[email protected]>
- Re: [patch 01/28] cpu alloc: The allocator
  - From: Eric Dumazet <[email protected]>

References:
- [patch 00/28] cpu alloc v1: Optimize by removing arrays of pointers to per cpu objects
  - From: Christoph Lameter <[email protected]>
- [patch 01/28] cpu alloc: The allocator
  - From: Christoph Lameter <[email protected]>
- Re: [patch 01/28] cpu alloc: The allocator
  - From: David Miller <[email protected]>

Prev by Date: Re: [BUG] New Kernel Bugs
Next by Date: Re: [PATCH 0/5][RFC] Physical PCI slot objects
Previous by thread: Re: [patch 01/28] cpu alloc: The allocator
Next by thread: Re: [patch 01/28] cpu alloc: The allocator
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]