From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: netdev@vger.kernel.org, BjörnTöpel <bjorn.topel@intel.com>,
magnus.karlsson@intel.com, eugenia@mellanox.com,
"John Fastabend" <john.fastabend@gmail.com>,
"Eran Ben Elisha" <eranbe@mellanox.com>,
"Saeed Mahameed" <saeedm@mellanox.com>,
galp@mellanox.com, "Daniel Borkmann" <borkmann@iogearbox.net>,
"Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
"Tariq Toukan" <tariqt@mellanox.com>,
brouer@redhat.com
Subject: Re: [bpf-next V2 PATCH 07/15] virtio_net: convert to use generic xdp_frame and xdp_return_frame API
Date: Fri, 9 Mar 2018 10:44:58 +0100 [thread overview]
Message-ID: <20180309104458.213a9914@redhat.com> (raw)
In-Reply-To: <323a325d-4eec-7a7a-efda-c0576a5b04ca@redhat.com>
On Fri, 9 Mar 2018 16:03:28 +0800
Jason Wang <jasowang@redhat.com> wrote:
> On 2018年03月08日 21:08, Jesper Dangaard Brouer wrote:
> > The virtio_net driver assumes XDP frames are always released based on
> > page refcnt (via put_page). Thus, is only queues the XDP data pointer
> > address and uses virt_to_head_page() to retrieve struct page.
> >
> > Use the XDP return API to get away from such assumptions. Instead
> > queue an xdp_frame, which allow us to use the xdp_return_frame API,
> > when releasing the frame.
> >
> > Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
> > ---
> > drivers/net/virtio_net.c | 31 +++++++++++++++++++++----------
> > 1 file changed, 21 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> > index 23374603e4d9..6c4220450506 100644
> > --- a/drivers/net/virtio_net.c
> > +++ b/drivers/net/virtio_net.c
> > @@ -419,30 +419,41 @@ static bool __virtnet_xdp_xmit(struct virtnet_info *vi,
> > struct xdp_buff *xdp)
> > {
> > struct virtio_net_hdr_mrg_rxbuf *hdr;
> > - unsigned int len;
> > + struct xdp_frame *xdpf, *xdpf_sent;
> > struct send_queue *sq;
> > + unsigned int len;
> > unsigned int qp;
> > - void *xdp_sent;
> > int err;
> >
> > qp = vi->curr_queue_pairs - vi->xdp_queue_pairs + smp_processor_id();
> > sq = &vi->sq[qp];
> >
> > /* Free up any pending old buffers before queueing new ones. */
> > - while ((xdp_sent = virtqueue_get_buf(sq->vq, &len)) != NULL) {
> > - struct page *sent_page = virt_to_head_page(xdp_sent);
> > + while ((xdpf_sent = virtqueue_get_buf(sq->vq, &len)) != NULL)
> > + xdp_return_frame(xdpf_sent->data, &xdpf_sent->mem);
> >
> > - put_page(sent_page);
> > - }
> > + xdpf = convert_to_xdp_frame(xdp);
> > + if (unlikely(!xdpf))
> > + return -EOVERFLOW;
> > +
> > + /* virtqueue want to use data area in-front of packet */
> > + if (unlikely(xdpf->metasize > 0))
> > + return -EOPNOTSUPP;
> > +
> > + if (unlikely(xdpf->headroom < vi->hdr_len))
> > + return -EOVERFLOW;
>
> I think this need another independent patch. For now we can simply drop
> the packet, but we probably need to think more to address it completely,
> allocate header part either dynamically or statically.
Okay, so we can followup later if we want to handle this case better
than drop.
> >
> > - xdp->data -= vi->hdr_len;
> > + /* Make room for virtqueue hdr (also change xdpf->headroom?) */
> > + xdpf->data -= vi->hdr_len;
> > /* Zero header and leave csum up to XDP layers */
> > - hdr = xdp->data;
> > + hdr = xdpf->data;
> > memset(hdr, 0, vi->hdr_len);
> > + hdr->hdr.hdr_len = xdpf->len; /* Q: is this needed? */
>
> Maybe another patch but not a must, hdr_len is hint for the linear part
> of skb used in host. Backend implementation may simply ignore this value.
So, I should leave it out for now?
Or it is okay to keep it?
> > + xdpf->len += vi->hdr_len;
> >
> > - sg_init_one(sq->sg, xdp->data, xdp->data_end - xdp->data);
> > + sg_init_one(sq->sg, xdpf->data, xdpf->len);
When _later_ introducing bulking, can we use something else than
sg_init_one() to send/queue multiple raw XDP frames for sending?
(I'm asking as I don't know this "sg_*" API usage)
> > - err = virtqueue_add_outbuf(sq->vq, sq->sg, 1, xdp->data,
> > GFP_ATOMIC);
> > + err = virtqueue_add_outbuf(sq->vq, sq->sg, 1, xdpf,
> > GFP_ATOMIC); if (unlikely(err))
> > return false; /* Caller handle free/refcnt */
> >
--
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:[~2018-03-09 9:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 13:07 [bpf-next V2 PATCH 00/15] XDP redirect memory return API Jesper Dangaard Brouer
2018-03-08 13:07 ` [bpf-next V2 PATCH 01/15] mlx5: basic XDP_REDIRECT forward support Jesper Dangaard Brouer
2018-03-08 13:07 ` [bpf-next V2 PATCH 02/15] xdp: introduce xdp_return_frame API and use in cpumap Jesper Dangaard Brouer
2018-03-09 7:24 ` Jason Wang
2018-03-09 9:35 ` Jesper Dangaard Brouer
2018-03-09 13:04 ` Jason Wang
2018-03-09 16:05 ` Jesper Dangaard Brouer
2018-03-16 8:43 ` Jason Wang
2018-03-08 13:07 ` [bpf-next V2 PATCH 03/15] ixgbe: use xdp_return_frame API Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 04/15] xdp: move struct xdp_buff from filter.h to xdp.h Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 05/15] xdp: introduce a new xdp_frame type Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 06/15] tun: convert to use generic xdp_frame and xdp_return_frame API Jesper Dangaard Brouer
2018-03-08 15:16 ` Jesper Dangaard Brouer
2018-03-09 7:16 ` Jason Wang
2018-03-09 8:46 ` Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 07/15] virtio_net: " Jesper Dangaard Brouer
2018-03-09 8:03 ` Jason Wang
2018-03-09 9:44 ` Jesper Dangaard Brouer [this message]
2018-03-09 13:11 ` Jason Wang
2018-03-08 13:08 ` [bpf-next V2 PATCH 08/15] bpf: cpumap convert to use generic xdp_frame Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 09/15] mlx5: register a memory model when XDP is enabled Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 10/15] xdp: rhashtable with allocator ID to pointer mapping Jesper Dangaard Brouer
2018-03-09 8:08 ` Jason Wang
2018-03-09 9:37 ` Jesper Dangaard Brouer
2018-03-09 13:07 ` Jason Wang
2018-03-09 16:07 ` Jesper Dangaard Brouer
2018-03-16 8:45 ` Jason Wang
2018-03-19 9:48 ` Jesper Dangaard Brouer
2018-03-20 2:26 ` Jason Wang
2018-03-20 14:27 ` Jesper Dangaard Brouer
2018-03-22 2:16 ` Jason Wang
2018-03-08 13:08 ` [bpf-next V2 PATCH 11/15] page_pool: refurbish version of page_pool code Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 12/15] xdp: allow page_pool as an allocator type in xdp_return_frame Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 13/15] mlx5: use page_pool for xdp_return_frame call Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 14/15] xdp: transition into using xdp_frame for return API Jesper Dangaard Brouer
2018-03-08 13:08 ` [bpf-next V2 PATCH 15/15] xdp: transition into using xdp_frame for ndo_xdp_xmit Jesper Dangaard Brouer
2018-03-08 15:03 ` [bpf-next V2 PATCH 00/15] XDP redirect memory return API Alexander Duyck
2018-03-08 15:30 ` Jesper Dangaard Brouer
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=20180309104458.213a9914@redhat.com \
--to=brouer@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=borkmann@iogearbox.net \
--cc=eranbe@mellanox.com \
--cc=eugenia@mellanox.com \
--cc=galp@mellanox.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.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).