> >On Fri, Apr 09, 2010 at 10:48:07AM +0800, Ben Kloosterman wrote: >> 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 ? > >Copy on fork is expensive, and if you are going to do fork+exec then >why bother copying at all? vfork+exec works fine for that. > >fork is supposed to be a cheap operation. >
What did Unix do with fork before copy on write or non copy on write architectures ? _______________________________________________ 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
