From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Using mount -o bind vs mount -o subvol=vol
Date: Tue, 6 May 2014 17:34:11 +0000 (UTC) [thread overview]
Message-ID: <pan$db71b$28ae8fc2$4747ca76$c08f8373@cox.net> (raw)
In-Reply-To: 536735FB.6020205@swiftspirit.co.za
Brendan Hide posted on Mon, 05 May 2014 08:55:55 +0200 as excerpted:
> You are 100% right, though. The scale is very small. By negligible, the
> "penalty" is at most a few CPU cycles. When compared to the wait time on
> a spindle, it really doesn't matter much.
The analogy I've used before is that of taking a trip (which the data
effectively is, between the device and the CPU).
We've booked a 10-day cruise and are now debating what we plan on taking
to and from the boarding dock. Will taking the local bus with a couple
of transfers, or a taxi that will take us there in one trip but there's
road construction and thus a detour, or a helicopter to fly directly,
get us back from the cruise faster?
Obviously, taking the helicopter (at least for the return leg) will get
us back a bit faster, but we're talking perhaps a couple hours difference
at the end of a 10 day cruise!
=:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-05-06 19:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 0:47 Using mount -o bind vs mount -o subvol=vol Marc MERLIN
2014-05-04 7:07 ` Brendan Hide
2014-05-05 0:56 ` Marc MERLIN
2014-05-05 4:13 ` Brendan Hide
2014-05-05 4:36 ` Roman Mamedov
2014-05-05 6:55 ` Brendan Hide
2014-05-06 17:34 ` Duncan [this message]
2014-05-05 5:22 ` Marc MERLIN
2014-05-05 2:12 ` Duncan
2014-05-07 10:55 ` Marc MERLIN
2014-05-07 12:31 ` Duncan
2014-05-05 13:54 ` Chris Mason
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='pan$db71b$28ae8fc2$4747ca76$c08f8373@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).