From: Olivier Doucet <webmaster@ajeux.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Borislav Petkov <bp@alien8.de>, linux-kernel@vger.kernel.org
Subject: Re: Performance issue since 3.2.6
Date: Mon, 21 Jan 2013 15:26:10 +0100 [thread overview]
Message-ID: <CAPPqfY3vZX3a-GONmzoWdn7sp=_pzKL2qAKBxYZ9ABNLetKoag@mail.gmail.com> (raw)
In-Reply-To: <2462618.rQxKXSuBtr@vostro.rjw.lan>
>> FYI, I benchmarked a new version with :
>> CONFIG_PM_RUNTIME=y
>> CONFIG_PM=y
>>
>> but the performance loss is still present.
>
> In that case it is not quite likely that the commit you bisected to
> really introduced the problem, because it doesn't change things for
> CONFIG_PM=y.
>
> Does reverting that commit still help?
I tested several combinations. Results follows :
3.2.6 (base) + CONFIG_PM unset => BAD
3.2.6 (base) + CONFIG_PM=y => BAD
3.2.6 (base) + patch reverted + CONFIG_PM=y => BAD
3.2.6 (base) + patch reverted + CONFIG_PM unset => GOOD
So if I understand right, the targeted patch introduced the bug when
CONFIG_PM is unset, but there is an other bug when this var is set.
I'll try to track this commit.
Olivier
next prev parent reply other threads:[~2013-01-21 14:33 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 [this message]
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
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='CAPPqfY3vZX3a-GONmzoWdn7sp=_pzKL2qAKBxYZ9ABNLetKoag@mail.gmail.com' \
--to=webmaster@ajeux.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).