From: Olivier Galibert <galibert@pobox.com>
To: "Hack inc." <linux-kernel@vger.kernel.org>
Subject: What is the most efficient way to copy a bunch of files nowadays?
Date: Tue, 11 Apr 2006 13:11:37 +0200 [thread overview]
Message-ID: <20060411111137.GA13961@dspnet.fr.eu.org> (raw)
After having read-only mucked with the headers of a bunch of files[1]
I've selected a subset of 2500 or so with sizes going from 2K to 85M
which I want to copy to another directory in the same local
filesystem. What is the "best" (CPU usage, fragmentation, wall clock
time, system responsiveness during and after the copy) way to copy
these files? read+write, mmap+write, read+mmap, mmap+mmap+memcpy,
something else? That's with recent kernels, of course.
OG.
[1] Say rpms from a random distribution and its updates for instance
next reply other threads:[~2006-04-11 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 11:11 Olivier Galibert [this message]
2006-04-13 14:08 ` Jan Engelhardt
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=20060411111137.GA13961@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--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®