netdev - Re: [PATCH net-next] netdev: reshuffle netif_napi

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]

Date:   Wed, 04 May 2022 01:00:34 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     davem@...emloft.net, pabeni@...hat.com, edumazet@...gle.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next] netdev: reshuffle netif_napi_add() APIs to allow
 dropping weight

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:

On Mon,  2 May 2022 16:27:03 -0700 you wrote:
> Most drivers should not have to worry about selecting the right
> weight for their NAPI instances and pass NAPI_POLL_WEIGHT.
> It'd be best if we didn't require the argument at all and selected
> the default internally.
> 
> This change prepares the ground for such reshuffling, allowing
> for a smooth transition. The following API should remain after
> the next release cycle:
>   netif_napi_add()
>   netif_napi_add_weight()
>   netif_napi_add_tx()
>   netif_napi_add_tx_weight()
> Where the _weight() variants take an explicit weight argument.
> I opted for a _weight() suffix rather than a __ prefix, because
> we use __ in places to mean that caller needs to also issue a
> synchronize_net() call.
> 
> [...]

Here is the summary with links:
  - [net-next] netdev: reshuffle netif_napi_add() APIs to allow dropping weight
    https://git.kernel.org/netdev/net-next/c/58caed3dacb4

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