From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Jesper Dangaard Brouer <jdb@comx.dk>
Cc: Eric Dumazet <eric.dumazet@gmail.com>, netdev <netdev@vger.kernel.org>
Subject: Re: Loopback performance from kernel 2.6.12 to 2.6.37
Date: Sun, 12 Dec 2010 13:48:33 -0200 [thread overview]
Message-ID: <20101212154833.GB20240@ghostprotocols.net> (raw)
In-Reply-To: <1289388256.15004.66.camel@firesoul.comx.local>
Em Wed, Nov 10, 2010 at 12:24:16PM +0100, Jesper Dangaard Brouer escreveu:
> > BUT perf top reveals that its probably related to the function
> > 'find_busiest_group' ... any kernel config hints how I get rid of that?
>
> The 'find_busiest_group' seems to be an artifact of "perf top", if I use
> "perf record" then the 'find_busiest_group' function disappears. Which
> is kind of strange, as 'find_busiest_group' seem the be related to
> sched_fair.c.
>
> perf --version
> perf version 2.6.35.7.1.g60d9c
perf top does sytemwide sampling, while when you use 'perf record
./workload' its not systemwide.
Take a look at 'perf top --help' to see how to limit this to an existing
pid, tid, cpu list, etc.
- Arnaldo
next prev parent reply other threads:[~2010-12-12 15:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1288954189.28003.178.camel@firesoul.comx.local>
[not found] ` <1288988955.2665.297.camel@edumazet-laptop>
[not found] ` <1289213926.15004.19.camel@firesoul.comx.local>
[not found] ` <1289214289.2820.188.camel@edumazet-laptop>
2010-11-08 15:06 ` Loopback performance from kernel 2.6.12 to 2.6.37 Eric Dumazet
2010-11-09 0:05 ` Andrew Hendry
2010-11-09 5:22 ` Eric Dumazet
2010-11-09 6:23 ` Eric Dumazet
2010-11-09 6:30 ` Andrew Hendry
2010-11-09 6:38 ` Eric Dumazet
2010-11-09 6:42 ` Eric Dumazet
2010-11-09 13:59 ` Jesper Dangaard Brouer
2010-11-09 14:06 ` Eric Dumazet
2010-11-09 14:16 ` Jesper Dangaard Brouer
2010-11-09 14:25 ` Eric Dumazet
2010-11-18 13:52 ` Eric Dumazet
2010-11-18 17:41 ` Eric Dumazet
2010-11-18 17:48 ` David Miller
2010-11-09 14:38 ` Jesper Dangaard Brouer
2010-11-10 11:24 ` Jesper Dangaard Brouer
2010-12-12 15:48 ` Arnaldo Carvalho de Melo [this message]
2010-11-09 21:35 Xose Vazquez Perez
2010-11-10 8:49 ` Jesper Dangaard Brouer
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=20101212154833.GB20240@ghostprotocols.net \
--to=acme@infradead.org \
--cc=eric.dumazet@gmail.com \
--cc=jdb@comx.dk \
--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 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).