netdev - Re: Q: netdev: generate kobject uevent on network events.

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]

Message-ID: <20091209185409.GD32273@kvack.org>
Date:	Wed, 9 Dec 2009 13:54:09 -0500
From:	Benjamin LaHaise <bcrl@...et.ca>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Johannes Stezenbach <js@...21.net>,
	Stephen Hemminger <shemminger@...tta.com>,
	netdev@...r.kernel.org, linux-hotplug@...r.kernel.org
Subject: Re: Q: netdev: generate kobject uevent on network events.

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
--
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