>-----Original Message----- >From: uclinux-dev-boun...@uclinux.org [mailto:uclinux-dev- >boun...@uclinux.org] On Behalf Of Mike Frysinger >Sent: Friday, April 09, 2010 12:44 PM >To: uclinux-dev@uclinux.org >Subject: Re: [uClinux-dev] Creating a new arch > >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).
Oops didn't mean to drag up old discussions. Why cant it be done in userspace ? There is no MMU and I hence on most (all ?) arch no protection you just need to trust the lib to do the job properly. _______________________________________________ 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
