Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> wrote:
>removing
>that sysconf() wreckage closed the gap considerably (needing to know
>the
>number of cpus to optimize locking sounds like a trainwreck all of its
>own, needing it _that_ often instead of just once at startup is even
>worse).
Yeah, I think it's ridiculous to say that glibc is not doing something stupid and that it's a problem with kernel interfaces.
Do the proc file parsing once and cache the result in a static variable. Doing it over and over again is just crazy.
Adding new system calls because glibc is crazy is insane.
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>