From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: brouer@redhat.com, sashal@kernel.org,
linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
kys@microsoft.com, sthemmin@microsoft.com, olaf@aepfle.de,
vkuznets@redhat.com, davem@davemloft.net,
linux-kernel@vger.kernel.org,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH V3,net-next, 1/2] hv_netvsc: Add XDP support
Date: Wed, 22 Jan 2020 20:51:33 +0100 [thread overview]
Message-ID: <20200122205133.00688f7c@carbon> (raw)
In-Reply-To: <1579713814-36061-2-git-send-email-haiyangz@microsoft.com>
On Wed, 22 Jan 2020 09:23:33 -0800
Haiyang Zhang <haiyangz@microsoft.com> wrote:
> +u32 netvsc_run_xdp(struct net_device *ndev, struct netvsc_channel *nvchan,
> + struct xdp_buff *xdp)
> +{
> + void *data = nvchan->rsc.data[0];
> + u32 len = nvchan->rsc.len[0];
> + struct page *page = NULL;
> + struct bpf_prog *prog;
> + u32 act = XDP_PASS;
> +
> + xdp->data_hard_start = NULL;
> +
> + rcu_read_lock();
> + prog = rcu_dereference(nvchan->bpf_prog);
> +
> + if (!prog)
> + goto out;
> +
> + /* allocate page buffer for data */
> + page = alloc_page(GFP_ATOMIC);
The alloc_page() + __free_page() alone[1] cost 231 cycles(tsc) 64.395 ns.
Thus, the XDP_DROP case will already be limited to just around 10Gbit/s
14.88 Mpps (67.2ns).
XDP is suppose to be done for performance reasons. This looks like a
slowdown.
Measurement tool:
[1] https://github.com/netoptimizer/prototype-kernel/blob/master/kernel/mm/bench/page_bench01.c
> + if (!page) {
> + act = XDP_DROP;
> + goto out;
> + }
> +
> + xdp->data_hard_start = page_address(page);
> + xdp->data = xdp->data_hard_start + NETVSC_XDP_HDRM;
> + xdp_set_data_meta_invalid(xdp);
> + xdp->data_end = xdp->data + len;
> + xdp->rxq = &nvchan->xdp_rxq;
> + xdp->handle = 0;
> +
> + memcpy(xdp->data, data, len);
And a memcpy.
> +
> + act = bpf_prog_run_xdp(prog, xdp);
> +
> + switch (act) {
> + case XDP_PASS:
> + case XDP_TX:
> + case XDP_DROP:
> + break;
> +
> + case XDP_ABORTED:
> + trace_xdp_exception(ndev, prog, act);
> + break;
> +
> + default:
> + bpf_warn_invalid_xdp_action(act);
> + }
> +
> +out:
> + rcu_read_unlock();
> +
> + if (page && act != XDP_PASS && act != XDP_TX) {
> + __free_page(page);
Given this runs under NAPI you could optimize this easily for XDP_DROP
(and XDP_ABORTED) by recycling the page in a driver local cache. (The
page_pool also have a driver local cache build in, but it might be
overkill to use page_pool in this simple case).
You could do this in a followup patch.
> + xdp->data_hard_start = NULL;
> + }
> +
> + return act;
> +}
--
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:[~2020-01-22 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 17:23 [PATCH V3,net-next, 0/2] hv_netvsc: Add XDP support Haiyang Zhang
2020-01-22 17:23 ` [PATCH V3,net-next, 1/2] " Haiyang Zhang
2020-01-22 19:51 ` Jesper Dangaard Brouer [this message]
2020-01-22 20:29 ` Haiyang Zhang
2020-01-23 16:59 ` Jakub Kicinski
2020-01-23 17:14 ` Haiyang Zhang
2020-01-23 17:30 ` Jakub Kicinski
2020-01-23 17:44 ` Haiyang Zhang
2020-01-22 17:23 ` [PATCH V3,net-next, 2/2] hv_netvsc: Update document for " Haiyang Zhang
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=20200122205133.00688f7c@carbon \
--to=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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).