From: Jan Kiszka <kiszka@domain.hid>
To: Herman Bruyninckx <herman.bruyninckx@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Future of fusion
Date: Thu, 13 Oct 2005 15:57:34 +0200 [thread overview]
Message-ID: <434E67CE.60507@domain.hid> (raw)
In-Reply-To: <Pine.LNX.4.64.0510131131490.5110@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
Herman Bruyninckx wrote:
> On Thu, 13 Oct 2005, Philippe Gerum wrote:
>
>> Herman Bruyninckx wrote:
>>
>>> On Thu, 13 Oct 2005, Gilles Chanteperdrix wrote:
>>>
>>>> Herman Bruyninckx wrote:
>>>> > On Thu, 13 Oct 2005, Philippe Gerum wrote:
>>>> >
>>>> > [...]
>>>> > > - New skins: Any new colors for the "chameleon"?
>>>> > "Perfect POSIX" is, to me, more important than new skins.
>>>> "Perfect" means,
>>>> > among other things, that the interference problem with the Posix
>>>> thread
>>>> > library (libraries) under Linux is solved.
>>>>
>>>> What is wrong with the current implementation ?
>>>
>>>
>>> [...]
>>>
>>>> But I assumed the
>>>> interference with the posix thread library was solved. Could you
>>>> elaborate a bit more on the issues you observed ?
>>>
>>>
>>>
>>> Well, if this problem is solved, I'm very happy :-) And maybe I look
>>> at the
>>> wrong places, but where do I find a succint explanation of the solution?
>>>
>>
>> Well, what's your question first? :o>
>>
> Sorry if that was not clear.
>
> The question is: how is the following problem solved? Where the problem is
> as follows: using Posix threads in realtime requires another library than
> the standard NPTL library that Linux uses (at least, I think you require
> another library), but how do you make sure to link to the correct library?
> Or is NPTL realtime safe?
>
Nope, that's why there is RT-NPTL. And that library is still in flux,
especially now with the ongoing work on PREEMPT_RT. Let's wait for the
result and see if it is feasible to reuse this userspace infrastructure.
For now, I'm convinced that it is much more comfortable for the user to
obtain kernel extension and userspace library from one hand with a clear
and consistent versioning.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2005-10-13 13:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 7:55 [Xenomai-core] Future of fusion Marco Cavallini
2005-10-13 8:15 ` Jan Kiszka
2005-10-13 8:24 ` Philippe Gerum
2005-10-13 8:37 ` Herman Bruyninckx
2005-10-13 8:50 ` Gilles Chanteperdrix
2005-10-13 8:54 ` Herman Bruyninckx
2005-10-13 9:12 ` Philippe Gerum
2005-10-13 9:34 ` Herman Bruyninckx
2005-10-13 13:57 ` Jan Kiszka [this message]
2005-10-13 19:57 ` Gilles Chanteperdrix
2005-10-13 9:46 ` Jan Kiszka
2005-10-13 10:46 ` Paul
2005-10-13 13:33 ` Philippe Gerum
2005-10-13 19:47 ` Wolfgang Grandegger
2005-10-13 20:28 ` Gilles Chanteperdrix
2005-10-14 3:42 ` Romain Lenglet
2005-10-16 7:47 ` [Xenomai-core] Packaging issues and licensing issues Romain Lenglet
2005-10-16 7:50 ` Gilles Chanteperdrix
2005-10-16 14:00 ` gna-dev
2005-10-16 14:18 ` Romain Lenglet
2005-10-17 18:54 ` 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=434E67CE.60507@domain.hid \
--to=kiszka@domain.hid \
--cc=herman.bruyninckx@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.