[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X/exS1VmkmxCI8TK@lunn.ch>
Date: Fri, 8 Jan 2021 02:11:39 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Danielle Ratson <danieller@...lanox.com>, netdev@...r.kernel.org,
davem@...emloft.net, jiri@...dia.com, f.fainelli@...il.com,
mkubecek@...e.cz, mlxsw@...dia.com, idosch@...dia.com,
Danielle Ratson <danieller@...dia.com>
Subject: Re: [PATCH net-next repost v2 2/7] ethtool: Get link mode in use
instead of speed and duplex parameters
> > diff --git a/Documentation/networking/ethtool-netlink.rst b/Documentation/networking/ethtool-netlink.rst
> > index 05073482db05..c21e71e0c0e8 100644
> > --- a/Documentation/networking/ethtool-netlink.rst
> > +++ b/Documentation/networking/ethtool-netlink.rst
> > @@ -406,6 +406,7 @@ Kernel response contents:
> > ``ETHTOOL_A_LINKMODES_PEER`` bitset partner link modes
> > ``ETHTOOL_A_LINKMODES_SPEED`` u32 link speed (Mb/s)
> > ``ETHTOOL_A_LINKMODES_DUPLEX`` u8 duplex mode
> > + ``ETHTOOL_A_LINKMODES_LINK_MODE`` u8 link mode
>
> Are there other places in the uapi we already limit ourselves to
> u8 / max 255? Otherwise u32 is better, the nlattr will be padded,
> anyway.
Only allowing 255 values might be too limiting. We already have 91 of
them. It was initially thought that 32 would be enough, and fixing
that limitation was a lot of work.
Andrew
Powered by blists - more mailing lists