From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f169.google.com (mail-qk0-f169.google.com [209.85.220.169]) by dpdk.org (Postfix) with ESMTP id 3314C1396 for ; Mon, 26 Sep 2016 18:59:28 +0200 (CEST) Received: by mail-qk0-f169.google.com with SMTP id t7so169804056qkh.2 for ; Mon, 26 Sep 2016 09:59:28 -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=u+garEMqLBct6w8/fQI9NZdrcqXRvRxxQw10fY96osk=; b=jiVM25UJnFhJndMGJrmhq4Bh/cXxr/W3+tJRQx2VxDXOGVHlZKbNBUGF8iK3nH9kw9 SOMs0LduFfrEBDJhApLRG+c0epPsjNPYEnGLnTdjf5ptYMg0DQdpMN6GmqYU/aonby5X +eaI6VEP3kj/KVrxmRkqRolwWgbay61nIu/dogmzTA5DPsEhAxJBvrciFaEZDGt7B3eu rK/g5XuDVdQUn/ri/3TEiQpAY/JStZm13uY6v5QwSh9StHFNZsZ5sUuW0aS8jaLwLGFi j3jFC0xf9ivVVJhYeD+wxupyTjKwRQB5iNhoKkNq9wjsomd+wmCFaMjYjqS95DSMxSWt XRHA== 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=u+garEMqLBct6w8/fQI9NZdrcqXRvRxxQw10fY96osk=; b=QdlWwFfEDKVl7YXZeoMxqGSBr23YHMkNWrNx7cB84sQpfcXEn8bRKvjqHsCO/i55HF 7lvvj9pWD6sBSnNG0FDTUtPun7TQfrMHhKovzUzv1hDsHQq01Y7DsCRU+7wYx/W5RNLa OQZ5KJ6vgZVtTN/L90pj0XfBeQ4EFg2vAGhxDQtVhUeh49eiUsMIP5qkhknj5uEJvkkn Xa41tC5EJoVmOMpRUdSkFiIZ6NQBnNglw4nv9lt9+Y5ODNLZD+A7gGLtLwoM2/00pli6 NM2K7c10T4zKpee4K9jxPZN3eMDpIMDBkL7EvJ6hW2S8XSNqC6IOG1iqNgUw2odTka57 5KEQ== X-Gm-Message-State: AE9vXwNTBtv1DTB4W71C9GJavQjbBSweb1mAh7oAkp8ApnBw1D16m8CwbH+/drSff09v8XK5 X-Received: by 10.194.158.40 with SMTP id wr8mr18628862wjb.109.1474909167589; Mon, 26 Sep 2016 09:59:27 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id u185sm12124760wmu.20.2016.09.26.09.59.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Sep 2016 09:59:26 -0700 (PDT) From: Thomas Monjalon To: "Iremonger, Bernard" Cc: dev@dpdk.org, "Richardson, Bruce" , Jerin Jacob , "Shah, Rahul R" , "Lu, Wenzhuo" , azelezniak Date: Mon, 26 Sep 2016 18:59:26 +0200 Message-ID: <2212551.lClP9YTigq@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <8CEF83825BEC744B83065625E567D7C21A08D383@IRSMSX108.ger.corp.intel.com> References: <1471528125-26357-1-git-send-email-bernard.iremonger@intel.com> <8452736.eEWzj5BUlI@xps13> <8CEF83825BEC744B83065625E567D7C21A08D383@IRSMSX108.ger.corp.intel.com> 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: Mon, 26 Sep 2016 16:59:28 -0000 2016-09-26 15:37, Iremonger, Bernard: > Hi Thomas, Bruce, > > > > > Subject: Re: [dpdk-dev] [RFC PATCH v2 3/5] librte_ether: add API's for VF > > management > > > > 2016-09-23 17:02, Iremonger, Bernard: > > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > > > 2016-09-23 09:53, Richardson, Bruce: > > > > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > > > > > 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. > > > > > > > > > > Well, yes and no. The driver can manipulate things for the VF, but > > > > > DPDK > > > > doesn't actually have a device that corresponds to the VF. There are > > > > no PCI bar mappings for it, DPDK can't do RX and TX with it etc.? > > > > > > > > Very good point. > > > > There are only few ethdev functions which are supported by every > > > > drivers, like Rx/Tx and would not be available for VF from PF interface. > > > > > > > > > > > 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. > > > > > > > > > > While I see your point, and it could work, I just want to be sure > > > > > that we are > > > > ok with the results of that. Suppose we do create ethdevs for the > > > > VFs controlled by the PF. Does the new VF get counted in the > > > > rte_eth_dev_count() value (I assume yes)? How are apps meant to use > > > > the port? Do they have to put in a special case when iterating > > > > through all the port ids to check that it's not a pseudo port that > > > > can't do anything. None of the standard ethdev calls from an app > > > > will work on it, you can't configure nb rx/tx queues on it, you can't start or > > stop it, you can't do rx or tx on it, etc, etc. > > > > > > > > Yes these devices would be special because their supported API would > > > > be quite different. I was thinking that in the future you could add > > > > most of the configuration functions through the VF mailbox. > > > > But the Intel mailbox currently support only some special > > > > configurations which are not supported by other devices even its own > > > > VF device (except setting MAC address). > > > > And when I read "set drop enable bit in the VF split rx control > > > > register", it becomes clear it is really specific and has nothing to > > > > do in the generic ethdev API. > > > > That's why it is a NACK. > > > > > > > > When we want to use these very specific features we are aware of the > > > > underlying device and driver. So we can directly include a header > > > > from the driver. I suggest to retrieve a handler for the device > > > > which is not a port id and will allow to call ixgbe functions directly. > > > > It could be achieved by adding an ethdev function like discussed here: > > > > http://dpdk.org/ml/archives/dev/2016-September/047392.html > > > > > > > > > > I have been reading the net/vhost mail thread above. The following quote > > is from this thread. > > > > > > "It means I would be in favor of introducing API in drivers for very specific > > features." > > > > > > At present all the PMD functions are accessed through the eth_dev_ops > > structure, there are no PMD API's. > > > > > > Is your proposal to add API(s) to the DPDK ixgbe PMD (similar to a driver > > ioctl API) which can be accessed through a generic API in the ethdev? > > > > Not exactly. I'm thinking about a PMD specific API. > > The only ethdev API you need would be a function to retrieve a handler (an > > opaque pointer on the device struct) from the port id. > > Then you can include rte_ixgbe.h and directly call the specific ixgbe function, > > passing the device handler. > > How does it sound? > > I have been prototyping this proposed solution, it appears to work. > > I have added the following function: > > int rte_eth_dev_get_pmd_handle(uint8_t port_id, void** pmd_handle); > > The pmd_handle is a pointer to a dev_ops structure containing driver specific functions. > > Using the pmd_handle the driver specific functions can be called (without having them in struct eth_dev_ops) > > Has this proposal been superseded by the discussion on the following patch? > > [PATCH] net/vhost: Add function to retreive the 'vid' for a given port id Maybe, it can be superseded by this discussion, yes. Bruce thinks we do not need rte_eth_dev_get_pmd_handle(). What is your opinion about using port_id directly and retrieving the structs from the driver via rte_eth_devices?