All of lore.kernel.org
 help / color / mirror / Atom feed
From: sidc7 <siddhartha.chhabra@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: COW optimization on exec
Date: Sat, 14 Mar 2009 23:20:43 -0700 (PDT)	[thread overview]
Message-ID: <22520422.post@talk.nabble.com> (raw)
In-Reply-To: <200903151458.25363.nickpiggin@yahoo.com.au>


> exec throws out all those pages, so go away without ever having been
> copied. However it still costs memory CPU time TLB flushes etc in order
> to set up the COW optimisation in the first place, so if you are doing
> fork/exec, then I think vfork is the better option.


Thanks once again, if I do something like creating an array spanning over
multiple pages, and then do a fork and in the child or the parent, write to
the array elements, this should result in an actual cow, where the OS will
actually do a copy of the pages as well in addition to the overhead required
for setting up COW in the first place?

Thanks


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



-- 
View this message in context: http://www.nabble.com/COW-optimization-on-exec-tp22519639p22520422.html
Sent from the linux-kernel mailing list archive at Nabble.com.


      reply	other threads:[~2009-03-15  6:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15  2:57 COW optimization on exec sidc7
2009-03-15  3:41 ` Johannes Weiner
2009-03-15  4:20   ` sidc7
2009-03-15  3:58 ` Nick Piggin
2009-03-15  6:20   ` sidc7 [this message]

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=22520422.post@talk.nabble.com \
    --to=siddhartha.chhabra@gmail.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.