> >You may be able to learn something about performance possibilities by >looking >at the ARM example here. > > http://opensrc.sec.samsung.com/document.html > >uClinux+mono pain will probably depend on mono more than anything. > > * how much does it fork() (and is it vfork safe) > * reliance on loadable modules and shared libraries. > * stack usage (to some extent) >
That's what I expect, been working on Arm ( which mono supports , they run on Android). Stack usage in .NET is normally fixed and hard code in the apps meta data and mono supports shared and non shared libs. Fork is the big question mark , speaking of which why didn't uclib support fork and instead of copy on write ( like early unix fork) just change fork to copy on fork or are the API differences to big ? Regards, Ben _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
