DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=c/kq7znEXe5pIuYGa7XFctWFhZCDdmFQOHpHfGnYS7vIqz9nMPDbBiCsqAMTPVttoE
         iLiHpDnjIwFWjH+J/UDpaan654Vrq2hsVhEy5GDLnfZ1Y/xAfHsqftEogyC6Afx2qfhA
         T2YQE9G93eZdnkeJB4Z1C3rliJdQZTvuPqpQI=
MIME-Version: 1.0
In-Reply-To: <22736146.post@talk.nabble.com>
References: <22736146.post@talk.nabble.com>
Date: Fri, 27 Mar 2009 01:35:18 -0400
Message-ID: <3e8340490903262235g6174c6b4t4bfd76311be91eeb@mail.gmail.com>
Subject: Re: Copy-on-write
From: Bryan Donlan <bdonlan@gmail.com>
To: sidc7 <siddhartha.chhabra@gmail.com>
Cc: linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1019
Lines: 20

On Fri, Mar 27, 2009 at 1:15 AM, sidc7 <siddhartha.chhabra@gmail.com> wrote:
>
> When the kernel does a COW, say from a "src" to a "dest" page, does it need
> to map the "src" and "dest" page to its address space or the kernel can
> directly initiate the read from "src" and write to "dest" page ?

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.
--
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/