From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v4] ethdev: add isolated mode to flow API Date: Wed, 14 Jun 2017 23:33:21 +0200 Message-ID: <1756567.58yx1UZM0n@xps> References: <6ed2734fe0baa20cf993434d81375deb1f647179.1497444240.git.adrien.mazarguil@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Andrew Rybchenko To: Adrien Mazarguil Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 2104D2C00 for ; Wed, 14 Jun 2017 23:33:24 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 14/06/2017 17:41, Andrew Rybchenko: > On 06/14/2017 05:48 PM, Adrien Mazarguil wrote: > > Isolated mode can be requested by applications on individual ports to avoid > > ingress traffic outside of the flow rules they define. > > > > Besides making ingress more deterministic, it allows PMDs to safely reuse > > resources otherwise assigned to handle the remaining traffic, such as > > global RSS configuration settings, VLAN filters, MAC address entries, > > legacy filter API rules and so on in order to expand the set of possible > > flow rule types. > > > > To minimize code complexity, PMDs implementing this mode may provide > > partial (or even no) support for flow rules when not enabled (e.g. no > > priorities, no RSS action). Applications written to use the flow API are > > therefore encouraged to enable it. > > > > Once effective, leaving isolated mode may not be possible depending on PMD > > implementation. > > > > Signed-off-by: Adrien Mazarguil > > Acked-by: Nelio Laranjeiro > > Cc: Andrew Rybchenko > > Acked-by: Andrew Rybchenko Applied, thanks