From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Olivier Doucet <webmaster@ajeux.com>,
Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org,
Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: Performance issue since 3.2.6
Date: Sat, 18 May 2013 10:34:57 +0530 [thread overview]
Message-ID: <51970BF9.7070602@linux.vnet.ibm.com> (raw)
In-Reply-To: <1426477.y1e3fnLN2J@vostro.rjw.lan>
On 05/18/2013 05:21 AM, Rafael J. Wysocki wrote:
> On Saturday, May 18, 2013 01:20:10 AM Srivatsa S. Bhat wrote:
>> On 05/17/2013 11:47 PM, Olivier Doucet wrote:
>>> Hello,
>>>
>>> This performance penalty is still present in kernel 3.9.2. And
>>> CONFIG_PM cannot be deactivated anymore.
>>>
>>> I was able to make a working 3.9.2 (meaning with no penalty) with
>>> following config and patch :
>>> CONFIG_PM=y
>>> CONFIG_PM_SLEEP=y
>>> CONFIG_PM_SLEEP_SMP=y
>>> CONFIG_CPU_IDLE=y
>>> CONFIG_ACPI=y
>>> CONFIG_ACPI_PROCESSOR=y
>>>
>>> Patch : https://gist.github.com/odoucet/5600630
>>>
[...]
>> So, to summarize my thoughts:
>> - IMHO there is no regression here, you just depended on a bug included
>> in 3.2.0 (which made it behave like idle=poll with CONFIG_PM=n) and
>> started your comparisons from there. The later kernels (3.2.6+) got
>> that bug fixed which is why you saw "performance drops".
>>
>> - As much as we would like to do it, we can't set the value of
>> PM_QOS_CPU_DMA_LAT_DEFAULT_VALUE to 0 when CONFIG_PM=n, because
>> CONFIG_PM doesn't encompass all power-management features (which is
>> a pity). Doing that would need a big overhaul of all the relevant
>> Kconfigs, which might or might not be worth the effort. (Because, who
>> says that CONFIG_PM=n kernels are supposed to eat power like crazy??)
>
> I think it *is* worth the effort. We could drop some CONFIG_PM* options in the
> process which would simplify things quite a bit too.
>
Ah, ok..
>> So here is my suggestion - use the interfaces provided by the kernel to
>> fix your problem:
>> - you can give idle=poll in the kernel command line,
>> - OR you can echo 0 > /dev/cpu_dma_latency
>>
>> Irrespective of your kernel configuration options (CONFIG_PM=y/n), the
>> CPUs will not enter deep idle states, giving you the performance
>> improvement that you are looking for.
>
> Thanks a lot for the very clear explanation of this!
>
No problem! :-)
Regards,
Srivatsa S. Bhat
prev parent reply other threads:[~2013-05-18 5:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 21:05 Performance issue since 3.2.6 Olivier Doucet
2013-01-18 21:24 ` Borislav Petkov
2013-01-18 21:46 ` Rafael J. Wysocki
2013-01-18 21:43 ` Olivier Doucet
2013-01-18 22:17 ` Rafael J. Wysocki
2013-01-21 13:18 ` Olivier Doucet
2013-01-21 13:29 ` Rafael J. Wysocki
2013-01-21 14:26 ` Olivier Doucet
2013-01-21 22:49 ` Rafael J. Wysocki
2013-01-21 22:57 ` Olivier Doucet
2013-01-21 23:09 ` Rafael J. Wysocki
2013-01-31 15:15 ` Olivier Doucet
2013-02-12 21:09 ` Olivier Doucet
2013-05-17 18:17 ` Olivier Doucet
2013-05-17 19:50 ` Srivatsa S. Bhat
2013-05-17 23:51 ` Rafael J. Wysocki
2013-05-18 5:04 ` Srivatsa S. Bhat [this message]
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=51970BF9.7070602@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=webmaster@ajeux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.