From: Denys Fedoryschenko <denys@visp.net.lb>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Benjamin LaHaise <bcrl@lhnet.ca>,
Stephen Hemminger <shemminger@vyatta.com>,
Cosmin Ratiu <cratiu@ixiacom.com>,
netdev@vger.kernel.org
Subject: Re: [RFC] make per interface sysctl entries configurable
Date: Mon, 26 Oct 2009 00:32:32 +0200 [thread overview]
Message-ID: <200910260032.32303.denys@visp.net.lb> (raw)
In-Reply-To: <200910260021.48785.opurdila@ixiacom.com>
On Monday 26 October 2009 00:21:48 Octavian Purdila wrote:
> Very good point, I think this is the best solution for people using a
> moderately high number of interfaces (a few thousand).
>
> But for really large setups there is another issue: memory consumption. In
> fact, in order to be able to scale to 128K interfaces and still have a
> significant amount of memory available to applications we also had to
> disable sysfs and #ifdef CONFIG_SYSFS struct device from net_device.
>
> I would also argue that when you have such a large number of interfaces you
> don't need to change setting on a per interface basis. Or at least this is
> our case :) and I suspect that the case with a large number of PPP
> interfaces is similar.
I will add also, sysctl -a (over busybox) on pppoe with 2k interfaces takes
ages to complete.
next prev parent reply other threads:[~2009-10-25 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 17:54 [RFC] make per interface sysctl entries configurable Octavian Purdila
2009-10-25 18:07 ` Denys Fedoryschenko
2009-10-25 21:37 ` Eric Dumazet
2009-10-25 22:21 ` Octavian Purdila
2009-10-25 22:32 ` Denys Fedoryschenko [this message]
2009-10-26 9:01 ` Cosmin Ratiu
2009-10-26 4:31 ` Stephen Hemminger
2009-10-26 15:24 ` Denys Fedoryschenko
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=200910260032.32303.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=bcrl@lhnet.ca \
--cc=cratiu@ixiacom.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
--cc=shemminger@vyatta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).