From: Denis Vlasenko <vda@ilport.com.ua>
To: "Ram Gupta" <ram.gupta5@gmail.com>
Cc: "Andreas Mohr" <andi@rhlx01.fht-esslingen.de>,
"linux mailing-list" <linux-kernel@vger.kernel.org>
Subject: Re: select takes too much time
Date: Thu, 20 Apr 2006 12:01:50 +0300 [thread overview]
Message-ID: <200604201201.50981.vda@ilport.com.ua> (raw)
In-Reply-To: <728201270604130911y4adf9967kd38712e731161074@mail.gmail.com>
On Thursday 13 April 2006 19:11, Ram Gupta wrote:
> On 4/13/06, Andreas Mohr <andi@rhlx01.fht-esslingen.de> 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
next prev parent reply other threads:[~2006-04-20 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 15:01 select takes too much time Ram Gupta
2006-04-13 15:30 ` Andreas Mohr
2006-04-13 16:11 ` Ram Gupta
2006-04-20 9:01 ` Denis Vlasenko [this message]
2006-05-01 17:00 ` Ram Gupta
2006-04-13 15:56 ` linux-os (Dick Johnson)
2006-04-13 18:29 ` Jan Knutar
2006-04-13 18:36 ` Michal Schmidt
2006-04-13 19:51 ` Ram Gupta
2006-04-13 21:08 ` linux-os (Dick Johnson)
2006-04-13 21:18 ` Nish Aravamudan
2006-04-13 21:20 ` Michal Schmidt
2006-04-14 14:54 ` Ram Gupta
2006-04-14 14:56 ` linux-os (Dick Johnson)
2006-04-14 21:45 ` Jan Engelhardt
2006-04-17 15:55 ` Ram Gupta
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=200604201201.50981.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ram.gupta5@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