From: Rick Jones <rick.jones2@hp.com>
To: Radha Mohan <radhamohan_ch@yahoo.com>
Cc: netdev@vger.kernel.org
Subject: Re: can we reuse an skb
Date: Fri, 19 Jun 2009 09:56:06 -0700 [thread overview]
Message-ID: <4A3BC326.4090203@hp.com> (raw)
In-Reply-To: <962874.62146.qm@web94813.mail.in2.yahoo.com>
Radha Mohan wrote:
> Hi,
>
> For an ethernet driver, we need to allocate some pool of SKBs for
> receiving packets. Is there any way we can reuse the same SKBs
> without the need to re-allocate in atomic every time one has been
> used up for netif_rx().
Assuming a driver did have its own "pool" and didn't rely on the pool(s)
from which skbs are drawn, doesn't that mean you have to now have
another configuable? There is no good guarantees on when the upper
layers will be finished with the skb right? Which means you would be
requiring the admin(s) to have an idea of how long their applications
wait to pull data from their sockets and configure your driver accordingly.
It would seem there would have to be a considerable performance gain
demonstrated for that kind of thing?
rick jones
next prev parent reply other threads:[~2009-06-19 16:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 6:46 can we reuse an skb Radha Mohan
2009-06-19 6:51 ` jon_zhou
2009-06-19 7:10 ` Radha Mohan
2009-06-19 7:21 ` Peter Chacko
2009-06-19 10:37 ` Saikiran Madugula
2009-06-19 18:41 ` Neil Horman
2009-06-19 16:56 ` Rick Jones [this message]
2009-06-19 23:29 ` David Miller
2009-06-20 3:54 ` Peter Chacko
2009-06-20 8:00 ` Evgeniy Polyakov
2009-06-20 11:51 ` Ben Hutchings
2009-06-21 5:41 ` Peter Chacko
2009-06-21 5:49 ` David Miller
2009-06-21 11:46 ` [RFD] Pluggable code design (was: can we reuse an skb) Al Boldi
-- strict thread matches above, loose matches on Subject: below --
2009-06-19 10:11 can we reuse an skb Nicholas Van Orton
2009-06-22 13:34 ` Philby John
2009-06-22 13:56 ` Peter Chacko
2009-06-22 14:33 ` Philby John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A3BC326.4090203@hp.com \
--to=rick.jones2@hp.com \
--cc=netdev@vger.kernel.org \
--cc=radhamohan_ch@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).