From: Thomas Gleixner <tglx@linutronix.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Daniel Walker <dwalker@dwalker1.mvista.com>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: NO_HZ Kconfig rework
Date: Thu, 29 Jun 2006 16:27:38 +0200 [thread overview]
Message-ID: <1151591258.25491.621.camel@localhost.localdomain> (raw)
In-Reply-To: <20060629094231.GA2009@elf.ucw.cz>
Pavel,
On Thu, 2006-06-29 at 11:42 +0200, Pavel Machek wrote:
> On Mon 2006-06-26 09:16:37, Daniel Walker wrote:
> > I got NO_HZ working on ARM, but because the ARM tree already
> > extensively implements NO_IDLE_HZ I had to make NO_HZ a
> > completely seprate option.
>
> So... what is the difference between NO_HZ and NO_IDLE_HZ?
> Pavel
Mostly a development vehicle. This will be removed once we are ready to
merge the existing arch implementations.
tglx
prev parent reply other threads:[~2006-06-29 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 16:16 NO_HZ Kconfig rework Daniel Walker
2006-06-29 9:42 ` Pavel Machek
2006-06-29 14:22 ` Daniel Walker
2006-06-29 14:27 ` Thomas Gleixner [this message]
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=1151591258.25491.621.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=dwalker@dwalker1.mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
/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