From: Haiyang Zhang <haiyangz@microsoft.com>
To: David Miller <davem@davemloft.net>
Cc: "sashal@kernel.org" <sashal@kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
KY Srinivasan <kys@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
"olaf@aepfle.de" <olaf@aepfle.de>, vkuznets <vkuznets@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH V2,net-next, 1/2] hv_netvsc: Add XDP support
Date: Wed, 22 Jan 2020 02:12:19 +0000 [thread overview]
Message-ID: <MN2PR21MB1375DBB53EBFC15229B6ED52CA0C0@MN2PR21MB1375.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20200121.222829.888926574980511328.davem@davemloft.net>
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org <linux-kernel-
> owner@vger.kernel.org> On Behalf Of David Miller
> Sent: Tuesday, January 21, 2020 4:28 PM
> To: Haiyang Zhang <haiyangz@microsoft.com>
> Cc: sashal@kernel.org; linux-hyperv@vger.kernel.org; netdev@vger.kernel.org;
> KY Srinivasan <kys@microsoft.com>; Stephen Hemminger
> <sthemmin@microsoft.com>; olaf@aepfle.de; vkuznets
> <vkuznets@redhat.com>; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH V2,net-next, 1/2] hv_netvsc: Add XDP support
>
> From: Haiyang Zhang <haiyangz@microsoft.com>
> Date: Tue, 21 Jan 2020 18:53:28 +0000
>
> > Sorry I was replying too quickly. See more detailed explanation below.
> >
> >> -----Original Message-----
> >> From: linux-hyperv-owner@vger.kernel.org <linux-hyperv-
> >> owner@vger.kernel.org> On Behalf Of David Miller
> >> Sent: Tuesday, January 21, 2020 5:05 AM
> >> To: Haiyang Zhang <haiyangz@microsoft.com>
> >> Cc: sashal@kernel.org; linux-hyperv@vger.kernel.org;
> >> netdev@vger.kernel.org; KY Srinivasan <kys@microsoft.com>; Stephen
> >> Hemminger <sthemmin@microsoft.com>; olaf@aepfle.de; vkuznets
> >> <vkuznets@redhat.com>; linux-kernel@vger.kernel.org
> >> Subject: Re: [PATCH V2,net-next, 1/2] hv_netvsc: Add XDP support
> >>
> >> From: Haiyang Zhang <haiyangz@microsoft.com>
> >> Date: Mon, 20 Jan 2020 14:22:36 -0800
> >>
> >> > +u32 netvsc_run_xdp(struct net_device *ndev, struct netvsc_channel
> *nvchan,
> >> > + struct xdp_buff *xdp)
> >> > +{
> >> > + struct page *page = NULL;
> >> > + void *data = nvchan->rsc.data[0];
> >> > + u32 len = nvchan->rsc.len[0];
> >> > + struct bpf_prog *prog;
> >> > + u32 act = XDP_PASS;
> >>
> >> Please use reverse christmas tree ordering of local variables.
> > Will do.
> >
> >>
> >> > + 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);
> >>
> >> Why can't the program run directly on nvchan->rsc.data[0]?
> >
> > The Azure/Hyper-V synthetic NIC receive buffer doesn't provide
> > headroom for XDP. We thought about re-use the RNDIS header space, but
> > it's too small. So we decided to copy the packets to a page buffer for
> > XDP. And, most of our VMs on Azure have Accelerated Network (SRIOV)
> > enabled, so most of the packets run on VF NIC. The synthetic NIC is
> > considered as a fallback data-path. So the data copy on netvsc won't
> > impact performance significantly.
>
> You need to explain this in your commit message otherwise every reviewer
> with XDP expertiece will ask the same question.
Will do.
Thanks,
- Haiyang
next prev parent reply other threads:[~2020-01-22 2:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 22:22 [PATCH V2,net-next, 0/2] hv_netvsc: Add XDP support Haiyang Zhang
2020-01-20 22:22 ` [PATCH V2,net-next, 1/2] " Haiyang Zhang
2020-01-21 10:04 ` David Miller
2020-01-21 13:56 ` Haiyang Zhang
2020-01-21 18:53 ` Haiyang Zhang
2020-01-21 21:28 ` David Miller
2020-01-22 2:12 ` Haiyang Zhang [this message]
2020-01-20 22:22 ` [PATCH V2,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=MN2PR21MB1375DBB53EBFC15229B6ED52CA0C0@MN2PR21MB1375.namprd21.prod.outlook.com \
--to=haiyangz@microsoft.com \
--cc=davem@davemloft.net \
--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).