From: "Dâniel Fraga" <fragabr@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 3.10.0: Full dynticks = high load
Date: Thu, 11 Jul 2013 06:49:04 -0300 [thread overview]
Message-ID: <krlv29$jbp$1@ger.gmane.org> (raw)
I upgraded to kernel 3.10.0 and decided to try the new "Full
dynticks system (tickless)" option, but now the system load is always
at 1 or above.
Using the previous "Idle dynticks system (tickless idle)" solves
the problem, so it seems the new Full dynticks code is causing this.
Maybe Ingo Molnar can help to debug this (I put this in Power
Management, but if it should be in other area, please change).
My desktop is:
Asus P8Z68-V Pro/Gen3
Core i7 2700k
8GB RAM
Feel free to suggest how can I debug this to help you. I can try
patches if you want.
Thank you.
--
Linux 3.10.0: Unicycling Gorilla
http://www.youtube.com/DanielFragaBR
http://www.libertarios.org.br
next reply other threads:[~2013-07-11 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 9:49 Dâniel Fraga [this message]
2013-07-12 6:52 ` 3.10.0: Full dynticks = high load Heinz Diehl
2013-07-15 13:05 ` Dâniel Fraga
2013-07-15 13:36 ` Mike Galbraith
2013-07-15 14:25 ` Frederic Weisbecker
2013-07-15 14:51 ` Dâniel Fraga
2013-07-15 15:01 ` Frederic Weisbecker
2013-07-15 18:50 ` Dâniel Fraga
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='krlv29$jbp$1@ger.gmane.org' \
--to=fragabr@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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