Benjamin LaHaise writes:
> Instead of doing a completely separate skb reuse path, what happens if
> you remove the memset() from __alloc_skb() and instead do it in a slab
> ctor? I remember seeing that in the profiles for af_unix. Dave, could
> you refresh my memory why the slab ctor ended up being dropped? Doing
> the memset() at free time is usually almost free since it is usually in
> the cache at that point.
Right but that's another issue...
This can be done I played with a variant of this too
I splitted alloc_skb in two parts to get the memset() part even done
in the driver just before passing the skb to the stack.
I did expect a big win in but I didn't see any gain. Strange but the code
was bad so it might be worth a try again. But this is a bit different
from the skb reuse we discuss now.
Cheers.
--ro
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
