From: Mike Galbraith <efault@gmx.de>
To: Mel Gorman <mgorman@suse.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Suresh Siddha <suresh.b.siddha@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Netperf UDP_STREAM regression due to not sending IPIs in ttwu_queue()
Date: Wed, 10 Oct 2012 15:02:01 +0200 [thread overview]
Message-ID: <1349874121.6992.80.camel@marge.simpson.net> (raw)
In-Reply-To: <20121010122921.GX29125@suse.de>
On Wed, 2012-10-10 at 13:29 +0100, Mel Gorman wrote:
> On Wed, Oct 03, 2012 at 03:30:01PM +0200, Mike Galbraith wrote:
> > nohz=off, pipe-test with one half pinned to CPU0, the other to CPU1.
> >
> > procs -----------memory---------- ---swap-- -----io---- -system-- -----cpu------
> > r b swpd free buff cache si so bi bo in cs us sy id wa st
> > TTW_QUEUE
> > 1 0 0 3039488 50948 444720 0 0 0 0 539724 1013417 1 15 84 0 0
> > 1 0 0 3039488 50956 444720 0 0 0 1 540853 1015679 1 15 84 0 0
> > 1 0 0 3039364 50956 444720 0 0 0 0 541630 1017239 1 16 83 0 0
> > 2 0 0 3038992 50956 444720 0 0 0 0 335550 1096569 4 20 76 0 0
> > NO_TTWU_QUEUE
> > 1 0 0 3038992 50956 444720 0 0 0 0 33100 1318984 1 27 71 0 0
> > 1 0 0 3038868 50956 444720 0 0 0 0 33100 1319126 2 27 71 0 0
> > 1 0 0 3038868 50956 444720 0 0 0 0 33097 1317968 1 27 72 0 0
> > 2 0 0 3038868 50964 444720 0 0 0 1 33104 1318558 2 27 71 0 0
> >
> > We can switch faster with NO_TTWU_QUEUE, so we switch more, and that
> > hurts netperf UDP_STREAM throughput.. somehow. Fatter is better is not
> > the way context switch happy benchmarks usually work.
> >
>
> Do we really switch more though?
Yup, pipe-test measures the full round trip, and agrees with vmstat.
netperf TCP_RR agrees, tbench agrees... this STREAM thingy is the only
high frequency switcher I've seen go all weird like this.
(hm, wonder how fast box can blast IPIs.. 1MHz?)
-Mike
next prev parent reply other threads:[~2012-10-10 13:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 6:51 Netperf UDP_STREAM regression due to not sending IPIs in ttwu_queue() Mel Gorman
2012-10-02 7:49 ` Mike Galbraith
2012-10-02 8:45 ` Mel Gorman
2012-10-02 9:31 ` Mike Galbraith
2012-10-02 13:14 ` Mel Gorman
2012-10-02 14:33 ` Mike Galbraith
2012-10-03 6:50 ` Mike Galbraith
2012-10-03 8:13 ` Mike Galbraith
2012-10-03 13:30 ` Mike Galbraith
2012-10-10 12:29 ` Mel Gorman
2012-10-10 13:02 ` Mike Galbraith [this message]
2012-10-10 13:05 ` Peter Zijlstra
2012-10-02 22:48 ` Rick Jones
2012-10-03 9:47 ` Mel Gorman
2012-10-03 10:22 ` Eric Dumazet
2012-10-03 18:04 ` Rick Jones
2012-10-05 9:54 ` Mel Gorman
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=1349874121.6992.80.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=suresh.b.siddha@intel.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