From: "Luck, Tony" <tony.luck@intel.com>
To: Robin Holt <holt@sgi.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>, Keith Owens <kaos@sgi.com>,
Dimitri Sivanich <sivanich@sgi.com>
Subject: Re: [PATCH] ia64: disable preemption in udelay()
Date: Fri, 16 Dec 2005 09:33:42 -0800 [thread overview]
Message-ID: <20051216173342.GA12205@agluck-lia64.sc.intel.com> (raw)
In-Reply-To: <20051216122854.GA10375@lnx-holt.americas.sgi.com>
On Fri, Dec 16, 2005 at 06:28:54AM -0600, Robin Holt wrote:
> > +#define SMALLUSECS 100
>
> John, I did not see your posts until this had already made it out.
> I would think that the folks running realtime applications would expect
> udelay to hold off for even shorter periods of time. I would expect
> something along the line of 20 or 25 uSec.
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.
We can make fine tune changes to the udelay() implementation after we
get some data on what is needed.
> How much drift would you expect from this? I have not tried this, but
> what about something more along the lines of:
>
> #define MAX_USECS_WHILE_NOT_PREMPTIBLE 20
As we reduce the non-preemtible window drift in my version of udelay()
would get worse ... but I haven't done any measurements on how much worse.
> timeout += next * local_cpu_data->cyc_per_usec;
> while (ia64_get_itc() < timeout)
> cpu_relax();
Bad news if your ar.itc wraps around (less than four centuries of uptime
at 1.6GHz :-)
-Tony
next prev parent reply other threads:[~2005-12-16 17:33 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 [this message]
2005-12-16 18:39 ` John Hawkes
-- 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=20051216173342.GA12205@agluck-lia64.sc.intel.com \
--to=tony.luck@intel.com \
--cc=akpm@osdl.org \
--cc=hawkes@sgi.com \
--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 \
/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).