mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ram Gupta" <ram.gupta5@gmail.com>
To: "Michal Schmidt" <xschmi00@stud.feec.vutbr.cz>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
	"linux mailing-list" <linux-kernel@vger.kernel.org>
Subject: Re: select takes too much time
Date: Fri, 14 Apr 2006 09:54:21 -0500	[thread overview]
Message-ID: <728201270604140754g7bf955d6y5e06bc5ce4f86c7b@mail.gmail.com> (raw)
In-Reply-To: <443EC09C.2050409@stud.feec.vutbr.cz>

> Of course you can't get lower resolution than 1/HZ, unless you're using
> a kernel with high-res timers. It's always been like that.
> But it's not Ram's problem, because he's requesting a timeout of 90ms,
> which is much longer than one tick even with HZ=100.
>
> Michal
>

So it seems that the only solution to return back right away after
timeout is to play around with the scheduler or put the process doing
select at the front of the queue so it get a chance to run first.
Is there any other better way to do it?

  reply	other threads:[~2006-04-14 14:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 15:01 Ram Gupta
2006-04-13 15:30 ` Andreas Mohr
2006-04-13 16:11   ` Ram Gupta
2006-04-20  9:01     ` Denis Vlasenko
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 [this message]
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=728201270604140754g7bf955d6y5e06bc5ce4f86c7b@mail.gmail.com \
    --to=ram.gupta5@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=xschmi00@stud.feec.vutbr.cz \
    /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

all inboxes | Powered by JetHome®