From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id AA41DA00E6 for ; Sat, 10 Aug 2019 23:10:33 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 612C62A6A; Sat, 10 Aug 2019 23:10:32 +0200 (CEST) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by dpdk.org (Postfix) with ESMTP id D52D6DE3 for ; Sat, 10 Aug 2019 23:10:30 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 6262F1A34; Sat, 10 Aug 2019 17:10:30 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sat, 10 Aug 2019 17:10:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=zRocLyEROVKT+y42L42CdVtCAoVapRjPRtVOliDmijw=; b=SF+BtGjIP1f3 C2uVN92SUJo9XhSvddMsRyFnCQu3vvPEsNFiGKdtwBv1qXwiRiPqz8z3Y5BscG2b WJfe+RZ0NoLJ4bNvIQYbSmVInRIUJSSnfrNAZQVDyFyGpUp+wZzwZAfjLtC4fFij yZpGezbaMuCeBp85i2LXb/ScnYUS8RI= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=zRocLyEROVKT+y42L42CdVtCAoVapRjPRtVOliDmi jw=; b=VjYS7G77UBIK7WJ5rm0eoqUiH7/sEEV0HI1h4Wp0v9IgpMI1NmpVci7Ua IBROaOujmGSHC+fVRr9DukjpTdbysLi18c31a7qCZNwrNeTVBA4Xh3D2JGYEmjOh fI/9+zbo6MPpAmT1r+CXkWFEuKcl8+KrmDIEeafucPGemm7ATECzJNjMqgAZ8JUP 04nhQTJ23OHx+3fVSMWsBmLS7lJkmZkgfBL5M+ZBmzS8EqG1mcEXywQQK/+WT48C Rb7nRw0yHPHvhpiI+HBcoGpwKF0MJ94s6ImgffD/JRHr9TGmdZRRVScTEs75COYM z2CtO3GRzbnKUboN96zI3eHzXN6FA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudduledgudehkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc fkphepjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpeht hhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 25195380075; Sat, 10 Aug 2019 17:10:28 -0400 (EDT) From: Thomas Monjalon To: "pbhagavatula@marvell.com" Cc: dev@dpdk.org, "Ananyev, Konstantin" , "jerinj@marvell.com" , "stephen@networkplumber.org" , "arybchenko@solarflare.com" , "hemant.agrawal@nxp.com" , "Yigit, Ferruh" , "Richardson, Bruce" , Neil Horman , "Mcnamara, John" , "Kovacevic, Marko" Date: Sat, 10 Aug 2019 23:10:27 +0200 Message-ID: <5809087.tckKttxGng@xps> In-Reply-To: <2601191342CEEE43887BDE71AB9772580168A64198@irsmsx105.ger.corp.intel.com> References: <20190809081740.1607-1-pbhagavatula@marvell.com> <20190809095559.1900-1-pbhagavatula@marvell.com> <2601191342CEEE43887BDE71AB9772580168A64198@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [patch v5] doc: announce API change in ethdev offload flags 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > > Add new offload flags ``DEV_RX_OFFLOAD_RSS_HASH`` and > > ``DEV_RX_OFFLOAD_FLOW_MARK``. > > Add new function ``rte_eth_dev_set_supported_ptypes`` to allow application > > to set specific ptypes to be updated in ``rte_mbuf::packet_type`` > > > > Signed-off-by: Pavan Nikhilesh > > Acked-by: Andrew Rybchenko > > Acked-by: Jerin Jacob > > Acked-by: Hemant Agrawal > Acked-by: Konstantin Ananyev We'll probably have to discuss more the details of these new APIs, but the overall idea looks good. I am not sure there is any API or ABI breakage here, so the announce may not be required. Anyway applied, thanks.