From: John Fastabend <john.fastabend@gmail.com>
To: daniel@iogearbox.net, mst@redhat.com, shm@cumulusnetworks.com,
davem@davemloft.net, tgraf@suug.ch, alexei.starovoitov@gmail.com
Cc: john.r.fastabend@intel.com, netdev@vger.kernel.org,
bblanco@plumgrid.com, brouer@redhat.com
Subject: Re: [net-next PATCH v4 5/6] virtio_net: add XDP_TX support
Date: Fri, 2 Dec 2016 19:10:09 -0800 [thread overview]
Message-ID: <58423791.4020802@gmail.com> (raw)
In-Reply-To: <20161202205122.4331.70274.stgit@john-Precision-Tower-5810>
On 16-12-02 12:51 PM, John Fastabend wrote:
> This adds support for the XDP_TX action to virtio_net. When an XDP
> program is run and returns the XDP_TX action the virtio_net XDP
> implementation will transmit the packet on a TX queue that aligns
> with the current CPU that the XDP packet was processed on.
>
> Before sending the packet the header is zeroed. Also XDP is expected
> to handle checksum correctly so no checksum offload support is
> provided.
>
> Signed-off-by: John Fastabend <john.r.fastabend@intel.com>
> ---
> drivers/net/virtio_net.c | 63 ++++++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 60 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> index b67203e..137caba 100644
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -330,12 +330,43 @@ static struct sk_buff *page_to_skb(struct virtnet_info *vi,
> return skb;
> }
>
> +static void virtnet_xdp_xmit(struct virtnet_info *vi,
> + unsigned int qnum, struct xdp_buff *xdp)
> +{
> + struct send_queue *sq = &vi->sq[qnum];
> + struct virtio_net_hdr_mrg_rxbuf *hdr;
> + unsigned int num_sg, len;
> + void *xdp_sent;
> + int err;
> +
> + /* Free up any pending old buffers before queueing new ones. */
> + while ((xdp_sent = virtqueue_get_buf(sq->vq, &len)) != NULL) {
> + struct page *page = virt_to_head_page(xdp_sent);
> +
> + put_page(page);
> + }
> +
> + /* Zero header and leave csum up to XDP layers */
> + hdr = xdp->data;
> + memset(hdr, 0, vi->hdr_len);
> +
> + num_sg = 1;
> + sg_init_one(sq->sg, xdp->data, xdp->data_end - xdp->data);
> + err = virtqueue_add_outbuf(sq->vq, sq->sg, num_sg,
> + xdp->data, GFP_ATOMIC);
> + if (unlikely(err))
> + put_page(virt_to_head_page(xdp->data));
> + else
> + virtqueue_kick(sq->vq);
> +}
> +
Hi Michael,
Any idea why the above pattern
> + err = virtqueue_add_outbuf(sq->vq, sq->sg, num_sg,
> + xdp->data, GFP_ATOMIC);
> + if (unlikely(err))
> + put_page(virt_to_head_page(xdp->data));
> + else
> + virtqueue_kick(sq->vq);
> +}
would cause a hang but if I call the virtqueue_kick as below
even in the error case everything seems to be fine.
err = virtqueue_add_outbuf(sq->vq, sq->sg, num_sg,
xdp->data, GFP_ATOMIC);
if (unlikely(err))
put_page(virt_to_head_page(xdp->data));
virtqueue_kick(sq->vq);
I'll take a look through the virtio code but thought I might ask in
case you know off-hand or it could be something else entirely.
I noticed virtio_input.c uses the second pattern and virtio_net.c
uses the above pattern but I'm guessing it never gets exercised due
to stack backoff.
Thanks,
John
next prev parent reply other threads:[~2016-12-03 3:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 20:49 [net-next PATCH v4 0/6] XDP for virtio_net John Fastabend
2016-12-02 20:49 ` [net-next PATCH v4 1/6] net: virtio dynamically disable/enable LRO John Fastabend
2016-12-04 4:01 ` David Miller
2016-12-04 5:36 ` Michael S. Tsirkin
2016-12-04 18:59 ` John Fastabend
2016-12-02 20:50 ` [net-next PATCH v4 2/6] net: xdp: add invalid buffer warning John Fastabend
2016-12-02 20:50 ` [net-next PATCH v4 3/6] virtio_net: Add XDP support John Fastabend
2016-12-02 20:50 ` [net-next PATCH v4 4/6] virtio_net: add dedicated XDP transmit queues John Fastabend
2016-12-02 20:51 ` [net-next PATCH v4 5/6] virtio_net: add XDP_TX support John Fastabend
2016-12-03 3:10 ` John Fastabend [this message]
2016-12-02 20:51 ` [net-next PATCH v4 6/6] virtio_net: xdp, add slowpath case for non contiguous buffers 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=58423791.4020802@gmail.com \
--to=john.fastabend@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bblanco@plumgrid.com \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.r.fastabend@intel.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shm@cumulusnetworks.com \
--cc=tgraf@suug.ch \
/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).