J
Jiri:
> > To do user-space hard RT, you'd need to make sure the entire linux
> > kernel is up to it; which is why most user-space RT is soft-RT.)
Robert:
> LXRT
...
> it seems to have some kind of a realtime "server" module which is the
> backend for the userspace process, which definitely is hard realtime
...
Sounds very good.
Do you have any more information/experience with this? If we can get userspace hard-RT, that would solve all the problems with partitioning RT and non-RT tasks... (For instance, it'd allow priority inheritance, which would mean that hard-RT, soft-RT and non-RT tasks could all safely run
against the same MAT core. That alone would save a world of hassle.)
Jiri
--
Jiri Baum <[email protected]>
http://www.csse.monash.edu.au/~jiribvisit the MAT LinuxPLC project at http://mat.sf.net
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
> > To do user-space hard RT, you'd need to make sure the entire linux
> > kernel is up to it; which is why most user-space RT is soft-RT.)
Robert:
> LXRT
...
> it seems to have some kind of a realtime "server" module which is the
> backend for the userspace process, which definitely is hard realtime
...
Sounds very good.
Do you have any more information/experience with this? If we can get userspace hard-RT, that would solve all the problems with partitioning RT and non-RT tasks... (For instance, it'd allow priority inheritance, which would mean that hard-RT, soft-RT and non-RT tasks could all safely run
against the same MAT core. That alone would save a world of hassle.)
Jiri
--
Jiri Baum <[email protected]>
http://www.csse.monash.edu.au/~jiribvisit the MAT LinuxPLC project at http://mat.sf.net
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc