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 8A4DCA057B; Tue, 14 Apr 2020 14:52:43 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5C9C71BED2; Tue, 14 Apr 2020 14:52:43 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id EC42B1C1E2; Tue, 14 Apr 2020 14:52:41 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 4144A5C028B; Tue, 14 Apr 2020 08:52:41 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Tue, 14 Apr 2020 08:52:41 -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=kZNdHfynir4ooUdknfShv3Yiyc81z18B73XTYunZjbU=; b=I9DcESv+Wxr/ 4rSwBrHoNmFBAgg94lJGdohYyG+8g5ICmyIrxzChsjJoU1vOEORQKLacdgm1Ur46 hK0KsZCAGCWFfGCsgy6fLDCIx+U1xil1olH/KuCgzKqPXJzic2GIJO1dU4K6aA23 fMu6LZajEjqIsRw/y5D/MtTAlsDo/Lw= 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=fm2; bh=kZNdHfynir4ooUdknfShv3Yiyc81z18B73XTYunZj bU=; b=bWmRBWOcUuiwIbGmCCg1sFd79zyoCavDG3eEK5WKPXZEXjIM+i+ekPluW 5fR7mnGhWei2YcRd4PwPE9U3wX6YQlMH9dlhzwibHaUar0lMKZwyRrvJo5ZcFIa7 xFVFDLKLBzAA8KsBXkdFQqT6LIA1zcf8F9P2Kv5VB+cJHyTBz0l9Po8jgogljv6e /0AQJvelc3KLBRWqpy11T/mKQQLOQlvIhf07M+4ljTVYG9uQMvEgcgPUMQCAkP+l QkINwTq2zJybX/yTSlYMnwrzyGDUj6hi/kZ03T3vvknq3OY9S3FJo47xF4rolJFk rBLFmIOu8vt+3EWRzsNynuQetrzCA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfedugdehjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth 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 DDBCF3060064; Tue, 14 Apr 2020 08:52:39 -0400 (EDT) From: Thomas Monjalon To: Alexander Kozyrev , Ferruh Yigit , Kevin Traynor , Luca Boccassi Cc: dev@dpdk.org, rasland@mellanox.com, matan@mellanox.com, viacheslavo@mellanox.com, stable@dpdk.org, David Marchand Date: Tue, 14 Apr 2020 14:52:38 +0200 Message-ID: <3469922.C4sosBPzcN@thomas> In-Reply-To: <9093c839-5655-6583-cc10-471a51ecccca@intel.com> References: <1585851108-485-1-git-send-email-akozyrev@mellanox.com> <1586471033-17130-2-git-send-email-akozyrev@mellanox.com> <9093c839-5655-6583-cc10-471a51ecccca@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 1/3] net/mlx5: add a devarg to specify MPRQ stride size 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" 14/04/2020 13:42, Ferruh Yigit: > On 4/9/2020 11:23 PM, Alexander Kozyrev wrote: > > Define a device parameter to configure log 2 of a stride size for MPRQ > > - mprq_log_stride_size. User is able to specify a stride size in a range > > allowed by an underlying hardware. The default stride size is defined as > > 2048 bytes to encompass most commonly used packet sizes in the Internet > > (MTU 1518 and less) and will be used in case a maximum configured packet > > size cannot fit into the largest possible stride size. Otherwise a > > stride size is set to a large enough value to encompass a whole packet. > > > > Cc: stable@dpdk.org > > Hi Alexander, > > This is a new feature, and you are asking it for to be backported to the stable > trees. > > There is no question on getting the fixes to the stable tree, but for > backporting features I would like to get the comment of the stable tree > maintainers first before merging the series. As far as I know, there is a fix hidden in this series, for the case of jumbo frames. In my understanding, jumbo frames cannot be fixed without a new option. I agree it's tricky deciding what is the limit with backports.