This seems like a pretty dumb test case. We have 64 cores sitting in a
loop "allocating" 32MB of memory, not actually using that memory and
then freeing it up again.
Any not-completely-insane application would actually _use_ the memory.
Which involves pagefaults, page allocations and much memory traffic
modifying the page contents.
Do we actually care?
It's a bit like a poorly tuned malloc. From what I heard poorly tuned
mallocs are quite
common in the field, also with lots of custom ones around.
While it would be good to tune them better the kernel should also have
reasonable performance
for this case.
The poorly tuned malloc has other problems too, but this addresses at
least one
of them.
Also I think Tim's patch is a general improvement to a somewhat dumb
code path.
-Andi
--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>