netdev - Re: [PATCH net-next v2 0/3] bonding: 3ad: support for 200G/400G ports and more verbose warning

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <c86ba0ea-23b5-2aaf-6f1a-c25b2b2488ac@6wind.com>
Date:   Thu, 11 Feb 2021 11:25:18 +0100
From:   Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:     Nikolay Aleksandrov <razor@...ckwall.org>, netdev@...r.kernel.org
Cc:     roopa@...dia.com, andy@...yhouse.net, j.vosburgh@...il.com,
        vfalico@...il.com, kuba@...nel.org, davem@...emloft.net,
        alexander.duyck@...il.com, idosch@...dia.com,
        Nikolay Aleksandrov <nikolay@...dia.com>
Subject: Re: [PATCH net-next v2 0/3] bonding: 3ad: support for 200G/400G ports
 and more verbose warning

Le 10/02/2021 à 21:43, Nikolay Aleksandrov a écrit :
> From: Nikolay Aleksandrov <nikolay@...dia.com>
> 
> Hi,
> We'd like to have proper 200G and 400G support with 3ad bond mode, so we
> need to add new definitions for them in order to have separate oper keys,
> aggregated bandwidth and proper operation (patches 01 and 02). In
> patch 03 Ido changes the code to use pr_err_once instead of
> pr_warn_once which would help future detection of unsupported speeds.
> 
> v2: patch 03: use pr_err_once instead of WARN_ONCE
> 
> Thanks,
>  Nik
> 
> Ido Schimmel (1):
>   bonding: 3ad: Print an error for unknown speeds
> 
> Nikolay Aleksandrov (2):
>   bonding: 3ad: add support for 200G speed
>   bonding: 3ad: add support for 400G speed
> 
>  drivers/net/bonding/bond_3ad.c | 26 ++++++++++++++++++++++----
>  1 file changed, 22 insertions(+), 4 deletions(-)
> 
Acked-by: Nicolas Dichtel <nicolas.dichtel@...nd.com>