Ne sym chul vyprosnata lekciq, no tova koeto cheta tuk ne e pravilno.
To e validno po princip za *nix, no ne i za Linux. Linux kernel-yt
se gordee s dosta byrzo fork-vane na procesi, ponezhe polzva t.nar.
copy-on-write ili copy-on-demand, pri koeto procesyt raboti kato
thread, dokato ne izvyrshi pisane (promqna) nqkyde v pametta. Chak
togava kernel-yt kopira roditelskata pamet. Eto kakvo dava
'man 2 fork':
Under Linux, fork is implemented using copy-on-write pages, so the
only penalty incurred by fork is the time and memory required
to duplicate the parent's page tables, and to create a unique task
structure for the child.
Ako nqkoj iska po-zadylbocheno opisanie na realizaciqta na thread-ove
i procesi, mozhe da pogledne tuk:
http://www.kernel.org/pub/linux/docs/LDP/LDP/lki/lki-2.html#ss2.2
Petko
>Date: Thu, 17 May 2001 16:30:26 +0300
>From: Alexader Shopov <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>SUBJECTReply-To: [EMAIL PROTECTED]
<--- cut --->
>Nishkite v ramkite na edin proces spodeliat obshti resursi - kato pamet,
>failovi deskriptori i t.n.
>S drugi dumi puskaneto na nov proces e po skapa operacia ot edna nishka
>- ne se zadelia pamet i t.n.
<--- cut --->
------------------------------------------------------------
--== Sent via Deja.com ==--
http://www.deja.com/
===========================================================================
A mail-list of Linux Users Group - Bulgaria (bulgarian linuxers)
http://www.linux-bulgaria.org/ Hosted by Internet Group Ltd. - Stara Zagora
