On 02/06/2011 11:30 PM, Ramesh Random wrote: > > hi, > i have gone through posts regarding porting corosync. things to > keep in mind > IPC mmap,semaphore.... > UDP multicasting.......... > POSIX compliance...pthread_xxxxx > > has anybody thought of porting corosync to VxWorks? what would be > the effort & feasibility? any conclusions made as of now... >
Has not been considered. Corosync uses a process model, and I know some versions of vxworks (atleast the old ones) do not have a process model, but instead share their entire address space among modules. I believe they added a process model in vxworks 6.0 but its been awhile since I've worked with embedded products. The things that may trip you up are: requirement for posix threads requirement for posix shared memory requirement for posix semaphores There are a few other os-specific components, such as the ip binding code that need porting to new platforms. If you have a porting patch, I'll consider adding if it is not drastic :) Regards -steve > thanks for help in advance > Ramesh > > > > _______________________________________________ > Openais mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/openais _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
