All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Fokkens <rolf-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
To: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache & btrfs: "Btrfs detected SSD devices, enabling SSD mode"
Date: Fri, 20 Sep 2013 21:25:29 +0200	[thread overview]
Message-ID: <523CA129.1000508@rolffokkens.nl> (raw)
In-Reply-To: <523C76F4.3070809-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 09/20/2013 06:25 PM, Gabriel de Perthuis wrote:
> SSD […] optimizations (e.g. avoiding unnecessary seek optimizations,
> sending writes in clusters, even if they are from unrelated files. This
> results in larger write operations and faster write throughput)
>
> The optimisations should be beneficial iff bcache is used in writeback
> mode.  ssd_spread and discard are enabled separately; I'm not sure what
> ssd_spread (from the wiki: more strict about finding a large unused
> region of the disk for new allocations) would do for bcache.
 From observing iostat I have the impression that bcache sometimes 
bypasses the cache, probably related to sequential_cutoff. Seems like 
btrfs tries to cluster writes (because an SSD is detected) and next 
bcache bypasses the SSD (because the writes are clustered). Doesn't seem 
the right kind of cooperation :-)

(Assuming of course that clustered writes are based on sequential writes)

      parent reply	other threads:[~2013-09-20 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 16:03 bcache & btrfs: "Btrfs detected SSD devices, enabling SSD mode" Rolf Fokkens
     [not found] ` <523C71C4.9030606-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-09-20 16:25   ` Gabriel de Perthuis
     [not found]     ` <523C76F4.3070809-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-20 19:25       ` Rolf Fokkens [this message]

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=523CA129.1000508@rolffokkens.nl \
    --to=rolf-6w2rdlbueqtpmfipwq+h6g@public.gmane.org \
    --cc=g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.