netdev - Re: [PATCH net-next 1/1] ixgbe: let the xdpdrv work with more than 64 cpus

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:   Thu, 30 Sep 2021 12:50:08 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Tony Nguyen <anthony.l.nguyen@...el.com>
Cc:     davem@...emloft.net, kuba@...nel.org, xingwanli@...ishou.com,
        netdev@...r.kernel.org, maciej.fijalkowski@...el.com,
        magnus.karlsson@...el.com, ast@...nel.org, daniel@...earbox.net,
        hawk@...nel.org, john.fastabend@...il.com, andrii@...nel.org,
        kpsingh@...nel.org, kafai@...com, yhs@...com, songliubraving@...co,
        bpf@...r.kernel.org, lishujin@...ishou.com,
        sandeep.penigalapati@...el.com
Subject: Re: [PATCH net-next 1/1] ixgbe: let the xdpdrv work with more than 64
 cpus

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Wed, 29 Sep 2021 10:56:05 -0700 you wrote:
> From: Jason Xing <xingwanli@...ishou.com>
> 
> Originally, ixgbe driver doesn't allow the mounting of xdpdrv if the
> server is equipped with more than 64 cpus online. So it turns out that
> the loading of xdpdrv causes the "NOMEM" failure.
> 
> Actually, we can adjust the algorithm and then make it work through
> mapping the current cpu to some xdp ring with the protect of @tx_lock.
> 
> [...]

Here is the summary with links:
  - [net-next,1/1] ixgbe: let the xdpdrv work with more than 64 cpus
    https://git.kernel.org/netdev/net-next/c/4fe815850bdc

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