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 68E00A00E6 for ; Sat, 10 Aug 2019 23:40:54 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8E3222B8C; Sat, 10 Aug 2019 23:40:53 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 58CD9231E for ; Sat, 10 Aug 2019 23:40:51 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C71DA207E1; Sat, 10 Aug 2019 17:40:50 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sat, 10 Aug 2019 17:40:50 -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=sIJtULU3Tcu4u58qJPrMta64ZQAO0Q0oS86c/dW2x3Q=; b=SMTH4+hPGPgC EIVs5eWaNWP1pcvyFXtyPQC50JKk4qKAIv4eAuc2BxtaVbueE725oz3RK/4vGf1H +J8tZ0PicvDeR/msKGIdma57D+p4GxiA3MpTBI4jKEarMKvZIJYQqAWRx0YvL8rm s/hNfmgOzNkySYlllaKEmHTpy0/wJ9Y= 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=sIJtULU3Tcu4u58qJPrMta64ZQAO0Q0oS86c/dW2x 3Q=; b=ELTWKE/LVF2LJkAPWHMaFvQgd7K/YICXy/XJ5Y54n6ENvdzdHww+Uhvqy knJwQlhqJmQyRToZhnfxlX3obnu4Dti0P0imddq7aZI0VXZH9LHa8uKCJLmiGRLq kqvlnNF6eyRu5P0ezzvxfJJfaWCC8Z08C6fAF07jjUINfE46lrfEZ4HmuS6x0cRb ddCjHEXP9IHOgH144Rlh1M18A6+pmvJL66BzGiwy5dH2s/qW6wVE26Egd2sjBl// cPRwJXvHDkJ+ZGna0/ctnbikmSoupi5IM6IHlQzCt02MbJzROkt613jeFxdFRLZZ tVQ41mmVfkgiyg264h30MnX+B7t2g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudduledgudeigecutefuodetggdotefrod 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 25309380075; Sat, 10 Aug 2019 17:40:49 -0400 (EDT) From: Thomas Monjalon To: Matan Azrad Cc: dev@dpdk.org, Andrew Rybchenko , Ferruh Yigit , Konstantin Ananyev , Olivier Matz Date: Sat, 10 Aug 2019 23:40:48 +0200 Message-ID: <3080600.NuWCTeAXad@xps> In-Reply-To: References: <1565103383-23864-1-git-send-email-matan@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 1/2] doc: announce ethdev ABI change for LRO fields 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" 06/08/2019 17:27, Andrew Rybchenko: > On 8/6/19 5:56 PM, Matan Azrad wrote: > > It may be needed by the user to limit the LRO session packet size. > > In order to allow the above limitation, a new Rx configuration may be > > added for the maximum LRO session size. > > > > A new capability may be added too to expose the maximum LRO session size > > supported by the port. > > > > Signed-off-by: Matan Azrad > > --- > > +* ethdev: new 32-bit fields may be added for maximum LRO session size, in > > + struct ``rte_eth_dev_info`` for the port capability and in struct > > + ``rte_eth_rxmode`` for the port configuration. > > Acked-by: Andrew Rybchenko > > I don't know examples when the information is required, but can imagine. Acked-by: Thomas Monjalon We have only 2 acks but as they are simple new fields, better to announce their addition in advance and allow for more discussion during 19.11 release cycle. Applied (only patch 1 of 2)