From: David Ahern <dsahern@gmail.com>
To: sowmini varadhan <sowmini05@gmail.com>, Julian Anastasov <ja@ssi.bg>
Cc: "Jamal Hadi Salim" <jhs@mojatatu.com>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
"Niels Möller" <nisse@southpole.se>,
netdev <netdev@vger.kernel.org>,
"Jonas Bonn" <jonas@southpole.se>
Subject: Re: Scaling 'ip addr add' (was Re: What's the right way to use a *large* number of source addresses?)
Date: Thu, 29 May 2014 10:19:40 -0600 [thread overview]
Message-ID: <53875E1C.2040708@gmail.com> (raw)
In-Reply-To: <CACP96tR8v=sujsGqFPefTw09X3WEud6-3KTX5j48ijX=hyyerw@mail.gmail.com>
On 5/29/14, 10:11 AM, sowmini varadhan wrote:
> I'm still not sure I understand*why* check_lifetime ends
> up being expensive, though. For this particular test, all the
...
>
> fib_sync_up() could also use a magnifying glass - was going to
> look at this later.
Annotation feature of perf should help
perf record -ga -- <command>
'perf report' with a TUI and then hit 'a' for annotation mode
or use 'perf annotate -k vmlinux -s <symbol name>'
David
prev parent reply other threads:[~2014-05-29 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 21:29 Scaling 'ip addr add' (was Re: What's the right way to use a *large* number of source addresses?) sowmini varadhan
2014-05-28 1:41 ` Eric Dumazet
2014-05-28 10:01 ` sowmini varadhan
2014-05-28 11:23 ` Jamal Hadi Salim
2014-05-28 11:54 ` sowmini varadhan
2014-05-28 12:18 ` sowmini varadhan
2014-05-28 13:44 ` Eric Dumazet
2014-05-28 14:48 ` Eric Dumazet
2014-05-28 16:00 ` Eric Dumazet
2014-05-28 17:18 ` sowmini varadhan
2014-05-29 6:34 ` Julian Anastasov
2014-05-29 16:11 ` sowmini varadhan
2014-05-29 16:19 ` David Ahern [this message]
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=53875E1C.2040708@gmail.com \
--to=dsahern@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=ja@ssi.bg \
--cc=jhs@mojatatu.com \
--cc=jonas@southpole.se \
--cc=netdev@vger.kernel.org \
--cc=nisse@southpole.se \
--cc=sowmini05@gmail.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).