From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: John Fastabend <john.fastabend@gmail.com>,
Jason Wang <jasowang@redhat.com>,
David Miller <davem@davemloft.net>,
John Fastabend <john.r.fastabend@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [net PATCH v5 1/6] virtio_net: use dev_kfree_skb for small buffer XDP receive
Date: Wed, 25 Jan 2017 16:52:52 +0200 [thread overview]
Message-ID: <20170125164844-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAADnVQ+O1tNuktnPgkL7JHZFBaQbWfxq0rjxPn86rsbRcteRyg@mail.gmail.com>
On Tue, Jan 24, 2017 at 11:33:56PM -0800, Alexei Starovoitov wrote:
> On Tue, Jan 24, 2017 at 8:02 PM, John Fastabend
> <john.fastabend@gmail.com> wrote:
> >
> > Finally just to point out here are the drivers with XDP support on latest
> > net tree,
> >
> > mlx/mlx5
> > mlx/mlx4
> > qlogic/qede
> > netronome/nfp
> > virtio_net
> >
> > And here is the list of adjust header support,
> >
> > mlx/mlx4
> >
>
> in net-next it's actually:
> yes: mlx4, mlx5
> no: qede, nfp, virtio
> while nfp and virtio are working on it.
>
> xdp_adjust_head() is must have for load balancer,
What amount of head space does it need? 70 bytes
to do vxlan kind of thing?
> so the sooner it lands for virtio the easier it will be
> to develop xdp programs. Initially I expected
> e1k+xdp to be the base line for debugging and
> development of xdp programs, but since not everyone
> agreed on e1k the virtio+xdp filled in the gap.
> So without adjust_head in virtio I see very little use for it
> in our environment.
> It is a must have feature regardless of timing.
> I will backport whatever is necessary, but distros
> will stick with official releases and imo it's not great
> from xdp adoption point of view to have
> virtio driver lacking key features.
If everyone can agree it's net-next material then I'm happy.
--
MST
next prev parent reply other threads:[~2017-01-25 14:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 7:33 [net PATCH v5 1/6] virtio_net: use dev_kfree_skb for small buffer XDP receive Alexei Starovoitov
2017-01-25 14:52 ` Michael S. Tsirkin [this message]
2017-01-25 15:52 ` John Fastabend
2017-01-25 22:56 ` [PATCH net resend] virtio_net: reject XDP programs using header adjustment Jakub Kicinski
2017-01-26 2:57 ` Jason Wang
2017-01-26 3:01 ` Michael S. Tsirkin
2017-01-26 3:49 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2017-01-17 22:19 [net PATCH v5 0/6] virtio_net XDP fixes and adjust_header support John Fastabend
2017-01-17 22:19 ` [net PATCH v5 1/6] virtio_net: use dev_kfree_skb for small buffer XDP receive John Fastabend
2017-01-18 15:48 ` Michael S. Tsirkin
2017-01-23 21:08 ` Michael S. Tsirkin
2017-01-23 21:57 ` John Fastabend
2017-01-24 19:43 ` David Miller
2017-01-24 20:08 ` Michael S. Tsirkin
2017-01-24 20:11 ` David Miller
2017-01-24 20:54 ` Michael S. Tsirkin
2017-01-25 2:57 ` Jason Wang
2017-01-25 3:23 ` Michael S. Tsirkin
2017-01-25 4:02 ` John Fastabend
2017-01-25 5:46 ` Jason Wang
2017-01-25 14:47 ` Michael S. Tsirkin
2017-01-25 14:45 ` Michael S. Tsirkin
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=20170125164844-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=john.r.fastabend@intel.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 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.