On Friday 09 April 2010 00:36:38 David McCullough wrote: > Jivin Ben Kloosterman lays it down ... > > 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 ? > > You can't just copy on fork (unless it's a truly big copyin/out on every > context switch). Pretty sure this has been beaten to death in the > uClinux-dev archives somewhere ;-)
isnt that exactly what minix does though ? crap performance sure, but it lets things get a basic port going easier ... the kernel would have to do the copy. no way it could be handled in userspace (i.e. uClibc). -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ 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
