netdev - Re: What now when we're [almost] out of ADVERTISED bits?

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]

Date:	Sun, 29 Nov 2015 23:39:38 +0200
From:	Or Gerlitz <gerlitz.or@...il.com>
To:	Yuval Mintz <Yuval.Mintz@...gic.com>
Cc:	"ben@...adent.org.uk" <ben@...adent.org.uk>,
	netdev <netdev@...r.kernel.org>,
	David Decotigny <ddecotig@...il.com>
Subject: Re: What now when we're [almost] out of ADVERTISED bits?

On Sun, Nov 29, 2015 at 3:53 PM, Yuval Mintz <Yuval.Mintz@...gic.com> wrote:
> [I suspect there was probably some discussion over this,
> but I couldn't find it; References would be welcome]

there was a work by David Decotigny that should have solved the out of
bits problem here [1]. Maybe it should be revived.

[1] https://lkml.org/lkml/2015/1/26/882


> So it appears we're almost out of bits for new advertised speeds;
> I'm currently looking at adding 100g.
>
> Assuming we want [and we do want] to have those in the `supported',
> `advertising' and `lp_advertising' fields, the 2 reserve fields in
> ethtool_cmd would not be sufficient [unless we break them into 4 u16].
> Or are we planning something more generic than this for future bits?

Or.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html