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  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]
Date:   Mon, 17 Oct 2022 11:45:43 +0200
From:   Jiri Pirko <>
To:     Maxime Chevallier <>
        Thomas Petazzoni <>,
        Antoine Tenart <>,
        "David S. Miller" <>,
        Heiner Kallweit <>,
        Florian Fainelli <>,
        Vivien Didelot <>,
        Andrew Lunn <>,
        Russell King - ARM Linux admin <>,
        Tobias Waldekranz <>,
        Oleksij Rempel <>,
        Jakub Kicinski <>
Subject: Re: Multi-PHYs and multiple-ports bonding support

Mon, Oct 17, 2022 at 10:51:00AM CEST, wrote:


>3) UAPI
>>From userspace, we would need ways to list the ports, their state, and
>possibly to configure the bonding parameters. for now in ethtool, we
>don't have the notion of port at all, we just have 1 netdevice == 1
>port. Should we therefore create one netdevice per port ? or stick to
>that one interface and refer to its ports with some ethtool parameters ?

I don't like the idea of having 1 netdev per port. Netdev represents
mostly the MAC entity, and there is only one.


Powered by blists - more mailing lists