mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Quinn Harris <quinn@nmt.edu>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: File copy system call proposal
Date: 07 Dec 2001 23:03:59 -0700	[thread overview]
Message-ID: <1007791439.355.7.camel@quinn.rcn.nmt.edu> (raw)
In-Reply-To: <9us387$poh$1@cesium.transmeta.com>
In-Reply-To: <1007782956.355.2.camel@quinn.rcn.nmt.edu>  <9us387$poh$1@cesium.transmeta.com>

On Fri, 2001-12-07 at 21:00, H. Peter Anvin wrote:
> Followup to:  <1007782956.355.2.camel@quinn.rcn.nmt.edu>
> By author:    Quinn Harris <quinn@nmt.edu>
> In newsgroup: linux.dev.kernel
> > 
> > All kernel copy:
> > Commands like cp and install open the source and destination file using
> > the open sys call.  The data from the source is copied to the
> > destination by repeatedly calling the read then write sys calls.  This
> > process involves copying the data in the file from kernel memory space
> > to the user memory space and back again.  Note that all this copying is
> > done by the kernel upon calling read or write.  I would expect if this
> > can be moved completely into the kernel no memory copy operations would
> > be performed by the processor by using hardware DMA.
> > 
> 
> mmap(source file);
> write(target file, mmap region);
> 
> 	-hpa

mmap will indeed get a file into user mem space without any memcopy
operation.  But as far as I can tell from examining generic_file_write
(in mm/filemap.c) used by ext2 and I asume many others, a write will
copy the memory even if it was mapped via mmap.  Am I missing
something?  This isn't true if kiobuf is used but as I understand it,
this bypasses the buffer cache.

I would like to see a zero-memcopy file copy.  A file copy that would
read  the file into the buffer cache if its not already there similar to
a normal read then write it back to disk from the cache without
duplicating the pages.  This would probably lead to modifying the buffer
cache to allow multiple buffer_heads to refer to the same data which
might not be worth the overhead.

One might implement such a thing by attempting in the generic_file_read
to determine if the memory range is an actual page or pages that can be
eventually written to the disk without a memcopy.  This could
conceivably make duplications between different files to not take up
duplicate pages.  But what is the chance that there are any sizeable
number of identical pages in the buffer cache do to anything but a file
copy?



  parent reply	other threads:[~2001-12-08  6:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1007833194.17577.0.camel@buffy>
2001-12-08  3:42 ` Quinn Harris
2001-12-08  4:00   ` H. Peter Anvin
2001-12-08  4:25   ` Christian Lavoie
2001-12-08  6:03   ` Quinn Harris [this message]
2001-12-08 13:57     ` Daniel Phillips
2001-12-09  0:19       ` H. Peter Anvin
2001-12-09  4:56       ` Quinn Harris
2001-12-10  5:44       ` Albert D. Cahalan
2001-12-09 20:25         ` Hans Reiser
2001-12-10 15:19         ` Daniel Phillips
2001-12-13 10:01           ` Andreas Dilger
2001-12-13 21:17             ` Pavel Machek
2001-12-19 20:26               ` Daniel Phillips
2001-12-20 10:09                 ` Pavel Machek
2001-12-20 13:38                   ` Svein Ove Aas
2001-12-20 13:53                     ` Jakob Østergaard
2001-12-20 14:00                       ` Jakob Østergaard
2001-12-23  1:19                       ` Pavel Machek
2001-12-20 14:31                     ` David Woodhouse
2001-12-20 15:06                       ` George Greer
2001-12-20 15:07                         ` David Woodhouse
2001-12-20 21:32                 ` Jamie Lokier
2001-12-08 19:23   ` Quinn Harris
2001-12-08 23:11     ` Ton Hospel
2001-12-09 15:35   ` Pavel Machek
2001-12-10 11:50     ` Albert D. Cahalan
2001-12-10  2:49       ` Hans Reiser
2001-12-10 12:13       ` Pavel Machek
2001-12-10 15:20     ` vda
2001-12-10 18:44 Petr Vandrovec

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=1007791439.355.7.camel@quinn.rcn.nmt.edu \
    --to=quinn@nmt.edu \
    --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

all inboxes | Powered by JetHome®