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
| ||
|
Date: Tue, 13 Oct 2009 10:34:32 -0400 From: Benjamin LaHaise <bcrl@...et.ca> To: jamal <hadi@...erus.ca> Cc: Denys Fedoryschenko <denys@...p.net.lb>, netdev@...r.kernel.org Subject: Re: kernel mode pppoe ppp if + ifb + mirred redirect, ethernet packets in ifb?! Hi folks, On Tue, Oct 13, 2009 at 09:02:38AM -0400, jamal wrote: > On Tue, 2009-10-13 at 15:45 +0300, Denys Fedoryschenko wrote: > > Another bottleneck is u32 (i can optimize but) and some strange locks > > appearing at top of perf, maybe same as logon case. > > like you say u32 can be optimized > > > And yes, pppd also appearing, but seems just registering new sysctls (for new > > interface?) takes a lot of resources. > > > > back in the days (when i was involved in pppoe) pppd was a big problem > because it was not rentrant, so to solve the problem you exec a new > process for each user.. > Ben Lahaise did a lot of work in this area and i am pretty sure decided > not to use pppd. Yes, I've been maintaining the ppp implementation (Babylon) initially written by SpellCaster back in '98. My main focus of late has been dealing with PPPoE and L2TP, and specifically with terminating a lot of L2TP LNS traffic. Babylon itself scales fairly well to large numbers of interfaces, as does the network stack these days. Currently the bottleneck in interface creation is in the sysctl code. The other big problem with large numbers of interfaces is interface deletion. The synchronize_rcu() call in the interface teardown ends up making a single daemon with thousands of interfaces take a long time to clean up after itself. -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
Powered by blists - more mailing lists