* sleep and wakeup at microsecond boundary
@ 2004-09-04 19:51 NucleoDyne Systems, Inc.
0 siblings, 0 replies; 3+ messages in thread
From: NucleoDyne Systems, Inc. @ 2004-09-04 19:51 UTC (permalink / raw)
To: linux-kernel
Hello,
We have a requirement to implement the sleep and wakeup mechanism
at microsecond boundary in 2.4 kernel. The intent of this mail is to
start a discussion on this topic and collect inputs from the kernel
developers. Any reply on the issues of implementing such a feature will
be greatly appreciated.
Thanks,
Kallol Biswas
--
--
NucleoDyne Corporation
nucleon@nucleodyne.com
www.nucleodyne.com
Phone:408-718-8164
Fax: 408-732-2284
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sleep and wakeup at microsecond boundary
2004-09-07 5:46 ` NucleoDyne Systems, Inc.
@ 2004-09-07 6:13 ` Arjan van de Ven
0 siblings, 0 replies; 3+ messages in thread
From: Arjan van de Ven @ 2004-09-07 6:13 UTC (permalink / raw)
To: nucleon; +Cc: Mike Galbraith, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Tue, 2004-09-07 at 07:46, NucleoDyne Systems, Inc. wrote:
> Hello,
> Let me explain the requirement a little more in detail.
>
> Consider the routine sleep_on_timeout(, timeout) in sched.c:
please don't use this routine. It's severely deprecated.
> On x86 the jiffies is updated every time PIT raises interrupt and
> do_timer() is called, i.e. once in every 10ms.
it's 1ms nowadays....
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sleep and wakeup at microsecond boundary
[not found] <5.2.1.1.2.20040905085650.00b1e640@pop.gmx.net>
@ 2004-09-07 5:46 ` NucleoDyne Systems, Inc.
2004-09-07 6:13 ` Arjan van de Ven
0 siblings, 1 reply; 3+ messages in thread
From: NucleoDyne Systems, Inc. @ 2004-09-07 5:46 UTC (permalink / raw)
To: Mike Galbraith; +Cc: linux-kernel
Hello,
Let me explain the requirement a little more in detail.
Consider the routine sleep_on_timeout(, timeout) in sched.c:
A timer is started and then schedule() is called. The timer expires
after present jiffies + timeout (in jiffies) period.
On x86 the jiffies is updated every time PIT raises interrupt and
do_timer() is called, i.e. once in every 10ms.
So we can set timeout in multiples of 10ms.
We are developing a very powerful system (not x86 based) with multiple
CPUs, one of them will be running linux and will act as a co-processor
for the other CPUs running different OS.
On the CPU running linux we need to be able to call sleep_on_timeout()
with more granular expiration time, may be in multiples of microseconds.
I already have done the investigation and looking for feedback from the
developers on all possible issues.
Hope this explains.
Thanks,
Kallol Biswas
On Sun, 2004-09-05 at 00:09, Mike Galbraith wrote:
> At 12:51 PM 9/4/2004 -0700, NucleoDyne Systems, " "Inc. wrote:
> >Hello,
> > We have a requirement to implement the sleep and wakeup mechanism
> >at microsecond boundary in 2.4 kernel.
>
> I've re-visited this message about 10 times now, so I suppose I'm curious
> enough to ask: why on God's green Earth would someone want to do
> that? (to _any_ kernel, but I'm mostly wondering why [TILT] anyone would
> do such a thing to a GP kernel)
>
> -Mike
On Sat, 2004-09-04 at 12:51, NucleoDyne Systems, Inc. wrote: \
> Hello,
> We have a requirement to implement the sleep and wakeup mechanism
> at microsecond boundary in 2.4 kernel. The intent of this mail is to
> start a discussion on this topic and collect inputs from the kernel
> developers. Any reply on the issues of implementing such a feature will
> be greatly appreciated.
>
> Thanks,
> Kallol Biswas
--
--
NucleoDyne Corporation
nucleon@nucleodyne.com
www.nucleodyne.com
--
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-09-07 6:13 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-09-04 19:51 sleep and wakeup at microsecond boundary NucleoDyne Systems, Inc.
[not found] <5.2.1.1.2.20040905085650.00b1e640@pop.gmx.net>
2004-09-07 5:46 ` NucleoDyne Systems, Inc.
2004-09-07 6:13 ` Arjan van de Ven
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®