* [Xenomai-help] pSOS skin in xenomai-solo @ 2011-09-20 11:10 Ronny Meeus 2011-09-21 12:32 ` Philippe Gerum 2011-09-21 12:35 ` Philippe Gerum 0 siblings, 2 replies; 6+ messages in thread From: Ronny Meeus @ 2011-09-20 11:10 UTC (permalink / raw) To: xenomai-help 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? 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. What is the status of this project? Regards, Ronny ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] pSOS skin in xenomai-solo 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 1 sibling, 0 replies; 6+ messages in thread From: Philippe Gerum @ 2011-09-21 12:32 UTC (permalink / raw) To: Ronny Meeus; +Cc: xenomai-help 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? > > 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. > > What is the status of this project? > https://mail.gna.org/public/xenomai-help/2011-06/msg00229.html Since this mail was posted, there has been a significant work on the -forge tree, you may want to have a look at the README git://git.xenomai.org/xenomai-forge.git This is NOT production grade yet, current lack of documentation is blatant as well, but AFAICT, this meets my expectations design-wise, and runtime-wise. Lot of work ahead though. You may want to try running the psos testsuite from lib/psos/testsuite, over the so-called "Mercury" core. You could do this as follows: $ .../xenomai-forge/configure --with-core=mercury --prefix=/ $ make install DESTDIR=/foo $ cd .../xenomai-forge/lib/psos/testsuite $ make DESTDIR=/foo test (*) (*) will require the current account to be sudoer > Regards, > Ronny > > _______________________________________________ > Xenomai-help mailing list > Xenomai-help@domain.hid > https://mail.gna.org/listinfo/xenomai-help -- Philippe. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] pSOS skin in xenomai-solo 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 1 sibling, 1 reply; 6+ messages in thread From: Philippe Gerum @ 2011-09-21 12:35 UTC (permalink / raw) To: Ronny Meeus; +Cc: xenomai-help 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. > 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] pSOS skin in xenomai-solo 2011-09-21 12:35 ` Philippe Gerum @ 2011-09-21 12:41 ` Philippe Gerum 2011-09-21 16:27 ` Ronny Meeus 0 siblings, 1 reply; 6+ messages in thread From: Philippe Gerum @ 2011-09-21 12:41 UTC (permalink / raw) To: Ronny Meeus; +Cc: xenomai-help 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. 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] pSOS skin in xenomai-solo 2011-09-21 12:41 ` Philippe Gerum @ 2011-09-21 16:27 ` Ronny Meeus 2011-09-21 19:09 ` Philippe Gerum 0 siblings, 1 reply; 6+ messages in thread From: Ronny Meeus @ 2011-09-21 16:27 UTC (permalink / raw) To: Philippe Gerum; +Cc: xenomai-help 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 ... 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. Ronny ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] pSOS skin in xenomai-solo 2011-09-21 16:27 ` Ronny Meeus @ 2011-09-21 19:09 ` Philippe Gerum 0 siblings, 0 replies; 6+ messages in thread From: Philippe Gerum @ 2011-09-21 19:09 UTC (permalink / raw) To: Ronny Meeus; +Cc: xenomai-help 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-09-21 19:09 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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.