From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: fritzsch <fritzsch@cip.physik.uni-muenchen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: running only 1 process on 1 cpu
Date: Tue, 16 May 2006 21:49:07 +0200 [thread overview]
Message-ID: <9a8748490605161249t33e6343bj4a4610d0b2958f03@mail.gmail.com> (raw)
In-Reply-To: <1147807902.6647.12.camel@localhost.localdomain>
On 16/05/06, fritzsch <fritzsch@cip.physik.uni-muenchen.de> wrote:
> Hallo,
> i have one process, which i want to run on a cpu (> CPU0). The special
> thing here is, that this process is very time critical and should NOT
> be interrupted by anything (cpusets/cpus_allowed would not be enough).
> (the process is not doing any system calls and is communicating to the
> world by shared memory).
> so i wanted to run the process on a CPU1, when all irqs are disabled and
> so the process could not be interrupted.
>
>
> I tried very simple to
>
> (1) migrate all processes to CPU0 by cpu_set_allowed
> (2) gave my process (running on CPU1) the highest priority
> (3) run schedule and make sure that the irqs are disables
> (disable_irqs())
> ...
>
Some ideas :
- Play with CPU affinity : "man sched_setaffinity" / "man sched_getaffinity" [1]
- Try a RealTime patched kernel (Ingo's -rt patchset) and set the
processes nice level to least nice & RT priority to the max [2]
- Implement the code as a kernel module if it really is that time critical
[1] http://www.linuxjournal.com/article/6799
[2] http://www.captain.at/howto-linux-real-time-patch.php
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-05-16 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 19:31 fritzsch
2006-05-16 19:49 ` Jesper Juhl [this message]
2006-05-17 7:45 ` Andreas Mohr
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=9a8748490605161249t33e6343bj4a4610d0b2958f03@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=fritzsch@cip.physik.uni-muenchen.de \
--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
all inboxes | Powered by JetHome®