On Tue, Aug 02, 2011 at 11:33:09AM +0200, Bjørn Mork wrote:
"Kevin O'Connor" kevin@koconnor.net writes:
Also, it's possible the code could try to use the f-segment if there are less than say 16 cpus and use high memory when more cpus are present.
How about a variant over the last suggestion: Don't actually care bout the number of CPUs, but just fall back to malloc_high if malloc_fseg fails?
This could make testing painful - small changes in the code could cause a different table layout that is OS visible. I'd prefer a more strict cutoff. Though, I suppose the cutoff could be by the table size itself instead of by number of CPUs.
-Kevin