From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: fweisbec@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Will CPU 0 be forever prohibited from NO_HZ_FULL status?
Date: Wed, 4 Dec 2013 11:39:57 -0800 [thread overview]
Message-ID: <20131204193957.GA2847@linux.vnet.ibm.com> (raw)
Hello, Frederic,
Just realized that I could further decrease RT latency of one of my "shut
up RCU on NO_HZ_FULL CPUs" patches if I relied on CPU 0 always having
a scheduling-clock tick unless the entire system is idle. The trick
is that I could then rely on CPU 0 to detect RCU CPU stall warnings,
and remove the checking from the other CPUs.
Thoughts?
Thanx, Paul
next reply other threads:[~2013-12-04 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 19:39 Paul E. McKenney [this message]
2013-12-05 1:20 ` Will CPU 0 be forever prohibited from NO_HZ_FULL status? Frederic Weisbecker
2013-12-05 2:50 ` Paul E. McKenney
2013-12-10 14:37 ` Frederic Weisbecker
2013-12-10 15:08 ` Paul E. McKenney
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=20131204193957.GA2847@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fweisbec@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