From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: svaidy@linux.vnet.ibm.com
Cc: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org, anton@samba.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpuidle: powernv/pseries: Decrease the snooze residency
Date: Sat, 30 May 2015 13:30:23 +0530 [thread overview]
Message-ID: <55696E17.2030700@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150530060141.GA19134@dirshya.in.ibm.com>
On 05/30/2015 11:31 AM, Vaidyanathan Srinivasan wrote:
> * Preeti U Murthy <preeti@linux.vnet.ibm.com> [2015-05-29 19:17:17]:
>
> [snip]
>
>>> + if (max_idle_state > 1) {
>>> + snooze_timeout_en = true;
>>> + snooze_timeout = cpuidle_state_table[1].target_residency *
>>> + tb_ticks_per_usec;
>>> + }
>>
>> Any idea why we don't have snooze defined on the shared lpar configuration ?
>
> In shared lpar case, spinning in guest context may potentially take
> away cycles from other lpars waiting to run on the same physical cpu.
>
> So the policy in shared lpar case is to let PowerVM hypervisor know
> immediately that the guest cpu is idle which will allow the hypervisor
> to use the cycles for other tasks/lpars.
>
Oh Ok! Thanks for the clarification !
Regards
Preeti U Murthy
> --Vaidy
>
next prev parent reply other threads:[~2015-05-30 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 12:32 [PATCH] cpuidle: powernv/pseries: Decrease the snooze residency Shilpasri G Bhat
2015-05-29 13:47 ` Preeti U Murthy
2015-05-30 6:01 ` Vaidyanathan Srinivasan
2015-05-30 8:00 ` Preeti U Murthy [this message]
2015-05-31 1:38 ` Benjamin Herrenschmidt
2015-06-03 15:35 ` Vaidyanathan Srinivasan
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=55696E17.2030700@linux.vnet.ibm.com \
--to=preeti@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rjw@rjwysocki.net \
--cc=shilpa.bhat@linux.vnet.ibm.com \
--cc=svaidy@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).