Hi > Could you address the performance issues in different ways? F.e. try to free > when the object is hot or free from multiple processors? SLAB has to take the > list_lock rather frequently under high concurrent loads (depends on queue > size). That will not occur with SLUB. So you actually can free (and allocate) > concurrently with high performance. just information. (offtopic?) When hackbench running, SLUB consume memory very largely than SLAB. then, SLAB often outperform SLUB in memory stavation state. I don't know why memory comsumption different. Anyone know it? -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
