From: Manfred Spraul <manfred@colorfullife.com>
To: paulmck@linux.vnet.ibm.com, mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
oleg@tv-sign.ru, dipankar@in.ibm.com, rostedt@goodmis.org,
dvhltc@us.ibm.com, niv@us.ibm.com
Subject: nohz_cpu_mask question (was: Re: [PATCH tip/core/rcu] classic RCU locking and memory-barrier cleanups)
Date: Tue, 19 Aug 2008 19:16:32 +0200 [thread overview]
Message-ID: <48AAFFF0.7020405@colorfullife.com> (raw)
In-Reply-To: <20080819140339.GF7106@linux.vnet.ibm.com>
Hi all,
can someone explain me nohz_cpu_mask?
If I understand it correctly, it merely means that this cpu does not
take timer interrupts, correct?
The cpu can still take "real" interupts, e.g. a nic interrupt. The cpu
could also do softirq processing.
Is that correct? Ingo?
If nohz cpus can take normal interrupts, then it would be wrong to
exclude these cpus from the mask of cpus that must pass a quiescent
cycle - a softirq could hold on a pointers.
--
Manfred
next prev parent reply other threads:[~2008-08-19 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 16:21 [PATCH tip/core/rcu] classic RCU locking and memory-barrier cleanups Paul E. McKenney
2008-08-05 16:48 ` Steven Rostedt
2008-08-05 17:40 ` Paul E. McKenney
2008-08-06 5:30 ` Manfred Spraul
2008-08-07 3:18 ` Paul E. McKenney
2008-08-18 9:13 ` Manfred Spraul
2008-08-18 14:04 ` Paul E. McKenney
2008-08-19 10:48 ` Manfred Spraul
2008-08-19 14:03 ` Paul E. McKenney
2008-08-19 17:16 ` Manfred Spraul [this message]
2008-08-19 17:41 ` nohz_cpu_mask question (was: Re: [PATCH tip/core/rcu] classic RCU locking and memory-barrier cleanups) Paul E. McKenney
2008-08-15 14:09 ` [PATCH tip/core/rcu] classic RCU locking and memory-barrier cleanups Ingo Molnar
2008-08-15 14:24 ` Ingo Molnar
2008-08-15 14:56 ` Ingo Molnar
2008-08-15 14:58 ` Paul E. McKenney
2008-08-17 14:37 ` [PATCH tip/core/rcu] classic RCU locking cleanup fix lockdep problem Paul E. McKenney
2008-08-17 15:38 ` Ingo Molnar
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=48AAFFF0.7020405@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=oleg@tv-sign.ru \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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