From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: xdp-newbies@vger.kernel.org, netdev@vger.kernel.org,
andy@greyhouse.net, brouer@redhat.com
Subject: Re: Blogpost evaluation this [PATCH v4 net-next RFC] net: Generic XDP
Date: Tue, 25 Apr 2017 10:28:57 +0200 [thread overview]
Message-ID: <20170425102857.6f71c082@redhat.com> (raw)
In-Reply-To: <20170424.182643.485613135674690555.davem@davemloft.net>
On Mon, 24 Apr 2017 18:26:43 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> From: Jesper Dangaard Brouer <brouer@redhat.com>
> Date: Mon, 24 Apr 2017 16:24:05 +0200
>
> > I've done a very detailed evaluation of this patch, and I've created a
> > blogpost like report here:
> >
> > https://prototype-kernel.readthedocs.io/en/latest/blogposts/xdp25_eval_generic_xdp_tx.html
>
> Thanks for doing this Jesper.
>
> > I didn't evaluate the adjust_head part, so I hope Andy is still
> > planning to validate that part?
>
> I was hoping he would post some results today as well.
>
> Andy, how goes it? :)
>
> Once the basic patch is ready and integrated in we can try to do
> xmit_more in generic XDP and see what that does for XDP_TX
> performance.
I agree, we can do xmit_more for generic-XDP later, and it should not
be that hard... basically replacing netdev_start_xmit() with
dev_hard_start_xmit() in generic_xdp_tx(), and finding some place to
store a XDP-skb-pointer (functioning as the skb-list) that will be
"flushed" like __kfree_skb_flush().
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2017-04-25 8:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 16:09 [PATCH v4 net-next RFC] net: Generic XDP David Miller
2017-04-13 20:16 ` Michael Chan
2017-04-13 20:23 ` David Miller
2017-04-14 1:59 ` [lkp-robot] [net] d1dff7db3b: net/core/dev.c:#suspicious_rcu_dereference_check()usage kernel test robot
2017-04-14 1:59 ` kernel test robot
2017-04-15 0:59 ` [PATCH v4 net-next RFC] net: Generic XDP Alexei Starovoitov
2017-04-15 15:46 ` David Ahern
2017-04-18 19:05 ` Andy Gospodarek
2017-04-18 19:07 ` David Miller
2017-04-18 19:29 ` David Miller
2017-04-18 19:37 ` Andy Gospodarek
2017-04-19 14:29 ` Andy Gospodarek
2017-04-19 17:17 ` Alexei Starovoitov
2017-04-19 17:44 ` John Fastabend
2017-04-19 20:25 ` Andy Gospodarek
2017-04-20 0:13 ` Alexei Starovoitov
2017-04-20 1:40 ` David Miller
2017-04-20 22:09 ` Andy Gospodarek
2017-04-20 14:30 ` Jesper Dangaard Brouer
2017-04-24 13:18 ` Jesper Dangaard Brouer
2017-04-18 20:26 ` Jesper Dangaard Brouer
2017-04-14 16:33 ` William Tu
2017-04-24 14:24 ` Blogpost evaluation this " Jesper Dangaard Brouer
2017-04-24 22:26 ` David Miller
2017-04-25 8:28 ` Jesper Dangaard Brouer [this message]
2017-04-25 17:25 ` Andy Gospodarek
2017-04-25 17:31 ` David Miller
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=20170425102857.6f71c082@redhat.com \
--to=brouer@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=xdp-newbies@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.