From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 33D0DC433F5 for ; Thu, 5 May 2022 18:09:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=PMFYj63xz17Wee51W3LrLbJXhGiNamv4Q0+Np92RGWU=; b=P+T1icU3SsoXUK kl7nVg/gsLeV8/E7TNOtw1BAW1u1LoGDrfU4UbGQMXEJzReJZQlbHa31ZoElC6flDytDqLW5ACgmg AkwHrwlTAwsXbENhAXK1UF3ct0BuXqh80xR1ZPySVsizfjMOVh08MT7SvcHEPHijr9rShyfVNuPxQ Z3X9nZT+T48ZwUVLojW/cP2AL63EEQULFxs8qdwwy9VIN/xboWN/V5zXv8xUUHqyB7aE/vzo3jO0m GUpeZx7L4Eb3Es9Ef1PD7ghP/OicLZu/m8V98RvbP2PwfX5epIwb8dt1uiThcEMreDmz2sUj2QF/f UwtKlsSg47KeeByqOM3g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nmftr-00HEof-SI; Thu, 05 May 2022 18:08:27 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nmfto-00HEmL-As for linux-arm-kernel@lists.infradead.org; Thu, 05 May 2022 18:08:25 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 59B6061EEB; Thu, 5 May 2022 18:08:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6763DC385A4; Thu, 5 May 2022 18:08:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1651774099; bh=o1D9W3mV4nlOFvs/Rd77CWl4QI0upM7ggMCpojlvSas=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=n0GdqlXT8vlY/pkauwl80J2AMHZrHfcndVEYOFcMNzQSFAR1t640sY7vJ/O2TWfli GcroCF6NRbx2cE2vmB/vFx7rzdGGZCRSw+ME71ZPjL6sz45KgGjU4G06KrEE7cefpH y3/KuvUSWpkfrGdVfszh6GHmUPlJGg+VEdhoSeH0MjzTtTokn4+RTbSRqH955VPqvC 3I2YmXHfRdb6wnuC2gDVr8sX4kleDPo+4MEV10NQgSZtSG7zaNp1NmFX6M4Pii7XPA xJLeGk+gtfbRq6yeDGIV89ulTbC7u/cjS/jVWa0gWUMh2RLRlW1IHtGhlVe7ptp35w G36YhscgVHIBw== Date: Thu, 5 May 2022 11:08:17 -0700 From: Jakub Kicinski To: Robert Hancock Cc: "radheys@xilinx.com" , "linux-arm-kernel@lists.infradead.org" , "netdev@vger.kernel.org" , "davem@davemloft.net" , "michals@xilinx.com" , "pabeni@redhat.com" , "edumazet@google.com" , "harinik@xilinx.com" Subject: Re: [PATCH net-next] net: axienet: Use NAPI for TX completion path Message-ID: <20220505110817.74938ad8@kernel.org> In-Reply-To: <5376cbf00c18487b7b96d72396807ab195f53ddc.camel@calian.com> References: <20220429222835.3641895-1-robert.hancock@calian.com> <20220504192028.2f7d10fb@kernel.org> <5376cbf00c18487b7b96d72396807ab195f53ddc.camel@calian.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220505_110824_437643_C2FE7515 X-CRM114-Status: GOOD ( 20.22 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, 5 May 2022 17:33:39 +0000 Robert Hancock wrote: > On Wed, 2022-05-04 at 19:20 -0700, Jakub Kicinski wrote: > > On Mon, 2 May 2022 19:30:51 +0000 Radhey Shyam Pandey wrote: > > > Thanks for the patch. I assume for simulating heavy network load we > > > are using netperf/iperf. Do we have some details on the benchmark > > > before and after adding TX NAPI? I want to see the impact on > > > throughput. > > > > Seems like a reasonable ask, let's get the patch reposted > > with the numbers in the commit message. > > Didn't mean to ignore that request, looks like I didn't get Radhey's email > directly, odd. > > I did a test with iperf3 from the board (Xilinx MPSoC ZU9EG platform) connected > to a Linux PC via a switch at 1G link speed. With TX NAPI in place I saw about > 942 Mbps for TX rate, with the previous code I saw 941 Mbps. RX speed was also > unchanged at 941 Mbps. So no real significant change either way. I can spin > another version of the patch that includes these numbers. Sounds like line rate, is there a difference in CPU utilization? _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel