From: Josef Bacik <jbacik@fusionio.com>
To: Roger Binns <rogerb@rogerbinns.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: document mount options in Documentation/fs/btrfs.txt
Date: Mon, 25 Mar 2013 09:59:30 -0400 [thread overview]
Message-ID: <20130325135930.GF1955@localhost.localdomain> (raw)
In-Reply-To: <kil9uq$210$1@ger.gmane.org>
On Sat, Mar 23, 2013 at 04:22:22PM -0600, Roger Binns wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 23/03/13 10:48, Eric Sandeen wrote:
> > Btrfs is a new copy on write filesystem for Linux aimed at
>
> How much longer does "new" get to be there as the filesystem has been
> going for well over half a decade.
>
> > + autodefrag + Detect small random writes into files and queue them up
> > for the + defrag process. Works best for small files; Not well suited
> > for + large database workloads.
>
> What is "large"? One man's large database is another's trivial database!
> Same applies to "small". Virtual machines are also in the category of
> large files with small random writes.
>
Any write below i_size that is less than 64k.
Josef
next prev parent reply other threads:[~2013-03-25 13:59 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
2013-03-25 15:57 ` David Sterba
2013-03-25 13:59 ` Josef Bacik [this message]
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=20130325135930.GF1955@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rogerb@rogerbinns.com \
/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.