From: Primiano Tucci <p.tucci@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
tglx <tglx@linutronix.de>
Subject: Re: Considerations on sched APIs under RT patch
Date: Wed, 21 Apr 2010 22:38:36 +0200 [thread overview]
Message-ID: <s2tc5b2c05b1004211338y814bc3b2o547a6eecdf64ca7f@mail.gmail.com> (raw)
In-Reply-To: <1271879833.1776.186.camel@laptop>
> No, any syscall can end up blocking/scheduling there are no exceptions.
> But blocking doesn't mean its non-deterministic, esp. when coupled with
> things like PI.
>
> But you do have to treat system resources as such, that is they can (and
> will) create cross-cpu dependencies, if you do not take that into
> account you will of course be surprised.
>
I actually don't understand why do you recall PI so frequently, it
seems to be the unique point of interest.
Actually I take care about not sharing cross-cpu resources, but I
cannot take care of what the kernel should do.
In my viewpoint is unacceptable that the scheduler apis can led into a
rescheduling.
It voids any form of process control.
If I lose the control while controlling other processes, Quis
custodiet ipsos custodes?
P.S. It actually does not happen in other RTOSes, e.g., VxWorks SMP
Primiano,
--
Primiano Tucci
http://www.primianotucci.com
next prev parent reply other threads:[~2010-04-21 20:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 20:48 Primiano Tucci
2010-04-20 9:20 ` Peter Zijlstra
2010-04-20 21:56 ` Primiano Tucci
2010-04-20 23:00 ` Steven Rostedt
2010-04-21 5:16 ` Primiano Tucci
2010-04-21 8:49 ` Peter Zijlstra
2010-04-21 12:46 ` Steven Rostedt
2010-04-21 19:24 ` Primiano Tucci
2010-04-21 19:57 ` Peter Zijlstra
2010-04-21 20:38 ` Primiano Tucci [this message]
2010-04-21 20:58 ` Peter Zijlstra
2010-04-22 13:20 ` Steven Rostedt
2010-04-22 13:50 ` Primiano Tucci
2010-04-22 13:57 ` Peter Zijlstra
2010-04-22 15:40 ` Primiano Tucci
2010-04-22 16:28 ` Peter Zijlstra
2010-04-22 17:48 ` Bjoern Brandenburg
2010-04-22 19:33 ` Primiano Tucci
2010-04-21 12:56 ` Peter Zijlstra
2010-04-27 13:18 ` Thomas Gleixner
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=s2tc5b2c05b1004211338y814bc3b2o547a6eecdf64ca7f@mail.gmail.com \
--to=p.tucci@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®