From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [Xenomai-commits] r4210 - in /trunk: ChangeLog src/skins/native/task.c
Date: Sun, 05 Oct 2008 14:45:56 +0200 [thread overview]
Message-ID: <48E8B704.8030403@domain.hid> (raw)
In-Reply-To: <48E8B29D.5040705@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Author: gch
>>> Date: Sat Oct 4 23:11:09 2008
>>> New Revision: 4210
>>>
>>> URL: http://svn.gna.org/viewcvs/xenomai?rev=4210&view=rev
>>> Log:
>>> Call __real_pthread_setschedparam in order to inform the libc of the scheduling parameters change.
>> Well, I dropped this idea after realizing that it will kick us out of
>> primary mode in all cases. This change is an improvement (/wrt Linux
>> scheduling accuracy) for borderline threads, but it will cause
>> regressions for primary-only threads. I have no idea right now how to
>> make both happy, at least without explicit pthread_setschedparam
>> invocations by the user application.
>
> Well, we discussed this on the xenomai mailing list, you did not answer,
> so we assumed you agreed.
I do not find any hint in that thread that we agreed on changing the
implementation. Rather I took back my suggestion to do it like #4210.
And you proposed to install some signal for syncing glibc /wrt
priorities. When changing something, then I would say explore this path
first.
Turning rt_task_set_priority into secondary-mode service is a critical
change, and only the last resort if we consider its current
implementation as totally broken - I wouldn't say it is like that. It's
partially and, unfortunately, silently broken, ie. lacking documentation
about its limitations. But its perfectly OK for primary-only users.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2008-10-05 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1KmEP8-0003wS-5y@domain.hid>
2008-10-05 12:14 ` [Xenomai-core] [Xenomai-commits] r4210 - in /trunk: ChangeLog src/skins/native/task.c Jan Kiszka
2008-10-05 12:27 ` Gilles Chanteperdrix
2008-10-05 12:41 ` Gilles Chanteperdrix
2008-10-05 12:45 ` Jan Kiszka [this message]
2008-10-05 12:54 ` Gilles Chanteperdrix
2008-10-05 13:21 ` Gilles Chanteperdrix
2008-10-05 13:31 ` Jan Kiszka
2008-10-05 13:34 ` Gilles Chanteperdrix
2008-10-05 13:41 ` Jan Kiszka
2008-10-05 15:47 ` Gilles Chanteperdrix
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=48E8B704.8030403@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--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.