[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20091115165015.GU19478@kvack.org>
Date: Sun, 15 Nov 2009 11:50:15 -0500
From: Benjamin LaHaise <bcrl@...et.ca>
To: Denys Fedoryschenko <denys@...p.net.lb>
Cc: Mark Smith <lk-netdev@...netdev.nosense.org>,
David Miller <davem@...emloft.net>, shemminger@...tta.com,
opurdila@...acom.com, eric.dumazet@...il.com,
netdev@...r.kernel.org
Subject: Re: [net-next-2.6 PATCH] net: fast consecutive name allocation
Hi Denys,
On Sun, Nov 15, 2009 at 03:55:14AM +0200, Denys Fedoryschenko wrote:
> And interface creation speed is important for me, when electricity goes down
> here, many customers disconnects (up to 500 on single NAS), and then join
> again to NAS. Load average was jumping to sky on such situations, just option
> to not create sysfs entries helped me a lot (was posted recently).
> Electricity outage is usual here, happens 2-3 times daily.
This is exactly the type of scenario I'm looking at. The design of the
Babylon PPP stack is meant to scale somewhat better that pppd. It uses a
single process (although I'm starting to add threads to improve scaling on
SMP systems) for all PPP/L2TP sessions, and has rather lower connection
setup overhead (no fork()/exec() being the biggest one). With udev tuned,
irqbalance disabled and a few other tweaks, it gets >500 connections per
second in startup on a modern 2.6GHz processor for L2TP traffic. There
is PPPoE support, but it needs a bit more work done to scale automatically
(there are a few hardcoded limits in the PPPoE implementation).
-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