From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [RFC] shadow threads with prio 0 / SCHED_NORMAL
Date: Fri, 21 Apr 2006 18:41:33 +0200 [thread overview]
Message-ID: <44490B3D.2060600@domain.hid> (raw)
In-Reply-To: <17481.417.382690.108221@domain.hid>
Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > > What about keeping SCHED_RR as the default scheduling policy and
> > > requiring users to manually select SCHED_NORMAL in thread creation
> > > attributes in order to create hybrid threads with pthread_create ?
> > >
> >
> > No objection a priori, but what would this buy us?
>
> As a user, I would expect pthread_create and pthread_setschedparam to
> allow the same scheduling policies and priorities.
>
Is your concern about having the POSIX skin in kernel space currently
assuming that SCHED_OTHER == SCHED_RR, which would be different than
Linux's perception in that case?
However, I really think that we should not rely on implicit rules when
we could avoid it (e.g. SCHED_RR as default), especially when those
rules are going to be most often overlooked (people are rather used to
default to SCHED_NORMAL/OTHER in the Linux sense).
What I suggested was to let people create normal threads using
pthread_create (likely conforming to the SCHED_OTHER policy), then use
the redirected pthread_setschedparam syscall (i.e. always applied to the
current thread) to promote them as Xenomai shadows, but leave them in
their original scheduling class. The same goes for rt_task_shadow. This
would be explicit actions that would not leave much room for "surprises".
--
Philippe.
next prev parent reply other threads:[~2006-04-21 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 22:01 [Xenomai-core] [RFC] shadow threads with prio 0 / SCHED_NORMAL Jan Kiszka
2006-04-20 12:55 ` Philippe Gerum
2006-04-21 10:46 ` Philippe Gerum
2006-04-21 15:21 ` Gilles Chanteperdrix
2006-04-21 15:47 ` Philippe Gerum
2006-04-21 16:00 ` Gilles Chanteperdrix
2006-04-21 16:41 ` Philippe Gerum [this message]
2006-04-21 17:40 ` Gilles Chanteperdrix
2006-04-21 17:50 ` Philippe Gerum
2006-04-21 18:18 ` Jan Kiszka
2006-04-21 21:40 ` Philippe Gerum
2006-04-21 16:03 ` Jan Kiszka
2006-06-04 17:58 ` Philippe Gerum
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=44490B3D.2060600@domain.hid \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.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 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.