public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Fabiano Ramos <fabramos@bol.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: task switching at Page Faults
Date: Tue, 20 Apr 2004 10:16:14 +0200	[thread overview]
Message-ID: <4084DC4E.3000903@aitel.hist.no> (raw)
In-Reply-To: <1082399579.1146.15.camel@slack.domain.invalid>

Fabiano Ramos wrote:
> Hi all.
> 
> 	I am in doubt about the linux kernel behaviour is this situation:
> supose a have the process A, with the highest realtime
> priority and SCHED_FIFO policy. The process then issues a syscall,
> say read():
> 
> 	1) Can I be sure that there will be no process switch during the
> syscall processing, even if the system call causes a page fault?

A page fault means your realtime process must wait, because the
data it wants isn't available yet. (Data have to be fetched
from disk/device which takes lots of time.)

There is nothing wrong with handing the cpu to some other
lower priority process unser such circumstances, because your realtime
process are stuck and can't use it anyway.

The realtime process wil grab the cpu as soon as it gets ready to run anyway,
I believe the scheduler looks for this sort of thing when the pagefault
eventually completes.

Helge Hafting


  parent reply	other threads:[~2004-04-20  8:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 18:32 task switching at Page Faults Fabiano Ramos
2004-04-19 19:49 ` Mikulas Patocka
2004-04-19 20:12   ` Fabiano Ramos
2004-04-19 23:07     ` Mikulas Patocka
2004-04-20  1:32 ` Richard B. Johnson
2004-04-20  8:16 ` Helge Hafting [this message]
     [not found] <1MN62-7wz-5@gated-at.bofh.it>
     [not found] ` <1MNpu-7QI-35@gated-at.bofh.it>
2004-04-19 21:52   ` Andi Kleen

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=4084DC4E.3000903@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=fabramos@bol.com.br \
    --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