From: James Bottomley <James.Bottomley@suse.de>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
mark gross <markgross@thegnar.org>,
David Alan Gilbert <linux@treblig.org>,
linux-kernel@vger.kernel.org, Len <len.brown@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [Patch] idle governor: Avoid lock acquisition to read pm_qos before entering idle
Date: Thu, 10 Feb 2011 11:45:13 -0600 [thread overview]
Message-ID: <1297359914.4933.56.camel@mulgrave.site> (raw)
In-Reply-To: <1297300864.2645.128.camel@schen9-DESK>
On Wed, 2011-02-09 at 17:21 -0800, Tim Chen wrote:
> I noticed that before entering idle state, the menu idle governor will
> look up the current pm_qos value according to the list of qos request
> received. This look up currently needs the acquisition of a lock to go
> down a list of qos requests to find the qos value, slowing down the
> entrance into idle state due to contention by multiple cpus to traverse
> this list. The contention is severe when there are a lot of cpus waking
> and going into idle. For example, for a simple workload that has 32
> pair of processes ping ponging messages to each other, where 64 cores
> cores are active in test system, I see the following profile:
>
> - 37.82% swapper [kernel.kallsyms] [k]
> _raw_spin_lock_irqsave
> - _raw_spin_lock_irqsave
> - 95.65% pm_qos_request
> menu_select
> cpuidle_idle_call
> - cpu_idle
> 99.98% start_secondary
>
> Perhaps a better approach will be to cache the updated pm_qos value so
> reading it does not require lock acquisition as in the patch below.
>
> Tim
>
> Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
What you say is true as long as the value is 32 bits ... perhaps a note
of that should be made somewhere?
Otherwise, it looks like a good lockless optimisation on the read path,
so you can add my ack.
James
next prev parent reply other threads:[~2011-02-10 17:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 1:21 Tim Chen
2011-02-10 3:46 ` Andi Kleen
2011-02-10 18:59 ` Rafael J. Wysocki
2011-02-10 5:10 ` mark gross
2011-02-10 16:20 ` Andi Kleen
2011-02-10 17:27 ` Tim Chen
2011-02-10 17:45 ` James Bottomley [this message]
2011-02-10 18:50 ` Rafael J. Wysocki
2011-02-10 19:33 ` Tim Chen
2011-02-10 20:37 ` James Bottomley
2011-02-10 17:55 ` mark gross
2011-02-10 23:17 ` Rafael J. Wysocki
2011-02-11 0:50 ` Tim Chen
2011-02-11 19:22 ` Rafael J. Wysocki
2011-02-11 19:27 ` Tim Chen
2011-02-11 19:33 ` James Bottomley
2011-02-11 20:03 ` Tim Chen
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=1297359914.4933.56.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=markgross@thegnar.org \
--cc=rjw@sisk.pl \
--cc=tim.c.chen@linux.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
all inboxes | Powered by JetHome®