All of lore.kernel.org
 help / color / mirror / Atom feed
From: sidc7 <siddhartha.chhabra@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Copy-on-write
Date: Thu, 26 Mar 2009 23:43:03 -0700 (PDT)	[thread overview]
Message-ID: <22736728.post@talk.nabble.com> (raw)
In-Reply-To: <3e8340490903262235g6174c6b4t4bfd76311be91eeb@mail.gmail.com>


> If the source and destination pages are not in high memory (exactly
> where this boundary is depends on your architecture) they do not need
> to be mapped before copying. See cow_user_page in mm/memory.c,
> copy_user_highpage in include/linux/highmem.h and kmap_atomic in
> arch/x86/mm/highmem_32.c (as well as implementations for other
> architectures)

> Note that on 64-bit platforms, generally there will be no high memory,
> and so remappings will never be needed to carry out a COW.

Thanks for the quick reply. In general if the kernel wishes to read any
arbitrary page mapped to an application's address space, will the kernel
cause a page fault on that page, since the page is currently not in its
address space and the kernel is wishing to read from this page?

Thanks

-- 
View this message in context: http://www.nabble.com/Copy-on-write-tp22736146p22736728.html
Sent from the linux-kernel mailing list archive at Nabble.com.


  reply	other threads:[~2009-03-27  6:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27  5:15 Copy-on-write sidc7
2009-03-27  5:35 ` Copy-on-write Bryan Donlan
2009-03-27  6:43   ` sidc7 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-06  5:49 Copy-on-Write Rick Brown
2008-02-06 11:00 ` Copy-on-Write Manish Katiyar
2008-02-06 12:33   ` Copy-on-Write Rajat Jain
2008-02-06 12:41     ` Copy-on-Write Manish Katiyar
2008-02-06 13:17     ` Copy-on-Write Daniel Cheng
2008-02-07 15:30 ` Copy-on-Write Mulyadi Santosa
2008-02-07 23:46   ` Copy-on-Write Brandon Philips
2008-02-08  2:11     ` Copy-on-Write Renê
     [not found]     ` <5f9618380802071809v24f2be47xc9aea8664a8f8488@mail.gmail.com>
2008-02-13  5:44       ` Copy-on-Write Brandon Philips

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=22736728.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.