From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 052E47F for ; Thu, 3 Aug 2023 01:13:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EEB84C433C7; Thu, 3 Aug 2023 01:13:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1691025223; bh=jJx5NlEJLKyCLwr9/8OEo0e98eJF2aZClaXFa4XHZvY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=GWVryhR3cegQIPZhi4pK8Wuh6eHGmQcVEeM4jHapXb9w7SxMPpJEu6Y20Ck183RUt oxSG7VZi4zjgVgkLIxsybbtuZW1vGO5CQeDswiSGF3TBSg+VosYb6v6xncy471vtYO pYxy4g0Bq8D7RNaBazOAxaiCxCaLNqXgE07blEzLW+jWqC5sIS/M/G96XAzJF4tVPP d6ahZZfn635h7/qo3DoTQzFAcbfyr+/LGPkLRX0NwFQreRKW0OkviGcvydGxWTi0fT dD9TQbAFfLdE8l1tgMsTAK9LDfMz5673bs7cvexCTG15Cug5AaIUa8Y84GdXujEKtv AkJDIprE3G8VQ== Date: Wed, 2 Aug 2023 18:13:41 -0700 From: Jakub Kicinski To: Alexander Lobakin Cc: Ratheesh Kannoth , , , , , , , , , Subject: Re: [PATCH net] octeontx2-pf: Set maximum queue size to 16K Message-ID: <20230802181341.14cb2e4b@kernel.org> In-Reply-To: <18fec8cd-fc91-736e-7c01-453a18f4e9c5@intel.com> References: <20230802105227.3691713-1-rkannoth@marvell.com> <18fec8cd-fc91-736e-7c01-453a18f4e9c5@intel.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 2 Aug 2023 18:11:35 +0200 Alexander Lobakin wrote: > > - ring->rx_max_pending = Q_COUNT(Q_SIZE_MAX); > > + ring->rx_max_pending = 16384; /* Page pool support on RX */ > > This is very hardcodish. Why not limit the Page Pool size when creating > instead? It's perfectly fine to have a queue with 64k descriptors and a > Page Pool with only ("only" :D) 16k elements. > Page Pool size affects only the size of the embedded ptr_ring, which is > used for indirect (locking) recycling. I would even recommend to not go > past 2k for PP sizes, it makes no sense and only consumes memory. Should we make the page pool cap the size at 32k then, instead of having drivers do the gymnastics? I don't see what else the driver can do, other than cap :S -- pw-bot: cr