From: patchwork-bot+netdevbpf@kernel.org
To: Souradeep Chakrabarti <schakrabarti@linux.microsoft.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, longli@microsoft.com,
yury.norov@gmail.com, leon@kernel.org, cai.huoqing@linux.dev,
ssengar@linux.microsoft.com, vkuznets@redhat.com,
tglx@linutronix.de, linux-hyperv@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, schakrabarti@microsoft.com,
paulros@microsoft.com
Subject: Re: [PATCH 0/4 V3 net-next] net: mana: Assigning IRQ affinity on HT cores
Date: Thu, 01 Feb 2024 12:20:25 +0000 [thread overview]
Message-ID: <170679002599.3757.12151723746549913869.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1706509267-17754-1-git-send-email-schakrabarti@linux.microsoft.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 28 Jan 2024 22:21:03 -0800 you wrote:
> This patch set introduces a new helper function irq_setup(),
> to optimize IRQ distribution for MANA network devices.
> The patch set makes the driver working 15% faster than
> with cpumask_local_spread().
>
> Souradeep Chakrabarti (1):
> net: mana: Assigning IRQ affinity on HT cores
>
> [...]
Here is the summary with links:
- [1/4,V3,net-next] cpumask: add cpumask_weight_andnot()
https://git.kernel.org/netdev/net-next/c/c1f5204efcbc
- [2/4,V3,net-next] cpumask: define cleanup function for cpumasks
https://git.kernel.org/netdev/net-next/c/dcee228078c3
- [3/4,V3,net-next] net: mana: add a function to spread IRQs per CPUs
https://git.kernel.org/netdev/net-next/c/91bfe210e196
- [4/4,V3,net-next] net: mana: Assigning IRQ affinity on HT cores
https://git.kernel.org/netdev/net-next/c/8afefc361209
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:[~2024-02-01 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 6:21 [PATCH 0/4 V3 net-next] net: mana: Assigning IRQ affinity on HT cores Souradeep Chakrabarti
2024-01-29 6:21 ` [PATCH 1/4 V3 net-next] cpumask: add cpumask_weight_andnot() Souradeep Chakrabarti
2024-02-01 9:39 ` Paolo Abeni
2024-01-29 6:21 ` [PATCH 2/4 V3 net-next] cpumask: define cleanup function for cpumasks Souradeep Chakrabarti
2024-01-29 6:21 ` [PATCH 3/4 V3 net-next] net: mana: add a function to spread IRQs per CPUs Souradeep Chakrabarti
2024-01-29 6:21 ` [PATCH 4/4 V3 net-next] net: mana: Assigning IRQ affinity on HT cores Souradeep Chakrabarti
2024-02-01 12:20 ` 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=170679002599.3757.12151723746549913869.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cai.huoqing@linux.dev \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulros@microsoft.com \
--cc=schakrabarti@linux.microsoft.com \
--cc=schakrabarti@microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wei.liu@kernel.org \
--cc=yury.norov@gmail.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).