On Mon, 12 Dec 2011, Shaohua Li wrote: > With the per-cpu partial list, I didn't see any workload which is still > suffering from the list lock, so I suppose both the trashing approach > and pick 25% used slab approach don't help. This doesn't necessarily have anything to do with contention on list_lock, it has to do with the fact that ~99% of allocations come from the slowpath since the cpu slab only has one free object when it is activated, that's what the statistics indicated for kmalloc-256 and kmalloc-2k. That's what I called "slab thrashing": the continual deactivation of the cpu slab and picking from the partial list that would only have one or two free objects causing the vast majority of allocations to require the slowpath. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. 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>