From: Thomas Gleixner <tglx@linutronix.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: Marcio Saito <marcio@cyclades.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Jiri Slaby <jirislaby@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
John Stultz <johnstul@us.ibm.com>,
x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
Tim Pepper <lnxninja@linux.vnet.ibm.com>,
jblunck@infradead.org, Ingo Molnar <mingo@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Avantika Mathur <mathur@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC] [PATCH] allow low HZ values?
Date: Tue, 12 Oct 2010 18:56:23 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1010121854430.2909@localhost6.localdomain6> (raw)
In-Reply-To: <871v7v32kn.fsf@basil.nowhere.org>
On Tue, 12 Oct 2010, Andi Kleen wrote:
> Thomas Gleixner <tglx@linutronix.de> writes:
> > We have told HPC folks for years that we need a kind of "NOHZ" mode
> > for HPC where we can transparently switch off the tick when only one
> > user space bound thread is active and switch back to normal once this
> > thing terminates or goes into the kernel via a syscall. Sigh, nothing
> > happened ever except for repeating the same crap patches over and
> > over.
>
> Jan Blunck posted a patch for this exactly few months ago.
> Unfortunately it didn't get the accounting right, but other than
> that it seemed like a reasonable starting point.
Unfortunately it did not get a lot of other things right either.
Thanks,
tglx
next prev parent reply other threads:[~2010-10-12 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 20:11 [RFC] [PATCH] allow low HZ values? Tim Pepper
2010-10-11 20:32 ` Thomas Gleixner
2010-10-11 21:11 ` Tim Pepper
2010-10-12 14:31 ` Andi Kleen
2010-10-12 16:56 ` Thomas Gleixner [this message]
2010-10-11 22:30 ` Benjamin Herrenschmidt
2010-10-11 22:33 ` Thomas Gleixner
2010-10-11 22:47 ` H. Peter Anvin
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=alpine.LFD.2.00.1010121854430.2909@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jblunck@infradead.org \
--cc=jirislaby@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lnxninja@linux.vnet.ibm.com \
--cc=marcio@cyclades.com \
--cc=mathur@linux.vnet.ibm.com \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=x86@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