Messages in this thread | | | Subject | Re: 2.4.23aa2 (bugfixes and important VM improvements for the high end) | From | Andi Kleen <> | Date | 28 Feb 2004 13:46:47 +0100 |
| |
Andrea Arcangeli <andrea@suse.de> writes: > > we can add a config option to enable together with 2.5:1.5 to drop the > gap page in vmalloc, and to reduce the vmalloc space, so that we can > sneak another few "free" dozen megs back for the 64G kernel just to get > more margin even if we don't strictly need it. (btw, the vmalloc space > is also tunable at boot, so this config option would just change the > default value)
Not sure if that would help, but you could relatively easily save 8 bytes on 32bit for each vma too. Replace vm_next with rb_next() and move vm_rb.color into vm_flags. It would be a lot of editing work though. NUMA API will add new 4 bytes again.
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |