From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Francois Romieu <romieu@fr.zoreil.com>, <davem@davemloft.net>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Deadlock, L2TP over IP are not working, 3.4.1
Date: Fri, 08 Jun 2012 18:56:12 +0300 [thread overview]
Message-ID: <67d8beaf421874815145fdefc69b3366@visp.net.lb> (raw)
In-Reply-To: <20120608154106.GD5024@kvack.org>
On 2012-06-08 18:41, Benjamin LaHaise wrote:
> On Fri, Jun 08, 2012 at 07:47:18AM +0200, Eric Dumazet wrote:
>> I have no idea how many l2tp_eth devices are setup at once in
>> typical
>> conf.
>
> Depends on the usage scenario. L2TP is commonly used for terminating
> customer connections by wholesale ISPs. In that kind of edge routing
> use-case, tens of thousands of interfaces are easily possible.
>
> -ben
In my case it is few hundreds. I am not sure it is typical case, but i
really will like if this setup
will give me good performance. Since Linux usually used on the PC's, i
don't think they will scale more
than 2-3 Gbps. Also L2TP pseudowire (l2tp_eth) usually done not
directly to end-users, but to LAC's, so i think
it is up to thousand.
Right now i am routing around 700Mbps over there, and noticed some
problem with pskb_expand_head,
but that's separate question i will ask, if i will not be able to sort
it out by myself.
---
Denys Fedoryshchenko, Network Engineer, Virtual ISP S.A.L.
next prev parent reply other threads:[~2012-06-08 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 9:54 Denys Fedoryshchenko
2012-06-07 20:53 ` Francois Romieu
2012-06-07 21:30 ` Eric Dumazet
2012-06-07 22:37 ` Francois Romieu
2012-06-08 5:47 ` Eric Dumazet
2012-06-08 15:41 ` Benjamin LaHaise
2012-06-08 15:56 ` Denys Fedoryshchenko [this message]
2012-06-08 16:04 ` Eric Dumazet
2012-06-10 12:14 ` Hong zhi guo
2012-06-10 13:31 ` Eric Dumazet
2012-06-10 13:38 ` Eric Dumazet
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=67d8beaf421874815145fdefc69b3366@visp.net.lb \
--to=denys@visp.net.lb \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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
all inboxes | Powered by JetHome®