All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Tim Blechmann <tim@klingt.org>
Cc: Nicholas Mc Guire <der.herr@hofr.at>,
	y@opentech.at, Mark Knecht <markknecht@gmail.com>,
	linux-rt-users@vger.kernel.org
Subject: Re: rt file i/o
Date: Wed, 4 Nov 2009 16:44:13 -0600	[thread overview]
Message-ID: <20091104164413.3aff479c@torg> (raw)
In-Reply-To: <4AF1BAB9.5080104@klingt.org>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

On Wed, 04 Nov 2009 18:32:41 +0100
Tim Blechmann <tim@klingt.org> wrote:

> >> well, if i understand the rt howto correctly, _no_ disc access is
> >> allowed, neither from rt nor from non-rt threads, since it may produce
> >> page faults, which introduce latencies ...
> > 
> > I would be supprised if the rt howto states that page-faults in non-rt
> > threads is a critical problem - that would not significantly impact RT
> > performance - atelast not the worst case - it will (as every other system
> > load) impact the average case. so having a non-rt thread reading disk-files
> > to a buffer and a rt-thread processing this buffer should be perfectly fine.
> 
> that is what i thought for years ... but according to [1] a page fault
> in an rt process freezes the entire process with both rt and non-rt
> threads until the page fault is handled ...
> 

No, we need to get that fixed in the wiki. It may have been the case
that the entire process was frozen while a fault was being handled, but
I don't believe that is the case now. If you're in a thread on core0
and a sibling thread on core1 faults, you shouldn't be impacted unless
you're trying to reference the same memory. 

Clark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-11-04 22:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 15:25 rt file i/o Tim Blechmann
2009-11-04 15:43 ` Mark Knecht
2009-11-04 15:52   ` Tim Blechmann
2009-11-04 17:14     ` Nicholas Mc Guire
2009-11-04 17:32       ` Tim Blechmann
2009-11-04 22:41         ` Nicholas Mc Guire
2009-11-04 22:44         ` Clark Williams [this message]
2009-11-05  4:30           ` Shane M Smith
2009-11-05  9:29           ` Tim Blechmann
2009-11-05 20:30             ` Remy Bohmer
2009-11-05  9:22       ` Sven-Thorsten Dietrich
2009-11-05  4:14     ` Mark Knecht
2009-11-04 17:09 ` Nicholas Mc Guire

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=20091104164413.3aff479c@torg \
    --to=williams@redhat.com \
    --cc=der.herr@hofr.at \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=markknecht@gmail.com \
    --cc=tim@klingt.org \
    --cc=y@opentech.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.