From: Dipankar Sarma <dipankar@in.ibm.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: akpm@osdl.org, hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (9/9): no timer interrupts in idle.
Date: Thu, 29 Apr 2004 17:36:41 +0530 [thread overview]
Message-ID: <20040429120641.GB3663@in.ibm.com> (raw)
In-Reply-To: <OF8DC2156F.441E947F-ONC1256E85.002E0C3D-C1256E85.002E2DB9@de.ibm.com>
On Thu, Apr 29, 2004 at 10:24:23AM +0200, Martin Schwidefsky wrote:
>
> > idle_cpu_mask does not really represent CPUs that are conventionally
> > called "idle", it represents the ones that have hz timer switched
> > off (in your patch). So, why not just call it nohz_cpu_mask ?
> > RCU doesn't need an idle cpu mask, it has its own mechanism
> > for detecting idle cpus, it just needs to know about the ones
> > that have hz timers switched off. If you call it nohz_cpu_mask,
> > then it would make sense to say that for systems which do not
> > switch off hz timer, nohz_cpu_mask will always be CPU_MASK_NONE.
>
> Ok, I don't really mind the name change. It's nohz_cpu_mask then.
Thanks. Sorry about the name nitpick, I too didn't think about this
when Jan had first sent me the patch.
Dipankar
next prev parent reply other threads:[~2004-04-29 12:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 8:24 [PATCH] s390 (9/9): no timer interrupts in idle Martin Schwidefsky
2004-04-29 12:06 ` Dipankar Sarma [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 7:43 Martin Schwidefsky
2004-04-29 8:16 ` Dipankar Sarma
2004-04-23 8:48 Martin Schwidefsky
2004-04-22 14:56 Martin Schwidefsky
2004-04-28 19:07 ` Dipankar Sarma
2004-04-22 12:44 Martin Schwidefsky
2004-04-22 13:11 ` Arjan van de Ven
2004-04-23 3:32 ` George Anzinger
2004-04-22 12:14 Martin Schwidefsky
2004-04-22 12:25 ` Arjan van de Ven
2004-04-22 11:09 Martin Schwidefsky
2004-04-22 11:14 ` Arjan van de Ven
2004-04-22 10:53 Martin Schwidefsky
2004-04-22 10:56 ` Arjan van de Ven
2004-04-22 8:55 Martin Schwidefsky
2004-04-22 8:48 Martin Schwidefsky
2004-04-22 8:52 ` Arjan van de Ven
[not found] <1Nt5d-84u-3@gated-at.bofh.it>
[not found] ` <1NwPD-2RW-37@gated-at.bofh.it>
[not found] ` <1NwPE-2RW-39@gated-at.bofh.it>
[not found] ` <1Nx8Y-3ev-15@gated-at.bofh.it>
2004-04-21 22:38 ` Andi Kleen
2004-04-21 18:52 Martin Schwidefsky
2004-04-21 21:58 ` Dipankar Sarma
2004-04-21 16:37 Martin Schwidefsky
2004-04-21 20:43 ` Dipankar Sarma
2004-04-21 20:46 ` Christoph Hellwig
2004-04-21 21:01 ` Dipankar Sarma
2004-04-21 16:31 Martin Schwidefsky
2004-04-21 16:32 ` Christoph Hellwig
2004-04-21 14:49 Martin Schwidefsky
2004-04-21 15:31 ` Christoph Hellwig
2004-04-22 8:02 ` Arjan van de Ven
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=20040429120641.GB3663@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.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