From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44]) by dpdk.org (Postfix) with ESMTP id 4FF677CBD for ; Thu, 1 Jun 2017 16:28:20 +0200 (CEST) Received: by mail-wm0-f44.google.com with SMTP id n195so34727154wmg.1 for ; Thu, 01 Jun 2017 07:28:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=V4uPPaupPOxCER8vBiORsoE1LXNqzis9NBC4BuomFvI=; b=khykYbIQeuBQ9cad6rps0QRSEtfpYo/p+nbxITQg7FQT3D1vzFr4NKjUJoiEFC9WOM r/fh+KIA2gENrlLi+QwKaFkUoDlE8FJLAA5INEx0zgBZFHzpW0ruLjEhkFtKQePH/ZxV STeMWSw2kPQ4292zL7g2sJCD00DhnKhHbxygz+iI8D/euKjaYww7i3ICMMlQFN3NhofD HNaNAFxkC04nIy/80LXwj0ZJevqXxmyrCUL5AEGzQ8zV915sfWQbNd1GjGgNHCw2ji88 NLLQmDjxSYaJ6FpDhbX4JkHkm+mhC/C++m+rfGQUyf1QP6ypSGzF7n1GEPrKjyDtY37q BO3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=V4uPPaupPOxCER8vBiORsoE1LXNqzis9NBC4BuomFvI=; b=dtdh3IKvJ6kwJ0xYzkG7KVjUviITVLC/osr1tpRE4am56OGioIqTIadbt1Jw17+Y4D Y6w/Pz0BpxtxAOBXPeqbRy3uzTBbv9ix9rwIEiWn8H1XoAuZSDCkqgXf8WlCFQ6q/Keg Bsaq91rG1ngDPn+6kcoHEnnu9ETxX7yuu2apo0tKUdhG6dcpHGc7xjMAlnBzWhLOTHdR Ikndqpez+7ElvkPH2iJRQ/D9ONyBDXuz8mmJbZYgyXA3Sxwl3aPxQiQUfx+ftPVG1ZBN raONqzFpD/lFu/PGRsllYWSZovz78bBau9lEhoxkFG1t7WUHp01Z0xfCIFRNsApHrLDi X3dQ== X-Gm-Message-State: AODbwcDdSdoWO7XEJobOVr4WdEmhck8MeFkoTATKSEVrha1ZE+WB27RN Xh+og9x7UjbZD712 X-Received: by 10.223.161.198 with SMTP id v6mr1475978wrv.135.1496327299936; Thu, 01 Jun 2017 07:28:19 -0700 (PDT) Received: from bidouze.vm.6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id b8sm22241513wrb.7.2017.06.01.07.28.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Jun 2017 07:28:19 -0700 (PDT) Date: Thu, 1 Jun 2017 16:28:13 +0200 From: =?iso-8859-1?Q?Ga=EBtan?= Rivet To: Stephen Hemminger Cc: dev@dpdk.org Message-ID: <20170601142813.GE18840@bidouze.vm.6wind.com> References: <36220bb3757d1764d5c054f72bfa72193a91040a.1496065002.git.gaetan.rivet@6wind.com> <20170531082139.5ddce6d9@xeon-e3> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170531082139.5ddce6d9@xeon-e3> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v4 07/12] net/failsafe: support flow API X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 14:28:20 -0000 On Wed, May 31, 2017 at 08:21:39AM -0700, Stephen Hemminger wrote: > On Mon, 29 May 2017 15:42:19 +0200 > Gaetan Rivet wrote: > > > Signed-off-by: Gaetan Rivet > > Acked-by: Olga Shern > > --- > > doc/guides/nics/features/failsafe.ini | 1 + > > drivers/net/failsafe/Makefile | 1 + > > drivers/net/failsafe/failsafe.c | 1 + > > drivers/net/failsafe/failsafe_eal.c | 1 + > > drivers/net/failsafe/failsafe_ether.c | 70 +++++++++++ > > drivers/net/failsafe/failsafe_flow.c | 216 ++++++++++++++++++++++++++++++++ > > drivers/net/failsafe/failsafe_ops.c | 29 +++++ > > drivers/net/failsafe/failsafe_private.h | 18 +++ > > 8 files changed, 337 insertions(+) > > create mode 100644 drivers/net/failsafe/failsafe_flow.c > > How does this interact with typical case of VF and dumb virtual device? > The VF has flow API but dumb virtual device does not. > The fail-safe requires capabilities to be the same on all its slave. If a capability must be supported on the VF, then is should be as well on the synthetic path. But the TAP PMD that can be used to capture traffic from a synthetic path supports rte_flow in the same capacity as other NICs. > How does this work with late binding plugin? If VF arrives later is > the flow table reprogrammed to the VF? The fail-safe stores an internal representation of rte_flows. These are replayed in the same order upon plugin, so the flow table is reprogrammed in the same way to the VF. -- Gaëtan Rivet 6WIND