From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v8 0/3] i40e: Add floating VEB support for i40e Date: Tue, 24 May 2016 12:22:21 -0700 Message-ID: <20160524122221.421bf2eb@xeon-e3> References: <1458895321-21896-1-git-send-email-zhe.tao@intel.com> <1464110886-9504-1-git-send-email-zhe.tao@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, jingjing.wu@intel.com To: Zhe Tao Return-path: Received: from mail-pf0-f172.google.com (mail-pf0-f172.google.com [209.85.192.172]) by dpdk.org (Postfix) with ESMTP id 50CA84AC7 for ; Tue, 24 May 2016 21:22:10 +0200 (CEST) Received: by mail-pf0-f172.google.com with SMTP id y69so9799041pfb.1 for ; Tue, 24 May 2016 12:22:10 -0700 (PDT) In-Reply-To: <1464110886-9504-1-git-send-email-zhe.tao@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, 25 May 2016 01:28:03 +0800 Zhe Tao wrote: > This patch-set add the support for floating VEB in i40e. > All the VFs VSIs can decide whether to connect to the legacy VEB/VEPA or > the floating VEB. When connect to the floating VEB a new floating VEB is > created. Now all the VFs need to connect to floating VEB or legacy VEB, > cannot connect to both of them. The PF and VMDQ,FD VSIs connect to > the old legacy VEB/VEPA. > > All the VEB/VEPA concepts are not specific for FVL, they are defined in the > 802.1Qbg spec. > > This floating VEB only take effects on the specific version F/W. > > Zhe Tao (3): > Support floating VEB config > Add floating VEB support in i40e > Add floating VEB extention support for i40e > > doc/guides/nics/i40e.rst | 10 ++ > doc/guides/rel_notes/release_16_07.rst | 6 + > drivers/net/i40e/i40e_ethdev.c | 205 +++++++++++++++++++++++++++++---- > drivers/net/i40e/i40e_ethdev.h | 9 ++ > drivers/net/i40e/i40e_pf.c | 12 +- > 5 files changed, 219 insertions(+), 23 deletions(-) > > V2: Added the release notes and changed commit log. > V3: Changed the VSI release operation. > V4: Added the FW version check otherwise it will cause the segment fault. > V5: Edited the code for new share code APIs > V6: Changed the floating VEB configuration method > V7: Added global reset for i40e > V7: removed global reset and added floating VEB extension support > kvargs are a very awkward API to use in a portable application. Good for Intel testing NIC's bad for DPDK users.