netdev - Re: Scaling the Number of Network Interfaces on Linux

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 10 Feb 2016 16:12:45 +0100
From:	Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:	David Ahern <dsa@...ulusnetworks.com>,
	Roopa Prabhu <roopa@...ulusnetworks.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: Scaling the Number of Network Interfaces on Linux

Le 10/02/2016 12:59, David Ahern a écrit :
> On 2/10/16 12:15 PM, Nicolas Dichtel wrote:
[snip]
>> Instead of removing completly the sysctl entries, another idea could be to
>> manage a group of interfaces which will share the same subtree.
>
> This come out from a side conversation as well -- for example to have interfaces
> enslaved to a bridge or bond share the same devconf.
It could also be interesting to have another way to group interfaces. For
example, group all ppp interfaces.

>
> This is certainly possible to do and I can give it a look. The key point is that
> we clearly need a means to lighten the overhead of a network interface.
Yes, I agree.