From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f173.google.com (mail-pf0-f173.google.com [209.85.192.173]) by dpdk.org (Postfix) with ESMTP id 28B2D7CCE for ; Thu, 1 Jun 2017 20:02:25 +0200 (CEST) Received: by mail-pf0-f173.google.com with SMTP id m17so33728593pfg.3 for ; Thu, 01 Jun 2017 11:02:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=7aRJKVRvI4a2MZDB3w23jcODS2WN8EyQp48iEoEdAfo=; b=Ya+eAuVKXWT9xOIPkPZPRpHLmtxLR7Ex5Mz1U5UkvnZ8fQIvcvwUBkSBF2zMovblMQ OUkHyRG0pG5VmHrcit9X2c557lkoWF6q/0ZIDBUL6yzykUQhdug6vkwI4v9/jMuVmN8C 0TLeDkHDqJv+Oa4QhT8+GQjeKueGxe21vDNZT+UMI+5RvK8lbab6i3unG0kmPuK6HLK3 WmqR8L8bwVLhYQDfzw21YOl1xyCxcZqjtf9Ja0D00SiNc+EJunLur3oEtsddYrBjXp5m rb+KASzqRUKl1FJarB3D45/YNsGHO9jhqvnaM2lGXQHZukkrw/2ZJxqeZ+NK82UOvw3o zG6g== 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:in-reply-to :references:mime-version:content-transfer-encoding; bh=7aRJKVRvI4a2MZDB3w23jcODS2WN8EyQp48iEoEdAfo=; b=t98bLKMvo+Yen8FJUsm2te7mDYSBUcbrhs0nyn5URFwURKdD8xPj9o3ek7PqAhD9wJ 0pojViFsBf3I16O6+BBR32H6OTw4nTRvhQWDncJAHSWArDyidyr+mNEp1J041qoo4JRy 1NZ4k5AMnCWqKxOX8mNBcew0BE6KpP9lJe09QR6n+NwItT5QfB8+XUW79NO8RB4LGuip KH+f4nS11Y2GISrFtsDzzWHn2/UHKyY4kLXICWcUgELYvk43+khg7rjRDD9zzZ1h7gXh 7TGYeP+b3LakV5w0lWwLzGR07yF4zlII70sYPQY7X26LwZVA/WLEdAIRHcrv5Mx/6pY6 LWaw== X-Gm-Message-State: AODbwcBtoIX6h2KlMTlg4o4HNlWx+02tLcJOu98JwTshMvW3zgSZxKPb yOlvtv62LOBQCI72 X-Received: by 10.99.174.77 with SMTP id e13mr2273257pgp.145.1496340144232; Thu, 01 Jun 2017 11:02:24 -0700 (PDT) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id p84sm33446487pfi.25.2017.06.01.11.02.24 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 01 Jun 2017 11:02:24 -0700 (PDT) Date: Thu, 1 Jun 2017 11:02:22 -0700 From: Stephen Hemminger To: =?UTF-8?B?R2HDq3Rhbg==?= Rivet Cc: dev@dpdk.org Message-ID: <20170601110222.246a0614@xeon-e3> In-Reply-To: <20170601142813.GE18840@bidouze.vm.6wind.com> References: <36220bb3757d1764d5c054f72bfa72193a91040a.1496065002.git.gaetan.rivet@6wind.com> <20170531082139.5ddce6d9@xeon-e3> <20170601142813.GE18840@bidouze.vm.6wind.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 18:02:25 -0000 On Thu, 1 Jun 2017 16:28:13 +0200 Ga=C3=ABtan Rivet wrote: > 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: > > =20 > > > 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 =20 > >=20 > > How does this interact with typical case of VF and dumb virtual device? > > The VF has flow API but dumb virtual device does not. > > =20 >=20 > 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. >=20 > 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. >=20 > > How does this work with late binding plugin? If VF arrives later is > > the flow table reprogrammed to the VF? =20 >=20 > 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. >=20 The synthetic path can't do flow direction in netvsc (and via tap). Therefo= re this whole flow direction part is uninteresting for the use case of Hyper-V/Azure.