netdev - Re: [PATCH v2 net-next] ibmvnic: Toggle between queue types in affinity mapping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <167515741629.26648.10038272468094003278.git-patchwork-notify@kernel.org>
Date:   Tue, 31 Jan 2023 09:30:16 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Nick Child <nnac123@...ux.ibm.com>
Cc:     netdev@...r.kernel.org, bjking1@...ux.ibm.com, haren@...ux.ibm.com,
        ricklind@...ibm.com
Subject: Re: [PATCH v2 net-next] ibmvnic: Toggle between queue types in affinity
 mapping

Hello:

This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@...hat.com>:

On Fri, 27 Jan 2023 15:43:58 -0600 you wrote:
> Previously, ibmvnic IRQs were assigned to CPU numbers by assigning all
> the IRQs for transmit queues then assigning all the IRQs for receive
> queues. With multi-threaded processors, in a heavy RX or TX environment,
> physical cores would either be overloaded or underutilized (due to the
> IRQ assignment algorithm). This approach is sub-optimal because IRQs for
> the same subprocess (RX or TX) would be bound to adjacent CPU numbers,
> meaning they were more likely to be contending for the same core.
> 
> [...]

Here is the summary with links:
  - [v2,net-next] ibmvnic: Toggle between queue types in affinity mapping
    https://git.kernel.org/netdev/net-next/c/6831582937bd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html