From: "John Hawkes" <hawkes@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>, "Robin Holt" <holt@sgi.com>
Cc: "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>,
"Keith Owens" <kaos@sgi.com>,
"Dimitri Sivanich" <sivanich@sgi.com>
Subject: Re: [PATCH] ia64: disable preemption in udelay()
Date: Fri, 16 Dec 2005 10:39:34 -0800 [thread overview]
Message-ID: <007001c60270$1066c0c0$6f00a8c0@comcast.net> (raw)
In-Reply-To: 20051216173342.GA12205@agluck-lia64.sc.intel.com
From: "Luck, Tony" <tony.luck@intel.com>
...
> A good question ... I'm going to put John's change in as-is for now so
> that 2.6.15 can benefit from the reduced code size of the out-of-line
> and avoid the ugly bug when preemption is enabled on a drifty system.
Okay, but I'll propose some changes to that soon, probably using Robin Holt's
suggestions. I'm concerned about the impact of interrupts outside of the
inner loop and inside the outer loop, which would increase the effective delay
time.
John Hawkes
next prev parent reply other threads:[~2005-12-16 18:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 2:42 [PATCH] ia64: disable preemption in udelay() hawkes
2005-12-16 12:28 ` Robin Holt
2005-12-16 17:33 ` Luck, Tony
2005-12-16 18:39 ` John Hawkes [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-14 23:25 hawkes
2005-12-15 22:50 ` Luck, Tony
2005-12-16 1:04 ` Luck, Tony
2005-12-16 8:20 ` Christian Hildner
2005-12-16 14:14 ` Alan Cox
2005-12-16 1:52 ` Zwane Mwaikambo
2005-12-16 2:03 ` Lee Revell
2005-12-16 2:12 ` John Hawkes
2005-12-16 2:40 ` Zwane Mwaikambo
2005-12-16 3:19 ` Lee Revell
2005-12-22 21:45 ` Bill Davidsen
2005-12-23 0:14 ` Keith Owens
2005-12-23 6:03 ` Zwane Mwaikambo
2005-12-16 2:37 ` Zwane Mwaikambo
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='007001c60270$1066c0c0$6f00a8c0@comcast.net' \
--to=hawkes@sgi.com \
--cc=akpm@osdl.org \
--cc=holt@sgi.com \
--cc=kaos@sgi.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 \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).