From: Pascal Chapperon <pascal.chapperon@wanadoo.fr>
To: paulmck@linux.vnet.ibm.com
Cc: Josh Boyer <jwboyer@redhat.com>,
linux-kernel@vger.kernel.org, kernel-team@fedoraproject.org
Subject: Re: RCU related performance regression in 3.3
Date: Thu, 10 May 2012 10:40:05 +0200 [thread overview]
Message-ID: <4FAB7EE5.8010507@wanadoo.fr> (raw)
In-Reply-To: <20120504231442.GT2411@linux.vnet.ibm.com>
Le 05/05/2012 01:14, Paul E. McKenney a écrit :
> On Fri, May 04, 2012 at 11:41:13PM +0200, Pascal Chapperon wrote:
>> Le 04/05/2012 17:04, Paul E. McKenney a écrit :
>>> On Fri, May 04, 2012 at 04:42:54PM +0200, Pascal Chapperon wrote:
>>>> Le 01/05/2012 17:45, Paul E. McKenney a écrit :
>>>>
>>>>> Here is my RCU_FAST_NO_HZ patch stack on top of v3.4-rc4.
>>>>>
>>>>> Or you can pull branch fnh.2012.05.01a from:
>>>>>
>>>>> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
>>>>>
>>>>> Thanx, Paul
>>>>>
>>>> I applied your global patch on top of v3.4-rc4. But the slowdown is
>>>> worse than before : boot sequence took 80s instead 20-30s (12s for
>>>> initramfs instead of 2s).
>>>>
>>>> I'll send you rcu tracing log in a second mail.
>>>
>>> Hmmm... Well, I guess I am glad that I finally did something that
>>> had an effect, but I sure wish that the effect had been in the other
>>> direction!
>>>
>>> Just to make sure I understand: the difference between the 20-30s and
>>> the 80s is exactly the patch I sent you?
>>>
>>> Thanx, Paul
>>>
>>>
>> Yes. Exactly same kernel config as in previous results, I applied
>> your patch against v3.4-rc4, and sorry, the result is exactly what I
>> said;
>> I saw that your global patch was quite huge, and addresses things which
>> are not directly related with the initial patch (commit
>> 7cb92499000e3c86dae653077b1465458a039ef6); maybe a side effect?
>>
>> However, I'm ready to try this patch on my smaller laptop which
>> supports well CONFIG_FAST_NO_HZ=y and systemd, if you think it can
>> help ?
>>
>> Another thought: this issue as nothing to do with i7 Hyper-threading
>> capacities ? (as I test core2duo, Pentium ulv in same conditions and I
>> don't encountered any slowdown ?)
>
> Well, one possibility is that your setup starts the jiffies counter
> at some interesting value. The attached patch (also against v3.4-rc4)
> applies a bit more paranoia to the initialization to handle this
> and other possibilities.
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
I tried your new patch against v3.4-rc5 and saw no improvement :
still 75 s. for the boot sequence.
I'll send you the logs in a second mail.
Pascal
next prev parent reply other threads:[~2012-05-10 8:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 12:15 RCU related performance regression in 3.3 Pascal Chapperon
2012-04-28 3:42 ` Paul E. McKenney
2012-05-01 0:02 ` Paul E. McKenney
2012-05-01 8:55 ` Pascal Chapperon
2012-05-01 15:45 ` Paul E. McKenney
2012-05-04 14:42 ` Pascal Chapperon
2012-05-04 15:04 ` Paul E. McKenney
2012-05-04 21:41 ` Pascal Chapperon
2012-05-04 23:14 ` Paul E. McKenney
2012-05-10 8:40 ` Pascal Chapperon [this message]
2012-05-14 22:32 ` Paul E. McKenney
2012-05-18 11:01 ` Pascal Chapperon
2012-05-18 12:14 ` Paul E. McKenney
2012-05-18 14:48 ` Pascal Chapperon
-- strict thread matches above, loose matches on Subject: below --
2012-04-04 15:27 Josh Boyer
2012-04-04 21:36 ` Paul E. McKenney
2012-04-05 12:37 ` Josh Boyer
2012-04-05 14:00 ` Paul E. McKenney
2012-04-05 14:15 ` Pascal CHAPPERON
2012-04-05 14:39 ` Paul E. McKenney
2012-04-06 9:18 ` Pascal Chapperon
2012-04-10 16:07 ` Paul E. McKenney
2012-04-11 15:06 ` Pascal
2012-04-12 18:04 ` Paul E. McKenney
2012-04-16 21:02 ` Paul E. McKenney
2012-04-18 9:37 ` Pascal Chapperon
2012-04-18 14:01 ` Paul E. McKenney
2012-04-18 15:00 ` Pascal Chapperon
2012-04-18 15:23 ` Paul E. McKenney
2012-04-20 14:45 ` Pascal Chapperon
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=4FAB7EE5.8010507@wanadoo.fr \
--to=pascal.chapperon@wanadoo.fr \
--cc=jwboyer@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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).