From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by dpdk.org (Postfix) with ESMTP id 885DC569F for ; Fri, 23 Sep 2016 11:36:23 +0200 (CEST) Received: by mail-wm0-f45.google.com with SMTP id 197so4052275wmk.1 for ; Fri, 23 Sep 2016 02:36:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=5LwaO+LEd3gNLi64i4rsgV1ickgesqoCCs7PbUgHL7Q=; b=hsTrtivuF7DaaaBMrm9OzsjxWdAP2XaFouSNJxLRcD3yN8ETm/lDAwRRWY4lgayj3z EUWWJolT9dMJA7y1V2kjnVW4R6l0WTknV+0Pn8lyvYjjciO2a/Eyjdudip62ZRSvCZYM GtbJNdk/i45EJxPlHqrMyIONqcVsSo/ZKv1ieb9a08ooZqrEszy94B96XUunf2qXScci Q/Fr3HuPxyq3BKliBfStE9RsU5Tb2ShcBZeihqU0etW0tBNLMlvH3AKLectuGgq48vkV 2ZF9+xpzFsPcVMeAJfO7bEoB+wgML4PAFYXl/0ydXWWy70OtxsPr940uPWuKUfSXlDFh 3YWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=5LwaO+LEd3gNLi64i4rsgV1ickgesqoCCs7PbUgHL7Q=; b=lfn16bYtA1WH8k1POSIgbH38XVsCX/Kg5iEKLxFIFrWNaWX4gObtFh7ZgPTWAcr211 GXaS3SwJaDgXytpZxQr64HYRSn2ByL/nQyi7U+MmZ7/kdVIjOH32TyyxMxXpDZ7G8xmo aq1UjACgl0tUnFjjZnNgBRswvtuGSGQl5/9JBPqhCn92y+KB/OfjrzEtZ2iawd+UlCOa WxmdZ1gSeNyVXmYDeU/0aN/BC69NgrEM1t+8Rxe/Ds1+kPQfmqVoEjxFXnW1VOua6TcZ XKYleOHJWO6cA9XBvKyhVNvCzhphXS4/udA5CT8jLq8/ZhG/rysWpMRnHLZc9quKaj/7 Z4zA== X-Gm-Message-State: AA6/9Rn0I6VcHju8/2zpXRMZZW6MVY61WOB1g+9ETbMxJ6wFsyWVvNCnjJLEbch3mW09J781 X-Received: by 10.28.109.144 with SMTP id b16mr2019927wmi.19.1474623383341; Fri, 23 Sep 2016 02:36:23 -0700 (PDT) Received: from xps13.localnet (guy78-3-82-239-227-177.fbx.proxad.net. [82.239.227.177]) by smtp.gmail.com with ESMTPSA id vh6sm6335516wjb.0.2016.09.23.02.36.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Sep 2016 02:36:22 -0700 (PDT) From: Thomas Monjalon To: Bruce Richardson Cc: "Iremonger, Bernard" , dev@dpdk.org, Jerin Jacob , "Shah, Rahul R" , "Lu, Wenzhuo" , azelezniak Date: Fri, 23 Sep 2016 11:36:21 +0200 Message-ID: <3936536.tPp6g5Daih@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <20160923092048.GA58328@bricha3-MOBL3> References: <1471528125-26357-1-git-send-email-bernard.iremonger@intel.com> <3664576.rt1sgYQyhm@xps13> <20160923092048.GA58328@bricha3-MOBL3> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [RFC PATCH v2 3/5] librte_ether: add API's for VF management X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 09:36:23 -0000 2016-09-23 10:20, Bruce Richardson: > On Thu, Sep 22, 2016 at 07:04:37PM +0200, Thomas Monjalon wrote: > > 2016-09-15 16:46, Iremonger, Bernard: > > > > > > Do we really need to expose VF specific functions here? > > > > > > It can be generic(PF/VF) function indexed only through port_id. > > > > > > (example: as rte_eth_dev_set_vlan_anti_spoof(uint8_t port_id, > > > > > > uint8_t on)) For instance, In Thunderx PMD, We are not exposing a > > > > > > separate port_id for PF. We only enumerate 0..N VFs as 0..N ethdev > > > > > > port_id > > > > > > > > > > Our intention with this patch is to control the VF from the PF. > > > > > > > > > > The following librte_ether functions already work in a similar way: > > > > > > > > > > rte_eth_dev_set_vf_rxmode(uint8_t port_id, uint16_t vf, uint16_t > > > > > rx_mode, uint8_t on) > > > > > > > > > > rte_eth_dev_set_vf_rx(uint8_t port_id, uint16_t vf, uint8_t on) > > > > > > > > > > rte_eth_dev_set_vf_tx(uint8_t port_id, uint16_t vf, uint8_t on) > > > > > > > > > > int rte_eth_set_vf_rate_limit(uint8_t port_id, uint16_t vf, uint16_t > > > > > tx_rate, uint64_t q_msk) > > > > > > > > I have a bad feeling with these functions dedicated to VF from PF. > > > > Are we sure there is no other way? > > > > I mean we just need to know the VF with a port ID. > > > > > > When the VF is used in a VM the port ID of the VF is not visible to the PF. > > > I don't think there is another way to do this. > > > > I don't understand why we could not assign a port id to the VF from the > > host instead of having the couple PF port id / VF id. > > Can we enumerate all the VFs associated to a PF? > > Then can we allocate them a port id in the array rte_eth_devices? > > Hi Thomas, > > The VF is not a port visible to DPDK, though, so it shouldn't have a port id > IMHO. DPDK can't actually do anything with it. You say the contrary below. > The PCI device for the VF is likely passed through to a different VM and being > used there. Unfortunately, the VF still needs certain things done for it by the > PF, so if the PF is under DPDK control, it needs to provide the functionality > to assist the VF. Why not have a VF_from_PF driver which does the mailbox things? So you can manage the VF from the PF with a simple port id. It really seems to be the cleanest design to me.