From: Eric Dumazet <eric.dumazet@gmail.com>
To: monstr@monstr.eu
Cc: juice@swagman.org, netdev@vger.kernel.org
Subject: Re: Hight speed data sending from custom IP out of kernel
Date: Mon, 25 Apr 2011 14:30:25 +0200 [thread overview]
Message-ID: <1303734625.2747.121.camel@edumazet-laptop> (raw)
In-Reply-To: <1303734468.2747.120.camel@edumazet-laptop>
Le lundi 25 avril 2011 à 14:27 +0200, Eric Dumazet a écrit :
> Le lundi 25 avril 2011 à 14:18 +0200, Michal Simek a écrit :
>
> > >
> > > Now, if all you want to do is send many packets from pktgen (with only
> > > ID changing), you could add a fast path to not rebuild from scratch new
> > > packets.
> >
> > What do you mean?
>
>
> If you know your device has X slots in its TX ring buffer, you would
> have to maintain at least X+1 skbs in pktgen to make sure you reuse an
> skb while its previous logical content was sent on wire.
>
> Then you are free to only change iph->id and iph->check very fast.
>
Checking skb->users would also be a good way to know if TX completion
released skb reference. If your module owns the last reference, it can
do a recycle.
next prev parent reply other threads:[~2011-04-25 12:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 11:34 Hight speed data sending from custom IP out of kernel juice
2011-04-19 11:50 ` Michal Simek
2011-04-19 16:02 ` juice
2011-04-21 8:02 ` Michal Simek
2011-04-21 8:18 ` Eric Dumazet
2011-04-21 9:20 ` Michal Simek
2011-04-25 11:18 ` Michal Simek
2011-04-25 12:14 ` Eric Dumazet
2011-04-25 12:18 ` Michal Simek
2011-04-25 12:27 ` Eric Dumazet
2011-04-25 12:30 ` Eric Dumazet [this message]
2011-04-25 12:48 ` Michal Simek
2011-04-21 13:56 ` zhou rui
2011-04-21 14:31 ` zhou rui
2011-04-21 20:27 ` juice
-- strict thread matches above, loose matches on Subject: below --
2011-04-19 9:49 Michal Simek
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=1303734625.2747.121.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=juice@swagman.org \
--cc=monstr@monstr.eu \
--cc=netdev@vger.kernel.org \
/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