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 725DA1E1C11; Wed, 8 Apr 2026 01:51:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775613091; cv=none; b=UyfRUDMqQzZl5KmMHOsGE3LUHo5jP6bFPNXNTBpOtfRVF9X20fTwcV7bx8X51LARziOODYLnFrooDzIjLHzuGed1d6ArcDr2EZAy+pL8uDDN3i3MmzoYmtlZCz0ja9YZ9jTA6gJh5T8C5HhpWWDU7XL889sTTKa1le3zUxmrbnE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775613091; c=relaxed/simple; bh=fCBSQGqMzevTkcT7LslCcxFsnnfWHpPEEY4JITLJoI8=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=BBk3Iq2oywvYi3LztNLnOnVIUpCv+vqrlPOkURyA8ZO/NnWpKdAj/s+t+OXd6N+R2TFXpoQDLjJTNrnALvF5vyoQBSWYXUL8O+2ScoLX1qivXbE+geFqI2GKZuVj2GUZMpPGXBcVLiJbvv0NHBDvRq9k6sryjJFyNVU8k/7wsF4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=rmFT+Cq7; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="rmFT+Cq7" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6FC6EC116C6; Wed, 8 Apr 2026 01:51:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1775613091; bh=fCBSQGqMzevTkcT7LslCcxFsnnfWHpPEEY4JITLJoI8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=rmFT+Cq7dOHDzaGRk/uVDX5HCxAuPad+QD64QI+cQin3Ltrp4p9HFTqU3yloYEgLF p7FdoxIQwaY89/hwlM5EpDqSv98tk5ojAezjn0cxqMoAQFvRIzaeDz5VXmnBmdxHxi JsEX0uOoJ2oevc4aHYzF6eBWaPbu4JoT8XmZ3QEw1rA0PKKH0xpWlWsq4c8YmNC0Is 87qj9fr3YYji1yDHn/FMmAs+u/QbnuolbArIEW3yLl7nDd3CgQMTbbJIzjUQtSVv7d uoQlqRYjU9o+V3yMg44SCYEhvGhsNJjVBDKR8TfrHXMclAT4KgUorGpGuVE52bLBdv hetGX8PaMDIqA== Date: Tue, 7 Apr 2026 18:51:28 -0700 From: Jakub Kicinski To: Alexander Lobakin Cc: Dipayaan Roy , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH net-next v5 0/2] net: mana: add ethtool private flag for full-page RX buffers Message-ID: <20260407185128.605dcacf@kernel.org> In-Reply-To: References: 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 Tue, 7 Apr 2026 15:10:45 +0200 Alexander Lobakin wrote: > > On some ARM64 platforms with 4K PAGE_SIZE, utilizing page_pool > > fragments for allocation in the RX refill path (~2kB buffer per fragment) > > causes 15-20% throughput regression under high connection counts > > (>16 TCP streams at 180+ Gbps). Using full-page buffers on these > > platforms shows no regression and restores line-rate performance. > > > > This behavior is observed on a single platform; other platforms > > perform better with page_pool fragments, indicating this is not a > > page_pool issue but platform-specific. > > > > This series adds an ethtool private flag "full-page-rx" to let the > > user opt in to one RX buffer per page: > > > > ethtool --set-priv-flags eth0 full-page-rx on > > Sorry I may've missed the previous threads. > > Has this approach been discussed here? Private flags are generally > discouraged. > > Alternatively, you can provide Ethtool ops to change the Rx buffer size, > so that you'd be able to set it to PAGE_SIZE on affected platforms and > the result would be the same. Actually, hm. Now that you spoke up I wonder how much this is an inherent ARM problem vs problem in whatever ARM Microsoft's management empire-built themselves into. Do you have access to any ARM servers? Google says GCP offers ARM instances with idpf NICs. So if idpf benefits from the same "tuning" we should totally push for a proper API not priv flags.