From: Philippe Gerum <rpm@xenomai.org>
To: Ronny Meeus <ronny.meeus@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] pSOS skin in xenomai-solo
Date: Wed, 21 Sep 2011 21:09:44 +0200 [thread overview]
Message-ID: <1316632184.2171.56.camel@domain.hid> (raw)
In-Reply-To: <CAMJ=MEfqBJAL9_VPpqFG1kZ8GEfy-Zu0A51M8DC-n-p_-025LA@mail.gmail.com>
On Wed, 2011-09-21 at 18:27 +0200, Ronny Meeus wrote:
> On Wed, Sep 21, 2011 at 2:41 PM, Philippe Gerum <rpm@xenomai.org> wrote:
> > On Wed, 2011-09-21 at 14:35 +0200, Philippe Gerum wrote:
> >> On Tue, 2011-09-20 at 13:10 +0200, Ronny Meeus wrote:
> >> > Hello
> >> >
> >> > We have ported a large pSOS based application to an Embedded Linux
> >> > environment using Xenomai.
> >> > A more or less stable version is running at this moment.
> >> >
> >> > The application is not a real-time application at all, we basically
> >> > selected Xenomai for its pSOS interface.
> >> > Since our application uses also native Linux calls (for example socket
> >> > communication), we start to see some strange behavior.
> >> > Example: lower priority tasks are running in the xenomai domain while
> >> > higher priority tasks, sending data on a socket for example, have to
> >> > wait until all processing in the Xenomai domain is completed.
> >> >
> >> > My feeling is that the Solo project would be better for us.
> >> > As far as I understand, this is just a thin layer on top of Linux,
> >> > purely running in user space that also offers the pSOS interface.
> >> > Is my understanding correct?
> >>
> >> Yes.
> >>
> >> >
> >> > If it is, I would think that the socket issue described above will be
> >> > automatically solved since there will only be 1 scheduler (the Linux
> >> > one) and it will respect the thread/task priorities.
> >> >
> >>
> >> True, but in purely Linux native mode, note that your app would be
> >> restricted to use VxWorks priorities between 0 and 98 inclusive.
>
> pSOS you mean ...
Yes, same issue.
> I can live with that since we convert the priority.
>
> > 0 and 97 inclusive, the two highest priority levels are reserved for
> > internal use.
> >
> >>
> >> > What is the status of this project?
> >> >
> >> > Regards,
> >> > Ronny
> >> >
> >> > _______________________________________________
> >> > Xenomai-help mailing list
> >> > Xenomai-help@domain.hid
> >> > https://mail.gna.org/listinfo/xenomai-help
> >>
> >
> > --
> > Philippe.
> >
> >
> >
>
> I was playing with the xenomai solo in today and I found some issue.
> It is also present in the -force repository.
> If you pass in pSOS a 0 as name to the t_ident (lib/psos/task.c)
> service call, it will return the taskId of the current running task.
> In the current implementation this call crashes with a segmentation fault.
>
This should be fixed in the repo now.
> Ronny
--
Philippe.
prev parent reply other threads:[~2011-09-21 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 11:10 [Xenomai-help] pSOS skin in xenomai-solo Ronny Meeus
2011-09-21 12:32 ` Philippe Gerum
2011-09-21 12:35 ` Philippe Gerum
2011-09-21 12:41 ` Philippe Gerum
2011-09-21 16:27 ` Ronny Meeus
2011-09-21 19:09 ` Philippe Gerum [this message]
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=1316632184.2171.56.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=ronny.meeus@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.