From: Andi Kleen <andi@firstfloor.org>
To: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
Cc: netdev@vger.kernel.org, Bernhard Schmidt <berni+ipv6@birkenwald.de>
Subject: Re: IPv6 tunnel scalability problem
Date: Mon, 01 Sep 2008 14:04:58 +0200 [thread overview]
Message-ID: <8763pgxead.fsf@basil.nowhere.org> (raw)
In-Reply-To: <200808311958.51510.rdenis@simphalempin.com> (Rémi Denis-Courmont's message of "Sun, 31 Aug 2008 19:58:51 +0300")
Rémi Denis-Courmont <rdenis@simphalempin.com> writes:
> I have been maintaining a TUN-based Linux implementation of Teredo/RFC4380. On
> a busy node, this can trigger quite many peers on the virtual point-to-point
> tunnel interface. I have received complaints that the whole thing seems to
> hit some severe performance bottleneck when this happens. It is not clear to
> me at this point whether it's a kernel or a user problem. So I have been
> writing a stress test.
You could use oprofile to find out where the CPU time is going.
That would work even during normal operation. Post the opreport -l output
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-09-01 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 16:58 IPv6 tunnel scalability problem Rémi Denis-Courmont
2008-09-01 12:04 ` Andi Kleen [this message]
2008-09-01 15:09 ` Rémi Denis-Courmont
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=8763pgxead.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=berni+ipv6@birkenwald.de \
--cc=netdev@vger.kernel.org \
--cc=rdenis@simphalempin.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;
as well as URLs for NNTP newsgroup(s).