From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: document mount options in Documentation/fs/btrfs.txt
Date: Sat, 23 Mar 2013 18:11:26 -0700 [thread overview]
Message-ID: <kiljrq$efp$1@ger.gmane.org> (raw)
In-Reply-To: <514E2F69.1030204@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23/03/13 15:40, Eric Sandeen wrote:
> I imagine it depends on the details of the workload & storage as well.
If the people who write btrfs can't come up with some measures to deem
appropriateness, then how can the administrators who have even less
information :-)
I suspect file size has nothing to do with it, and it is entirely about
the volume of random writes. (But as a correlator smaller files are
unlikely to get many random writes because they contain less useful
information than larger files.)
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAlFOUr0ACgkQmOOfHg372QSIsgCg3D1k0dL/2bMQpzHRDdlMkUo2
TT8AoI11eLAdAv6iQPweHaeVUiJNSRf6
=OVVq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-03-24 1:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 17:48 [PATCH] btrfs: document mount options in Documentation/fs/btrfs.txt Eric Sandeen
2013-03-23 18:33 ` Roman Mamedov
2013-03-23 18:45 ` Eric Sandeen
2013-03-26 13:23 ` Karel Zak
2013-03-23 20:35 ` Ilya Dryomov
2013-03-23 22:22 ` Roger Binns
2013-03-23 22:40 ` Eric Sandeen
2013-03-24 1:11 ` Roger Binns [this message]
2013-03-25 15:57 ` David Sterba
2013-03-25 13:59 ` Josef Bacik
2013-03-26 19:36 ` [PATCH V2] " Eric Sandeen
2013-03-29 16:48 ` David Sterba
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='kiljrq$efp$1@ger.gmane.org' \
--to=rogerb@rogerbinns.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.