On Thursday 13 April 2006 19:11, Ram Gupta wrote:
> On 4/13/06, Andreas Mohr <[email protected]> wrote:
> > Hi,
> >
> > Now if you have issues with select() taking too long, then I'd say tough
> > luck, that's life, other processes seem more important than y
> >
> > Or, to put it differently, select() doesn't have realtime guarantees, i.e.
> > there's no way for you to boldly assume that once select() times out
> > your process will continue to run instantly within microseconds.
>
> I was not expecting it to run instantly within microseconds but 1
> second seemed to me too much
Which processes are running on your system?
Try to stop almost all processes and retest on almost idle machine.
It is works (wakes up in 90ms) then all is working as designed.
If you want select() to wake up earlier than competing
processes, you have to inform scheduler that your task
is "more important". Use "nice" for that.
--
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
