\ > That's one reason I didn't make it 16MB. A 4MB machine is pretty damn > embedded these days (you'd want to enable EMBEDDED just to turn off some > other things that make the kernel bigger), but I can imagine that real > people run Linux/x86 in 16MB as long as they don't run X. for PAE it might make sense to just bump it to 16... but then again.. DMA zone pressure in 2.6 is almost gone anyway - 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/
- References:
- Patch to make the head.S-must-be-first-in-vmlinux order explicit
- From: Arjan van de Ven <[email protected]>
- Patch to reorder functions in the vmlinux to a defined order
- From: Arjan van de Ven <[email protected]>
- Re: Patch to reorder functions in the vmlinux to a defined order
- From: Andi Kleen <[email protected]>
- Re: Patch to reorder functions in the vmlinux to a defined order
- From: Arjan van de Ven <[email protected]>
- Re: Patch to reorder functions in the vmlinux to a defined order
- From: Linus Torvalds <[email protected]>
- Re: Patch to reorder functions in the vmlinux to a defined order
- From: Rene Herman <[email protected]>
- Re: Patch to reorder functions in the vmlinux to a defined order
- From: Linus Torvalds <[email protected]>
- Patch to make the head.S-must-be-first-in-vmlinux order explicit
- Prev by Date: Re: Slab: Node rotor for freeing alien caches and remote per cpu pages.
- Next by Date: Re: make -j with j <= 4 seems to only load a single CPU core
- Previous by thread: Re: Patch to reorder functions in the vmlinux to a defined order
- Next by thread: Re: Patch to reorder functions in the vmlinux to a defined order
- Index(es):
 |