[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1401284699.5367.268.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Wed, 28 May 2014 06:44:59 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: sowmini varadhan <sowmini05@...il.com>
Cc: Jamal Hadi Salim <jhs@...atatu.com>,
Niels Möller <nisse@...thpole.se>,
netdev <netdev@...r.kernel.org>, Jonas Bonn <jonas@...thpole.se>
Subject: Re: Scaling 'ip addr add' (was Re: What's the right way to use a
*large* number of source addresses?)
On Wed, 2014-05-28 at 08:18 -0400, sowmini varadhan wrote:
> On Tue, May 27, 2014 at 9:41 PM, Eric Dumazet <eric.dumazet@...il.com> wrote:
>
> > Last time I checked, we were spending _lot_ of time in check_lifetime()
>
> Although check_lifetime() itself did not light up in my
> perf output, i see your point- it has a few ifa_list walks
> that might end up being expensive - but these are static
> IPv4 addresses- they should be marked IFA_F_PERMANENT,
> right? That's probably why they did not show up in my perf output?
How did you run perf ?
If you run :
perf record ./your_script.sh
It wont catch all the load that is triggered from work queues.
If you do
./your_script.sh &
perf top
Then you'll see check_lifetime() at first position.
--
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