From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 537E725A1 for ; Mon, 23 Apr 2018 18:56:11 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9809221BF6; Mon, 23 Apr 2018 12:56:10 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 23 Apr 2018 12:56:10 -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; s=mesmtp; bh=suik62RADVEXI/AlCyjF4B6d/J y/IM6HggwV+cv0as8=; b=D7gGM3ksK9qfCfgO0PnGxury0R2iPaGoZziTEgZP7R yL3Dzgz0mLFoRPMrsmw3ah4FhsZ9Xm8jCZgdudoUT9IhoVSzGD5sPeS43S7wE5YX Ud13gpqHQtjtjDWzGbx1kLZjYB7lVA/nDCFe8d8QidXLQ/zvxObVBScx2JZM9NBX g= 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; s=fm2; bh=suik62 RADVEXI/AlCyjF4B6d/Jy/IM6HggwV+cv0as8=; b=YE8gcazYk1I3THhZUgZ8aH dwhnErkkLvPBdtgabaeykfH8ut2F2QfvL5OqTV4bZntJm5t9z9ZsTcWIQP8hkwK8 B2NSnqNxKP5/kwjq8D/p73v3Xn6ZBwWGZSdU6B7Jt3hGY3o78l/TrqlXPA8d2xLF BSGpnFM/X4zBcTt5oPiJIIOjaDDYc/2MH8M1C7A6BEd/+p9NXbyw/y1JfG4h/Bvp LswzrWl0NBUOOvPJQgrFXeXso99FiSrT2Gh0lEP7OwcGuQyZ80wRs4zKS3P9qu// ybtZGHfob93aw1Oc+pgFRlKMyFhtHrNoG3MAacJE4FVQySebnm1B9oSavJU2QTOA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 53C18E5097; Mon, 23 Apr 2018 12:56:09 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: Xueming Li , Wenzhuo Lu , Jingjing Wu , Adrien Mazarguil , Nelio Laranjeiro , Shahaf Shuler , dev@dpdk.org, Olivier Matz Date: Mon, 23 Apr 2018 18:56:08 +0200 Message-ID: <10812819.y0t78J1CiA@xps> In-Reply-To: References: <20180420115629.112472-1-xuemingl@mellanox.com> <20180423121635.32347-2-xuemingl@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v7 1/5] doc: remove RSS configuration change announcement 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: Mon, 23 Apr 2018 16:56:11 -0000 23/04/2018 18:13, Ferruh Yigit: > On 4/23/2018 1:16 PM, Xueming Li wrote: > > Remove deprecation as implementation of RSS level provided in Adrien's > > patch set: http://www.dpdk.org/dev/patchwork/patch/37399/ > > Why deprecation notice removed in this set if the implementation is in other > set, or am I missing something? If I remember well, Adrien is implementing with rte_flow, while the deprecation notice was for a different solution (legacy ethdev config). > > -* ethdev: A new rss level field planned in 18.05. > > - The new API add rss_level field to ``rte_eth_rss_conf`` to enable a choice > > - of RSS hash calculation on outer or inner header of tunneled packet.