From: Helge Hafting <helge.hafting@hist.no>
To: Jagadeesh Bhaskar P <jbhaskar@hclinsys.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: on the concept of COW
Date: Mon, 22 Nov 2004 08:35:22 +0100 [thread overview]
Message-ID: <41A196BA.700@hist.no> (raw)
In-Reply-To: <1100947100.4038.41.camel@myLinux>
Jagadeesh Bhaskar P wrote:
>Hi,
>
> When a process forks, every resource of the parent, including the
>virtual memory is copied to the child process. The copying of VM uses
>copy-on-write(COW). I know that COW comes when a write request comes,
>and then the copy is made. Now my query follows:
>
>How will the copy be distributed. Whether giving the child process a new
>copy of VM be permanent or whether they will be merged anywhere? And
>
>
Merging can only happen if the two pages becomes equal
again. That is extremely unlikely, and checking for this
would cost a lot more than the memory saved.
>shouldn't the operations/updations by one process be visible to the
>other which inherited the copy of the same VM?
>
>
Of course not - the whole reason for copying is so such
modifications won't be visible for the other process.
There may be special cases (shared mapping) where one
process is supposed to see updates done by another - but
then no COW is performed because there is no need.
Helge Hafting
next prev parent reply other threads:[~2004-11-22 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 10:38 on the concept of COW Jagadeesh Bhaskar P
2004-11-20 11:39 ` Antonio Vargas
2004-11-22 7:35 ` Helge Hafting [this message]
2004-11-22 20:44 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41A196BA.700@hist.no \
--to=helge.hafting@hist.no \
--cc=jbhaskar@hclinsys.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox