From: Sean Anderson <sean.anderson@linux.dev>
To: "Nelson, Shannon" <shannon.nelson@amd.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>,
netdev@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Michal Simek <michal.simek@amd.com>,
linux-kernel@vger.kernel.org, Heng Qi <hengqi@linux.alibaba.com>
Subject: Re: [RFC PATCH net-next v2 0/6] net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM
Date: Tue, 10 Sep 2024 10:30:35 -0400 [thread overview]
Message-ID: <7bd2dbef-643a-4258-af1c-b68bff980b22@linux.dev> (raw)
In-Reply-To: <d56ff939-cbcb-4455-b589-3a87b0ec57a4@amd.com>
On 9/9/24 21:34, Nelson, Shannon wrote:
> On 9/9/2024 4:52 PM, Sean Anderson wrote:
>>
>> To improve performance without sacrificing latency under low load,
>> enable DIM. While I appreciate not having to write the library myself, I
>> do think there are many unusual aspects to DIM, as detailed in the last
>> patch.
>>
>> This series depends on [1-2] and is therefore marked RFC. This series is
>> otherwise ready to merge.
>>
>> [1] https://lore.kernel.org/netdev/20240909230908.1319982-1-sean.anderson@linux.dev/
>> [2] https://lore.kernel.org/netdev/20240909231904.1322387-1-sean.anderson@linux.dev/
>>
>> Changes in v2:
>> - Add some symbolic constants for IRQ delay timer
>> - Report an error for bad coalesce settings
>> - Don't use spin_lock_irqsave when we know the context
>> - Split the CR calculation refactor from runtime coalesce settings
>> adjustment support for easier review.
>> - Have axienet_update_coalesce_rx/tx take the cr value/mask instead of
>> calculating it with axienet_calc_cr. This will make it easier to add
>> partial updates in the next few commits.
>> - Get coalesce parameters from driver state
>> - Don't take the RTNL in axienet_rx_dim_work to avoid deadlock. Instead,
>> calculate a partial cr update that axienet_update_coalesce_rx can
>> perform under a spin lock.
>> - Use READ/WRITE_ONCE when accessing/modifying rx_irqs
>>
>> Sean Anderson (6):
>> net: xilinx: axienet: Add some symbolic constants for IRQ delay timer
>> net: xilinx: axienet: Report an error for bad coalesce settings
>> net: xilinx: axienet: Combine CR calculation
>> net: xilinx: axienet: Support adjusting coalesce settings while
>> running
>> net: xilinx: axienet: Get coalesce parameters from driver state
>> net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM
>>
>> drivers/net/ethernet/xilinx/Kconfig | 1 +
>> drivers/net/ethernet/xilinx/xilinx_axienet.h | 31 +-
>> .../net/ethernet/xilinx/xilinx_axienet_main.c | 320 ++++++++++++++----
>> 3 files changed, 273 insertions(+), 79 deletions(-)
>>
>> --
>> 2.35.1.1320.gc452695387.dirty
>>
>>
>
> Except for a couple of comment nits pointed out in 3/6 and 6/6, this set seems reasonable.
>
> Reviewed by: Shannon Nelson <shannon.nelson@amd.com>
>
>
Thanks. I'll address these for v3.
--Sean
prev parent reply other threads:[~2024-09-10 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 23:52 [RFC PATCH net-next v2 0/6] net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM Sean Anderson
2024-09-09 23:52 ` [RFC PATCH net-next v2 1/6] net: xilinx: axienet: Add some symbolic constants for IRQ delay timer Sean Anderson
2024-09-09 23:52 ` [RFC PATCH net-next v2 2/6] net: xilinx: axienet: Report an error for bad coalesce settings Sean Anderson
2024-09-09 23:52 ` [RFC PATCH net-next v2 3/6] net: xilinx: axienet: Combine CR calculation Sean Anderson
2024-09-10 1:32 ` Nelson, Shannon
2024-09-09 23:52 ` [RFC PATCH net-next v2 4/6] net: xilinx: axienet: Support adjusting coalesce settings while running Sean Anderson
2024-09-09 23:52 ` [RFC PATCH net-next v2 5/6] net: xilinx: axienet: Get coalesce parameters from driver state Sean Anderson
2024-09-09 23:52 ` [RFC PATCH net-next v2 6/6] net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM Sean Anderson
2024-09-10 1:32 ` Nelson, Shannon
2024-09-10 1:34 ` [RFC PATCH net-next v2 0/6] " Nelson, Shannon
2024-09-10 14:30 ` Sean Anderson [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=7bd2dbef-643a-4258-af1c-b68bff980b22@linux.dev \
--to=sean.anderson@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hengqi@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=shannon.nelson@amd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).