public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Pavel Machek <pavel@suse.cz>, Quinn Harris <quinn@nmt.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File copy system call proposal
Date: Mon, 10 Dec 2001 13:20:07 -0200	[thread overview]
Message-ID: <01121013200704.01165@manta> (raw)
In-Reply-To: <1007782956.355.2.camel@quinn.rcn.nmt.edu> <20011209153522.A138@toy.ucw.cz>
In-Reply-To: <20011209153522.A138@toy.ucw.cz>

On Sunday 09 December 2001 13:35, Pavel Machek wrote:
> > I would like to propose implementing a file copy system call.
> > I expect the initial reaction to such a proposal would be "feature
> > bloat" but I believe some substantial benefits can be seen possibly
> > making it worthwhile, primarily the following:
> >
> > Copy on write:
>
> You want cowlink() syscall, not copy() syscall. If they are on different
> partitions, let userspace do the job.

A filesystem with support of COW files would be *extremely* useful,
especially when writes trigger COW on block level, not file-by-file.

And it will definitely need in-kernel copyfile()/cowlink()/whatever name you 
want...

> > Will many other users benefit from these features?  Will implementing
> > them (especially copy on write) cause an excessive addition to the code
> > of the kernel?

> Hmm, I have almost 20 different copies of kernel on my systems.... Yep it
> would save me a *lot* of space.

Me too
--
vda

  parent reply	other threads:[~2001-12-10 11:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-08  3:42 File copy system call proposal Quinn Harris
2001-12-08  4:00 ` H. Peter Anvin
2001-12-08  6:03   ` Quinn Harris
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  4:25 ` Christian Lavoie
     [not found] ` <1007833194.17577.0.camel@buffy>
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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=01121013200704.01165@manta \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=quinn@nmt.edu \
    /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