Messages in this thread | | | Subject | Re: OT: why no file copy() libc/syscall ?? | From | Daniel Gryniewicz <> | Date | Mon, 10 Nov 2003 23:03:26 -0500 |
| |
On Mon, 2003-11-10 at 22:50, Andreas Dilger wrote: > Having a sys_copy() syscall would be incredibly useful for Lustre > (distributed Linux fs). We could start a copy from one storage node > to another (or more likely many to many for a file striped over many > storage nodes) at num_stripes * uni-directional bandwidth with no > impact to the client node. Instead, we have to copy files at best a > single client's bi-directional network_bandwidth.
Plus a sys_copy() syscall could be used as a generic way for filesystems to set up Copy-on-Write. Right now, you'd need to have userspace call sys-reiser4 or something like that. -- Daniel Gryniewicz <dang@fprintf.net> [unhandled content-type:application/pgp-signature] | |