From: Vojtech Pavlik <vojtech@suse.com>
To: Simon Herter <sim.herter@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Btrfs on bcache device: mount options?
Date: Thu, 15 Oct 2015 16:29:45 +0200 [thread overview]
Message-ID: <20151015142945.GA10162@suse.com> (raw)
In-Reply-To: <87mvvk4718.fsf@gmx.de>
On Thu, Oct 15, 2015 at 03:04:35PM +0200, Simon Herter wrote:
> I'm using btrfs on a bcache device and I'm a bit confused about mount
> options. For example, bcache may (if I understood correctly) bypass the
> cache completely for sequential access. So should I use "ssd" mount
> option or not? Are there any general recommendations?
No, you should not. It modifies the data layout behavior to ignore seek
times. These may be present when reading from the backing media.
You likely want to enable compression and autodefragmentation, too.
--
Vojtech Pavlik
Director SUSE Labs
next prev parent reply other threads:[~2015-10-15 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 13:04 Btrfs on bcache device: mount options? Simon Herter
2015-10-15 14:29 ` Vojtech Pavlik [this message]
2015-10-15 21:27 ` Simon Herter
2015-11-24 7:30 ` Kai Krakow
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=20151015142945.GA10162@suse.com \
--to=vojtech@suse.com \
--cc=linux-bcache@vger.kernel.org \
--cc=sim.herter@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox