On Fri, Dec 30, 2011 at 03:04:30PM +0100, Ariane van der Steldt wrote: > On Fri, Dec 30, 2011 at 02:42:18PM +0100, Ariane van der Steldt wrote: > > The huge diff included below is to replace vmmap for something that > > works a lot better. This is the second version I plan to commit. > > I have been running this on my laptop for months and have had no > > problems. > > > > The current incarnation is: > > vmmap_sys.diff.63
Which never made it to the list apparently. I'll just blame spam filtering and provide it an alternative way: http://www.stack.nl/~ariane/vmmap_sys.diff.63 SHA256 (vmmap_sys.diff.63) = 5c3e71360795f3899baa652f6ba6caa999b137b01a778dca12c253af1dbcff00 MD5 (vmmap_sys.diff.63) = 11736a0bacb0b8b72079935ba01c62c4 size: 305720 bytes Highlights: - the mapping and allocation (address selection) logic is split - the allocator is in compatibility mode, meaning it ought to perform the same strategies (and hence contain the same bugs, yay) as the version that you are running in your kernel at the moment (this means java and various browsers won't die horribly, at least not more than they used to) - despite using the same algorithm, it is a bit^W alot faster - it's only a 3^W 10494 line diff :P I'll need testing on any and all architectures. Thanks, -- Ariane
