linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	CIFS <linux-cifs@vger.kernel.org>,
	samba-technical <samba-technical@lists.samba.org>
Subject: [LSF/MM TOPIC] Enhancing Copy Tools for Linux FS
Date: Fri, 8 Feb 2019 09:19:33 -0600	[thread overview]
Message-ID: <CAH2r5muqV2KfdtF6HdPm74Txs-pagz=vyMeDxywRssZAnj86+Q@mail.gmail.com> (raw)

Current Linux copy tools have various problems compared to other
platforms - small I/O sizes (and not even configurable for most), lack
of parallel I/O for multi-file copies, inability to reduce metadata
updates by setting file size first, lack of cross mount (to the same
file system) copy optimizations, limited ability to handle the wide
variety of server side copy (and copy offload) mechanisms and various
error handling problems.   And copy tools rely less on the kernel file
system (vs. code in the user space tool) in Linux than would be
expected, in order to determine which optimizations to use.

Would like to discuss some of the observations about copy tools and
how we can move forward on improving the performance of common copy
operations.

-- 
Thanks,

Steve

             reply	other threads:[~2019-02-08 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 15:19 Steve French [this message]
2019-02-08 22:37 ` [LSF/MM TOPIC] Enhancing Copy Tools for Linux FS Andreas Dilger
2019-02-08 23:03   ` Steve French
2019-02-08 23:56     ` Steve French
2019-02-11  8:32       ` Andreas Dilger
2019-02-11 17:43         ` Steve French
2019-02-11 23:22   ` L. A. Walsh

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='CAH2r5muqV2KfdtF6HdPm74Txs-pagz=vyMeDxywRssZAnj86+Q@mail.gmail.com' \
    --to=smfrench@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=samba-technical@lists.samba.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;
as well as URLs for NNTP newsgroup(s).