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: Fri, 6 Apr 2012 11:18:03 +0200 (CEST) [thread overview]
Message-ID: <588810225.17969.1333703883646.JavaMail.www@wwinf1g24> (raw)
In-Reply-To: <20120405143918.GE27672@linux.vnet.ibm.com>
> Message du 05/04/12 16:40
> De : "Paul E. McKenney"
> A : "Pascal CHAPPERON"
> Copie à : "Josh Boyer" , linux-kernel@vger.kernel.org, kernel-team@fedoraproject.org
> Objet : Re: RCU related performance regression in 3.3
>
> On Thu, Apr 05, 2012 at 04:15:33PM +0200, Pascal CHAPPERON wrote:
> > Hello,
> >
> > I didn't notice any significant slowdown while the system is up and running.
A full kernel compilation (make -j 16) takes 14mn with both 3.2.10 and 3.3.0.
>
> OK, so the natural approach is to disable CONFIG_RCU_FAST_NO_HZ at
> boot time. Unfortunately, you appear to need it to remain disabled
> through at least filesystem mounting, which if I understand correctly
> happens long after system_state gets set to SYSTEM_RUNNING.
>
In fact, I need it to remain disable until all the systemd units are completed.
Some units, such as NetworkManager can take longer time to complete with
RCU_FAST_NO_HZ enabled.
And i need it to be disabled at shutdown, as umounting cgroups, sysfs, etc.
plus old-root mounting can take one plain second for each umounting.
> If RCU has some way to find out when init is complete, I can easily
> make it so that CONFIG_RCU_FAST_NO_HZ optimizes for speed during boot
> and energy efficiency during runtime.
>
I said that I didn't noticed significant slowdown during runtime, but my
laptop usage is basic. Some specific tasks similar to systemd may
perhaps be impacted by this feature.
I can test a task/program that could stress RCU_FAST_NO_HZ if any ?
> One thing I could easily do would be to provide a sysfs parameter or
> some such that allows the boot process to enable energy-efficiency
> mode at runtime. I would much prefer to make this automatic, though.
>
So the feature is disabled until you trigger a sysfs parameter, and can be
disabled before shutdown ? It would be fair, at least for hardware like my
own.
> Other thoughts?
>
Do you think that the culprit is a buggy hardware in my laptop, or the
number of cpu/threads ?
> Thanx, Paul
>
Resent in plain text because rejected. Sorry, i forgot the rules.
Pascal
next prev parent reply other threads:[~2012-04-06 9:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 15:27 RCU related performance regression in 3.3 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-04-27 12:15 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
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
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=588810225.17969.1333703883646.JavaMail.www@wwinf1g24 \
--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