On Thu, 22 Aug 2013, Joonsoo Kim wrote: > And this patchset change a management method of free objects of a slab. > Current free objects management method of the slab is weird, because > it touch random position of the array of kmem_bufctl_t when we try to > get free object. See following example.
The ordering is intentional so that the most cache hot objects are removed first. > To get free objects, we access this array with following pattern. > 6 -> 3 -> 7 -> 2 -> 5 -> 4 -> 0 -> 1 -> END Because that is the inverse order of the objects being freed. The cache hot effect may not be that significant since per cpu and per node queues have been aded on top. So maybe we do not be so cache aware anymore when actually touching struct slab. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
