From: Jagadeesh Bhaskar P <jbhaskar@hclinsys.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: on the concept of COW
Date: Sat, 20 Nov 2004 16:08:21 +0530 [thread overview]
Message-ID: <1100947100.4038.41.camel@myLinux> (raw)
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
shouldn't the operations/updations by one process be visible to the
other which inherited the copy of the same VM?
How can this work? Can someone please help me on this regard?
--
With regards,
Jagadeesh Bhaskar P
R&D Engineer
HCL Infosystems Ltd
Pondicherry
INDIA
next reply other threads:[~2004-11-20 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 10:38 Jagadeesh Bhaskar P [this message]
2004-11-20 11:39 ` on the concept of COW Antonio Vargas
2004-11-22 7:35 ` Helge Hafting
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=1100947100.4038.41.camel@myLinux \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.