public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: llx@swissonline.ch
Cc: linux-kernel@vger.kernel.org
Subject: Re: misc questions about kernel 2.4.x internals
Date: Mon, 20 Aug 2001 13:49:00 -0700	[thread overview]
Message-ID: <3B8177BC.F8EB3EE@mvista.com> (raw)
In-Reply-To: <200108201452.f7KEqxk18219@mail.swissonline.ch> <3B815D97.680B37A5@mvista.com> <200108201946.f7KJkGk12091@mail.swissonline.ch>

Christian Widmer wrote:
> 
> thanks
> 
> > You would/ could assign it a real time priority and make it SCHED_FIFO
> > or SCHED_RR.
> 
> do you have references to an example how to to it?
> 
> > If you do this, it is a good idea to make the priority
> > used available to be "tuned".  Not every one will agree that _your_
> > handler is as important as you think it is.
> 
> ye i think so - in our cluster it's just fine at the moment :)
> 
> chris
Read the man page on sched_setscheduler(2).  If in the kernel, you would
need to make a system call.  I am afraid I don't know exactly how this
is done, but it is possible.  By the way, some scheduler patches allow
the real time priority to go well above 99, thus if you need this:

#ifndef MAX_PRI
#define MAX_PRI 99
#endif

if you want the maximum priority.

George

  reply	other threads:[~2001-08-20 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-20 14:52 misc questions about kernel 2.4.x internals Christian Widmer
2001-08-20 17:49 ` Daniel Phillips
2001-08-20 18:57 ` george anzinger
2001-08-20 19:46   ` Christian Widmer
2001-08-20 20:49     ` george anzinger [this message]
2001-08-20 20:52 ` Anders Peter Fugmann

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=3B8177BC.F8EB3EE@mvista.com \
    --to=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llx@swissonline.ch \
    /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