From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philippe Gerum In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Wed, 21 Sep 2011 14:35:53 +0200 Message-ID: <1316608553.2171.37.camel@domain.hid> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] pSOS skin in xenomai-solo List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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.