From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2112CC2D0CE for ; Tue, 21 Jan 2020 21:28:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F0ECA24655 for ; Tue, 21 Jan 2020 21:28:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728827AbgAUV2f (ORCPT ); Tue, 21 Jan 2020 16:28:35 -0500 Received: from shards.monkeyblade.net ([23.128.96.9]:41742 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728776AbgAUV2f (ORCPT ); Tue, 21 Jan 2020 16:28:35 -0500 Received: from localhost (unknown [62.21.130.100]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 6631B158C30AC; Tue, 21 Jan 2020 13:28:33 -0800 (PST) Date: Tue, 21 Jan 2020 22:28:29 +0100 (CET) Message-Id: <20200121.222829.888926574980511328.davem@davemloft.net> To: haiyangz@microsoft.com Cc: sashal@kernel.org, linux-hyperv@vger.kernel.org, netdev@vger.kernel.org, kys@microsoft.com, sthemmin@microsoft.com, olaf@aepfle.de, vkuznets@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH V2,net-next, 1/2] hv_netvsc: Add XDP support From: David Miller In-Reply-To: References: <1579558957-62496-2-git-send-email-haiyangz@microsoft.com> <20200121.110454.2077433904156411260.davem@davemloft.net> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 21 Jan 2020 13:28:34 -0800 (PST) Sender: linux-hyperv-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-hyperv@vger.kernel.org From: Haiyang Zhang 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 > owner@vger.kernel.org> On Behalf Of David Miller >> Sent: Tuesday, January 21, 2020 5:05 AM >> To: Haiyang Zhang >> Cc: sashal@kernel.org; linux-hyperv@vger.kernel.org; netdev@vger.kernel.org; >> KY Srinivasan ; Stephen Hemminger >> ; olaf@aepfle.de; vkuznets >> ; linux-kernel@vger.kernel.org >> Subject: Re: [PATCH V2,net-next, 1/2] hv_netvsc: Add XDP support >> >> From: Haiyang Zhang >> 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.