From: David Ahern <dsa@cumulusnetworks.com>
To: nicolas.dichtel@6wind.com, Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Scaling the Number of Network Interfaces on Linux
Date: Wed, 10 Feb 2016 12:59:48 +0100 [thread overview]
Message-ID: <56BB2634.3080500@cumulusnetworks.com> (raw)
In-Reply-To: <56BB1BEB.5090200@6wind.com>
On 2/10/16 12:15 PM, Nicolas Dichtel wrote:
> to follow your talk at nedev11, I already proposed some times ago a
> patch to
> remove sysctl, which was rejected. You can see the thread here:
> http://thread.gmane.org/gmane.linux.network/285840
Thanks for the reference. I'll take a look.
>
> 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.
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.
David
next prev parent reply other threads:[~2016-02-10 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 11:15 Scaling the Number of Network Interfaces on Linux Nicolas Dichtel
2016-02-10 11:59 ` David Ahern [this message]
2016-02-10 15:12 ` Nicolas Dichtel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56BB2634.3080500@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=roopa@cumulusnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.