netdev - Re: Suitable value for bonding module's tx

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:   Tue, 9 Nov 2021 16:29:38 -0800
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Johannes Lundberg <johalun0@...il.com>, netdev@...r.kernel.org
Subject: Re: Suitable value for bonding module's tx_queues?



On 11/9/21 12:58 PM, Johannes Lundberg wrote:
> Hi
> 
> Please cc me on reply since I'm not subscribed.
> 
> I'm wondering when you want to change tx_queues from default 16. Should this match the total number of queues of all the members of the bond? Let's say I got 2 interfaces, each with 24 queues on a 24 CPU system in a bond. Should I load bonding with 24 to match the number of CPUs or 48 to match the total number of queues of the members, or leave at default because it's not relevant?
> 
> Thanks!
> 

Unless you add a mq qdisc on the bonding device, "number of tx queues" does not matter
because bonding is a virtual device, with NETIF_F_LLTX