From: patchwork-bot+netdevbpf@kernel.org
To: Martin Habets <habetsm.xilinx@gmail.com>
Cc: ihuguet@redhat.com, davem@davemloft.net, kuba@kernel.org,
ecree.xilinx@gmail.com, netdev@vger.kernel.org,
dinang@xilinx.com
Subject: Re: [PATCH V2 net-next] sfc: The size of the RX recycle ring should be more flexible
Date: Wed, 02 Feb 2022 05:10:10 +0000 [thread overview]
Message-ID: <164377861092.30544.4725309458508653960.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220131111054.cp4f6foyinaarwbn@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 31 Jan 2022 11:10:54 +0000 you wrote:
> Ideally the size would depend on the link speed, but the recycle
> ring is created when the interface is brought up before the driver
> knows the link speed. So size it for the maximum speed of a given NIC.
> PowerPC is only supported on SFN7xxx and SFN8xxx NICs.
>
> With this patch on a 40G NIC the number of calls to alloc_pages and
> friends went down from about 18% to under 2%.
> On a 10G NIC the number of calls to alloc_pages and friends went down
> from about 15% to 0 (perf did not capture any calls during the 60
> second test).
> On a 100G NIC the number of calls to alloc_pages and friends went down
> from about 23% to 4%.
>
> [...]
Here is the summary with links:
- [V2,net-next] sfc: The size of the RX recycle ring should be more flexible
https://git.kernel.org/netdev/net-next/c/000fe940e51f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-02 5:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 15:14 Bad performance in RX with sfc 40G Íñigo Huguet
2021-11-18 17:19 ` Eric Dumazet
2021-12-02 14:26 ` Íñigo Huguet
2021-11-20 8:31 ` Martin Habets
2021-12-09 12:06 ` Íñigo Huguet
2021-12-23 13:18 ` Íñigo Huguet
2022-01-02 9:22 ` Martin Habets
2022-01-10 8:58 ` [PATCH net-next] sfc: The size of the RX recycle ring should be more flexible Martin Habets
2022-01-10 9:31 ` Íñigo Huguet
2022-01-12 9:05 ` Martin Habets
2022-01-31 11:08 ` Martin Habets
2022-01-10 17:22 ` Jakub Kicinski
2022-01-12 9:08 ` Martin Habets
2022-01-31 11:10 ` [PATCH V2 " Martin Habets
2022-02-02 5:10 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=164377861092.30544.4725309458508653960.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dinang@xilinx.com \
--cc=ecree.xilinx@gmail.com \
--cc=habetsm.xilinx@gmail.com \
--cc=ihuguet@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.