From: jamal <[EMAIL PROTECTED]>
Date: Fri, 09 Dec 2005 16:30:24 -0500

> indeed sounds interesting until you start hitting clones ;->
> so dont run a sniffer or do anything of the sort if you want to see
> some good numbers - otherwise I suspect you will get worse numbers than
> the case of current path and skbs being cloned/shared.

If it gets cloned then it simply degenerates to roughly what
is happening today.  We'll simply not allow the driver to
reuse the buffer and it will need to allocate a new one.

Or, we could mark SKB's specially when their usage ratio is
low.  At clone/share time, we can "cow" the SKB into a smaller
one.

There are a lot of things we can do to defer reallocation until
it is absolutely necessary and avoid it in most cases.

In fact, thinking more, if we put the copybreak logic into
the local protocol reception, we can check the cloned/shared
state right then and there and know if we can give it back
or not.
-
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

Reply via email to