From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6DC1242D83; Wed, 28 Jun 2023 21:07:19 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EC1DB406B3; Wed, 28 Jun 2023 21:07:18 +0200 (CEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by mails.dpdk.org (Postfix) with ESMTP id 9629E40151 for ; Wed, 28 Jun 2023 21:07:17 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 207F532002F9; Wed, 28 Jun 2023 15:07:14 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 28 Jun 2023 15:07:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1687979233; x=1688065633; bh=C+QaGtmk1Yo5v6jVKwQczbLJ3w+JbK/TFyQ Y24UoAXk=; b=VcybcXXyacw4jICZ1jLYmK4D8lrR6Ep5KA3dSk2b6ifqz8cMWXO Ikcx9GOyuLybVadFh1kSqBnqlMeywBnxMawv9KYU5A4TA7RB3H+Mtjg2E3RB8NnD fJMRxbWtEhJmhdVxOVDDanNPjEEtHfES0KYvBWdrJkwo2sOkYv4Qpgue4VL1iP8I Gina9E6GRupoAg8fe6Bc67VeSC2MkkXf4ou2F7eeXkdRJk49HvKwNU3Ki5Tfjy48 8VTSrVABwfxmjuyMsOUniyiyNZwy7SgFuqZ5TNs7V6ZneeMGub6vEiFKodEPDtC2 s99P346Sep8bBMz3sdAuFIIB2u/a71MOGuQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1687979233; x=1688065633; bh=C+QaGtmk1Yo5v6jVKwQczbLJ3w+JbK/TFyQ Y24UoAXk=; b=e47Nsn1NHwD0wbOw4F0TFU6Ha40vdkJBM36H312Z514fBti0N4W ZTCtlnSHcpHo5hJb6x5hG39tJ2YHNzql7LJtpYVTVnB76/MHHqUWtjYSKAkMmQ/r UqGOoGZbGoH0kRxY1J9YtGBmY+0Opz3CybZrX1UsOdUfx1NnplraPeKapHTz5mko 14k9yHQ9SDYl1jWV6OPK9Xgc4zLn5tGgmYIv0Y2fPiQCFWsWrKF1h6KGo6FcKMXP D5ReGAMCy86VxMd+z/fd3QGIQO4KZtN0lbJqlQzSSDIN9hFrvJM1wArEjycEyN7+ +V+X7GzxDwUXyCFO+jRdU1D96YYNSog3emQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrtddvgddufedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeegtddtleejjeegffekkeektdejvedtheevtdekiedvueeuvdei uddvleevjeeujeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 28 Jun 2023 15:07:12 -0400 (EDT) From: Thomas Monjalon To: Ajit Khaparde Cc: Randy Schacher , Farah Smith , Shahaji Bhosle , dev@dpdk.org, david.marchand@redhat.com Subject: Re: [PATCH v3 04/11] net/bnxt: update Truflow core Date: Wed, 28 Jun 2023 21:07:10 +0200 Message-ID: <1708454.izSxrag8PF@thomas> In-Reply-To: References: <20230504173612.17696-1-ajit.khaparde@broadcom.com> <1826961.atdPhlSkOF@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 28/06/2023 18:35, Ajit Khaparde: > On Sat, Jun 10, 2023 at 11:33=E2=80=AFAM Thomas Monjalon wrote: > > More important, you are doing huge update of many different things > > in one patch. > > It looks like you don't want the community to follow what you are doing. > Actually, no. > As I mentioned above, most of the truflow files are auto generated. > The reason for bundling some of the changes together was to avoid > multiple patches hitting the mail server patch size limit. > We thought it might be better to take the patch size hit on one patch > instead of multiple patches. I don't see how it is better to have one huge patch than multiple big ones. >=20 > We are working on some design changes to the auto generation scripts > which will avoid big churn in the template patches in the future.