From: Denys Fedoryschenko <denys@visp.net.lb>
To: Benjamin LaHaise <bcrl@lhnet.ca>
Cc: netdev@vger.kernel.org
Subject: Re: regression: unregister_netdev() unusably slow
Date: Mon, 25 May 2009 00:23:30 +0300 [thread overview]
Message-ID: <200905250023.31056.denys@visp.net.lb> (raw)
In-Reply-To: <20090524192150.GE24757@kvack.org>
Once oprofile gave me hint about similar issue
On Sunday 24 May 2009 22:21:50 Benjamin LaHaise wrote:
> Hi folks,
>
> I just ran a few L2TP tests against 2.6.30-rc7, and it looks like network
> device deletion has become unusably slow. At least in 2.6.27.10, deleting
> 1000 network interfaces takes less than 2 seconds of real time. The same
> test run under 2.6.30-rc7 is taking hundreds of seconds to delete 1000
> interfaces at a rate of about 5 per second. The interfaces all share the
> same local ip address, but each have a single route to a unique client
> ip address.
>
> This is a fairly reasonable use-case, as a single L2TP daemon can be
> terminating thousands of client connections on a single tunnel, and a
> tunnel flap will require tearing down all these interfaces. I'll work on
> bisecting it, but if someone has any ideas of the source, I'd appreciate
> hearing about it.
>
> -ben
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-24 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 19:21 regression: unregister_netdev() unusably slow Benjamin LaHaise
2009-05-24 21:23 ` Denys Fedoryschenko [this message]
2009-05-24 21:37 ` Benjamin LaHaise
2009-05-24 21:42 ` Eric Dumazet
2009-05-24 21:44 ` Benjamin LaHaise
2009-05-24 22:07 ` Eric Dumazet
2009-05-24 22:12 ` Benjamin LaHaise
2009-05-24 22:47 ` Eric Dumazet
2009-05-25 0:00 ` Benjamin LaHaise
2009-05-25 5:22 ` Eric Dumazet
2009-05-25 8:04 ` Damien Wyart
2009-05-25 16:21 ` Paul E. McKenney
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=200905250023.31056.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=bcrl@lhnet.ca \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.