From: Roman Mamedov <rm@romanrm.net>
To: Brendan Hide <brendan@swiftspirit.co.za>
Cc: Marc MERLIN <marc@merlins.org>, linux-btrfs@vger.kernel.org
Subject: Re: Using mount -o bind vs mount -o subvol=vol
Date: Mon, 5 May 2014 10:36:17 +0600 [thread overview]
Message-ID: <20140505103617.0e66f5a9@natsu> (raw)
In-Reply-To: <53670FEA.8050806@swiftspirit.co.za>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
On Mon, 05 May 2014 06:13:30 +0200
Brendan Hide <brendan@swiftspirit.co.za> wrote:
> >> 1) There will be a *very* small performance penalty (negligible, really)
> > Oh, really, it's slower to mount the device directly? Not that I really
> > care, but that's unexpected.
>
> Um ... the penalty is if you're mounting indirectly. ;)
I feel that's on about the same scale as giving your files shorter filenames,
"so that they open faster". Or have you looked at the actual kernel code with
regard to how it's handled, or maybe even have any benchmarks, other than a
general thought of "it's indirect, so it probably must be slower"?
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-05-05 4:36 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 [this message]
2014-05-05 6:55 ` Brendan Hide
2014-05-06 17:34 ` Duncan
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=20140505103617.0e66f5a9@natsu \
--to=rm@romanrm.net \
--cc=brendan@swiftspirit.co.za \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).