From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: brouer@redhat.com, John Fastabend <john.fastabend@gmail.com>,
bblanco@plumgrid.com, davem@davemloft.net,
alexei.starovoitov@gmail.com, john.r.fastabend@intel.com,
netdev@vger.kernel.org, xiyou.wangcong@gmail.com
Subject: Re: [net-next PATCH] e1000: add initial XDP support
Date: Mon, 29 Aug 2016 10:30:47 +0200 [thread overview]
Message-ID: <20160829103047.3968a4d8@redhat.com> (raw)
In-Reply-To: <b6cfb3c5-9c68-3ea7-48dd-7fbf666db751@mojatatu.com>
On Sun, 28 Aug 2016 08:23:26 -0400
Jamal Hadi Salim <jhs@mojatatu.com> wrote:
> On 16-08-27 03:11 AM, John Fastabend wrote:
> > From: Alexei Starovoitov <ast@fb.com>
> >
> > This patch adds initial support for XDP on e1000 driver. Note e1000
> > driver does not support page recycling in general which could be
> > added as a further improvement. However for XDP_DROP and XDP_XMIT
> > the xdp code paths will recycle pages.
> >
> > This patch includes the rcu_read_lock/rcu_read_unlock pair noted by
> > Brenden Blanco in another pending patch.
> >
> > net/mlx4_en: protect ring->xdp_prog with rcu_read_lock
>
> Do you have any perf numbers of drops of this vs tc drop at ingress?
Hi Jamal,
Can you please provide a simple "tc" command that implements "tc drop"?
Then, I'll add this to the series of tests I'm using for (what I call)
"zoom-in" benchmarking.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2016-08-29 8:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 7:11 [net-next PATCH] e1000: add initial XDP support John Fastabend
2016-08-28 5:55 ` Or Gerlitz
2016-08-29 5:33 ` John Fastabend
2016-08-28 12:23 ` Jamal Hadi Salim
2016-08-29 8:30 ` Jesper Dangaard Brouer [this message]
2016-08-29 10:53 ` Jamal Hadi Salim
2016-08-29 13:39 ` Jesper Dangaard Brouer
2016-08-29 15:55 ` Jesper Dangaard Brouer
2016-08-30 12:13 ` Jamal Hadi Salim
2016-08-30 13:31 ` Jesper Dangaard Brouer
2016-09-01 21:35 ` John Fastabend
2016-09-01 19:33 ` John Fastabend
2016-08-28 15:56 ` William Tu
2016-08-29 5:36 ` John Fastabend
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=20160829103047.3968a4d8@redhat.com \
--to=brouer@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bblanco@plumgrid.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=john.fastabend@gmail.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).