For my case an expensive fork is ok , still a lot of forks are done on apps load and compared to a disk load its cheap.
Anyway I'm not going to implement fork , if I need it in Mono and it cant be a vfork I will simply copy the data via pointers. Since the Mono lib is part of my TCB or if you prefer "kernel" . >-----Original Message----- >From: Mike Frysinger [mailto:vap...@gentoo.org] >Sent: Tuesday, April 13, 2010 10:42 AM >To: uclinux-dev@uclinux.org >Cc: Ben Kloosterman >Subject: Re: [uClinux-dev] Creating a new arch > >On Monday 12 April 2010 22:30:01 Ben Kloosterman wrote: >>>On Fri, Apr 09, 2010 at 10:48:07AM +0800, Ben Kloosterman wrote: >>>>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 ? > >it's why vfork was introduced -- forks used to be expensive. it isnt >really an architecture issue so much as researching new mmu tricks. >-mike _______________________________________________ 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
