From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel thread scheduling question
Date: Tue, 30 Mar 2004 15:17:43 +1000 [thread overview]
Message-ID: <406902F7.8030805@yahoo.com.au> (raw)
In-Reply-To: <4068F3E7.9060005@candelatech.com>
Ben Greear wrote:
> I have a kernel thread that I would like to have run at least
> every 1-2 miliseconds.
>
> I think I would be happy if there were a way to have the
> process yield/schedule() at least once per ms with the
> understanding that it would get to wake again 1-2ms later.
> Is there a way to do such a thing without hacking up the
> scheduler code?
>
> I have tried 2.6.4 with pre-empt, and setting the thread priority
> to -18, but I still see cases where the process is starved for 20+
> milliseconds every 3-5 seconds or so. Other than this single
> process, there is not a big load on the system.
>
Use realtime scheduling. sched_setscheduler (2) is a good
place to start.
prev parent reply other threads:[~2004-03-30 5:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 4:13 kernel thread scheduling question Ben Greear
2004-03-30 5:17 ` Nick Piggin [this message]
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=406902F7.8030805@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
/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