From: Benjamin LaHaise <bcrl@lhnet.ca>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Johannes Stezenbach <js@sig21.net>,
Stephen Hemminger <shemminger@vyatta.com>,
netdev@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: Re: Q: netdev: generate kobject uevent on network events.
Date: Wed, 9 Dec 2009 13:54:09 -0500 [thread overview]
Message-ID: <20091209185409.GD32273@kvack.org> (raw)
In-Reply-To: <ac3eb2510912091046g4e5173b1sb97d6a4dddfd0b81@mail.gmail.com>
On Wed, Dec 09, 2009 at 07:46:26PM +0100, Kay Sievers wrote:
> Can't, in some setups, these events happen at a rather high frequency?
> I heard of people running many hundreds of ppp interfaces on a single
> box acting as a DSL concentrator.
/me waves
Yes, DSL concentration is looking at tens of thousands to a hundred thousand
interfaces on current hardware with 10G links.
> They state to already have trouble
> handling the amount of uevents generated on such boxes just for the
> "add/remove" events of all the interfaces if something goes wrong with
> the network. If we add more for state transitions, such events would
> probably need to be rate-limited. In general, uevents/udev are not
> really suitable for high-frequency events, and if such behavior can be
> expected, we might better stick with the current netlink interface.
Duplicating events in different delivery mechanisms seems pointless. A
simple netlink listener can be done in less than a hundred lines, so I don't
see the need for the duplication.
-ben
next prev parent reply other threads:[~2009-12-09 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 17:02 Q: netdev: generate kobject uevent on network events Johannes Stezenbach
2009-12-09 18:46 ` Kay Sievers
2009-12-09 18:54 ` Benjamin LaHaise [this message]
2009-12-09 19:21 ` Dan Williams
2009-12-09 21:03 ` Johannes Stezenbach
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=20091209185409.GD32273@kvack.org \
--to=bcrl@lhnet.ca \
--cc=js@sig21.net \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).