From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: alex.shi@intel.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>
Subject: Re: UDP-U stream performance regression on 32-rc1 kernel
Date: Tue, 03 Nov 2009 12:33:10 +0800 [thread overview]
Message-ID: <1257222791.16282.46.camel@ymzhang> (raw)
In-Reply-To: <1257220036.3819.193.camel@alexs-hp.sh.intel.com>
On Tue, 2009-11-03 at 11:47 +0800, Alex Shi wrote:
> We found the UDP-U 1k/4k stream of netperf benchmark have some
> performance regression from 10% to 20% on our Tulsa and some NHM
> machines.
perf events shows function find_busiest_group consumes about 4.5% cpu time
with the patch while it only consumes 0.5% cpu time without the patch.
The communication between netperf client and netserver is very fast.
When netserver receives a message and there is no new message available,
it goes to sleep and scheduler calls idle_balance => load_balance_newidle.
load_balance_newidle spends too much time and a new message arrives quickly
before load_balance_newidle ends.
As the comments in the patch say hackbench benefits from it, I tested hackbench
on Nehalem and core2 machines. hackbench does benefit from it, about 6% on
nehalem machines, but doesn't benefit on core2 machines.
Yanmin
> Bisecting found it is due to the following commitment.
>
> commit 840a0653100dbde599ae8ddf83fa214dfa5fd1aa
> Author: Ingo Molnar <mingo@elte.hu>
> Date: Fri Sep 4 11:32:54 2009 +0200
next prev parent reply other threads:[~2009-11-03 4:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 3:47 UDP-U stream performance regression on 32-rc1 kernel Alex Shi
2009-11-03 4:33 ` Zhang, Yanmin [this message]
2009-11-03 9:09 ` Mike Galbraith
2009-11-03 17:45 ` Ingo Molnar
2009-11-04 1:55 ` Zhang, Yanmin
2009-11-04 12:07 ` Mike Galbraith
2009-11-05 2:20 ` Zhang, Yanmin
2009-11-05 5:20 ` Mike Galbraith
2009-11-05 7:03 ` Mike Galbraith
2009-11-05 8:57 ` Mike Galbraith
2009-11-05 7:44 ` Zhang, Yanmin
2009-11-05 8:10 ` Mike Galbraith
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=1257222791.16282.46.camel@ymzhang \
--to=yanmin_zhang@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=alex.shi@intel.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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