From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B3D2020D3F; Wed, 14 Jun 2017 17:33:23 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 14 Jun 2017 17:33:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=fkcp2tNVa/hXJfP HWXVdpjSYylPd/+SyZry8rV4+Wlk=; b=MP0iE69VHnQNAXRxvQkMvqm2uumFEq2 u64gqzqC4I5xDuzYx5t8RYB3n7tzmyRmS5pGSA9B1ugrZNwBpEojTvz4YHldUWcO xybiUUW9EaCGU+z+YX7O6rgOrOrMJH4nP8Ahg7+p28+MxgbATrCzFB0plcumEeQj JaJbR8gR1mhY= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=fkcp2tNVa/hXJfPHWXVdpjSYylPd/+SyZry8rV4+Wlk=; b=rfotcJcP mlEmrIzgfbSlhPBc3dCiHrWBScnyerOzNZuwwqBAlc00stKyIJbNM6+ZrqOIfdcF Pm19cEM1ih9ASl0OxlegEUaWXl2ax+i5WCUVt6+xYe0tv3x3Jqs8/mtUuSumGw52 2UIdqKnfcOyr7rh2mpDmAys4iDLyV+PZ7Njxwg1tqiShTsx5KjbSTqrZ7QBMxMgT D1pahTmRay2f7yYwX0tREmgJOB6byi7CNqE3PVgsD8pMJqfnGeAH5F3UUqxY3ldZ FkZkRicQq9xY0HYQuhV4Lu3/ao0isuIYuobuAgUf14KnfJwZBJ1FINUsJMEtz/4f sYocoTmlU9BhIg== X-ME-Sender: X-Sasl-enc: GvLJk2i7E7ddnNxkh0vw1am5p7oo4/SIujU3wA58Bl20 1497476003 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 3CAB07E6E5; Wed, 14 Jun 2017 17:33:23 -0400 (EDT) From: Thomas Monjalon To: Adrien Mazarguil Cc: dev@dpdk.org, Andrew Rybchenko Date: Wed, 14 Jun 2017 23:33:21 +0200 Message-ID: <1756567.58yx1UZM0n@xps> In-Reply-To: References: <6ed2734fe0baa20cf993434d81375deb1f647179.1497444240.git.adrien.mazarguil@6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4] ethdev: add isolated mode to 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: Wed, 14 Jun 2017 21:33:24 -0000 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