Re: [Xenomai-help] POSIX Skin: Changing scheduling parameters of threads in other processes

[Jan Kiszka <jan.kiszka@domain.hid>]

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

Hi Torsten,

<snippin a lot, sorry>

Torsten Kröger wrote:
>> Jan Kiszka wrote:
>> If you are seriously interested in prio-inheritance for the native
>> message passing API, the best you can do is to work actively on a patch
>> proposal. This would
>>
>> - demonstrate how unintrusive this addition could be (preferably, PI
>>   will be optional and use existing low-level services), while being
>>   so useful for certain scenarios
>>
>> - accelerate the testing cycle (_you_ have the scenario at hand)
>>
>> - raise the chances that Xenomai gains this feature soon (core
>>   developers are generally busy with many things)
>>
>> Posting patches early will allow you gain concrete feedback on the
>> design. And we will not sit there and watch you pulling hairs while
>> you're stuck. But hacking some Xenomai skin is also no black magic,
>> given the well defined nucleus API. Give it a try!
> 
> I am seriously interested in priority inheritance for the message
> passing API, but I don't consider myself as an expert in this field and
> nor as an operating system developer. My employer/my client does not
> give me time for such kind of system engineering, hence I will remain as
> a user - all I can do is to tell about my desires and experiences.

As I said, it doesn't take experts here, just someone to start and
collect the pieces (which might include asking for expert knowledge here
and there).

And someone being able to write such long and detailed essays - for me
even too long to read completely yet - should as well be able to play a
bit with code. Or motivate some talented student of yours (I know they
can be rare). ;)

> 
> Ok, now I'm coming to the end. I hope this posting was a bit interesting
> for any reader and that someone goes for further words on this...
> 
> ...any comment and further discussion is highly appreciated again! :-)
> 

Better let some code speak now...

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]