From: Jes Sorensen <jes@sgi.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: hawkes@sgi.com, Tony Luck <tony.luck@gmail.com>,
Andrew Morton <akpm@osdl.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Jack Steiner <steiner@sgi.com>, Robin Holt <holt@sgi.com>,
Dimitri Sivanich <sivanich@sgi.com>
Subject: Re: [PATCH] ia64: simplify and fix udelay()
Date: Wed, 15 Feb 2006 14:56:20 +0000 [thread overview]
Message-ID: <yq0y80cy8kr.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <200602150908.k1F98dg02934@unix-os.sc.intel.com>
>>>>> "Ken" = Chen, Kenneth W <kenneth.w.chen@intel.com> writes:
Ken> hawkes@sgi.com wrote on Tuesday, February 14, 2006 10:40 AM
>> a preemption and migration to another CPU during the while-loop
Ken> Off topic from the subject line a bit, but related: how many
Ken> Altix SN2 customers in the field turn on CONFIG_PREEMPT? Redhat
Ken> EL4 doesn't turn on preempt, SuSE SLES9 and SLES10 beta don't
Ken> turn it on either. Is there a real benefit of turning that
Ken> option on for SN2?
Ken,
Not sure if any do, however as long as it's a supported kernel option
then we ought to make sure the kernel is reliable under it. Who knows,
at some point some distro might even decide to switch it on as well
(as much as I would discourage doing so ;).
Cheers,
Jes
next prev parent reply other threads:[~2006-02-15 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 18:33 [PATCH] ia64: simplify and fix udelay() hawkes
2006-02-13 21:28 ` Andreas Schwab
2006-02-14 18:40 ` hawkes
2006-02-15 9:08 ` Chen, Kenneth W
2006-02-15 14:56 ` Jes Sorensen [this message]
2006-02-15 15:08 ` Jack Steiner
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=yq0y80cy8kr.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=akpm@osdl.org \
--cc=hawkes@sgi.com \
--cc=holt@sgi.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sivanich@sgi.com \
--cc=steiner@sgi.com \
--cc=tony.luck@gmail.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