but ... i fixed the performance problem that caused the previous
DEBUG_MUTEXES scalability problems. (there's no global mutex list
anymore) We also default to e.g. DEBUG_SLAB which is alot more costly.
OK. So what's the perf impact of the new version on a 32 cpu machine?
;-) Maybe it's fine, maybe it's not.
i'm wondering, why doesnt your config have DEBUG_MUTEXES disabled? Then
'make oldconfig' would pick it up automatically.
Because it builds off the same config file all the time. It was created
before CONFIG_MUTEXES existed ... creating a situation where we have to
explicitly disable new options all the time becomes a maintainance
nightmare ;-(
If we don't want to do performance regression checking on -mm, that's
fine, but I thought it was useful (has caught several things already).
If we want debug options explicitly enabled, we can do a separate debug
run, I'd think, but it makes it very difficult to do automated testing
if we add random new debug options all the time on by default ...
If we really think the debug options we're turning on by default have
zero perf impact, that's fine ... but it has not been my previous
experience. People obviously haven't checked that carefully in the past,
perhaps they are now and the world fixed itself, but I'm not that
optimistic ...
M.
-
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/
[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]
