On Mon, 10 Sep 2007, Nick Piggin wrote:
> OK, so after isolating the scheduler, then SLUB should be as fast as SLAB
> at the same allocation size. That's basically what we need to do before we
> can replace SLAB with it, I think?
The regression is due to the limited number of objects in the per cpu
"queue" in SLUB for 4k objects. With the .23 code this is one or two
(order 1 slab). So we have to call into the page allocator frequently and
do it for order 1 pages which requires the zone locks. Urgh.
I think the regression is best addressed by the page allocator pass
through patch in mm which makes the page allocator handle these objects.
They are single pages so the pcp lists are in use which provide much
larger queues than SLUB/SLAB.
IMHO >=4k objects should be handled by the page allocator. From the
numbers I have seen there is then still a 1% regression left. If
that is still the case after we have fixed the scheduler then maybe
we need to slim down the page allocator fast path.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
