From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: ast@plumgrid.com, edumazet@google.com, netdev@vger.kernel.org,
brouer@redhat.com
Subject: Re: [PATCH v2 net-next] net: pktgen: packet bursting via skb->xmit_more
Date: Thu, 2 Oct 2014 12:44:36 +0200 [thread overview]
Message-ID: <20141002124436.0d335b97@redhat.com> (raw)
In-Reply-To: <20141001.220839.1118640596408366269.davem@davemloft.net>
On Wed, 01 Oct 2014 22:08:39 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> From: Alexei Starovoitov <ast@plumgrid.com>
> Date: Tue, 30 Sep 2014 17:53:21 -0700
>
> > This patch demonstrates the effect of delaying update of HW tailptr.
> > (based on earlier patch by Jesper)
> >
> > burst=1 is the default. It sends one packet with xmit_more=false
> > burst=2 sends one packet with xmit_more=true and
> > 2nd copy of the same packet with xmit_more=false
> > burst=3 sends two copies of the same packet with xmit_more=true and
> > 3rd copy with xmit_more=false
> >
> > Performance with ixgbe (usec 30):
> > burst=1 tx:9.2 Mpps
> > burst=2 tx:13.5 Mpps
> > burst=3 tx:14.5 Mpps full 10G line rate
> >
> > Signed-off-by: Alexei Starovoitov <ast@plumgrid.com>
>
> Applied, great work.
Updated my pktgen script "pktgen02_burst.sh" for supporting this new
"burst" option:
https://github.com/netoptimizer/network-testing/commit/cb625712f8efb
https://github.com/netoptimizer/network-testing/blob/master/pktgen/pktgen02_burst.sh
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Sr. Network Kernel Developer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2014-10-02 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 0:53 [PATCH v2 net-next] net: pktgen: packet bursting via skb->xmit_more Alexei Starovoitov
2014-10-01 1:57 ` Eric Dumazet
2014-10-01 8:16 ` Jesper Dangaard Brouer
2014-10-02 2:08 ` David Miller
2014-10-02 10:44 ` Jesper Dangaard Brouer [this message]
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=20141002124436.0d335b97@redhat.com \
--to=brouer@redhat.com \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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;
as well as URLs for NNTP newsgroup(s).