From: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
To: Stefan Priebe <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
Cc: Jack Wang
<jack.wang.usish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: can't get bache's sequential_cutoff to work
Date: Wed, 24 Jul 2013 17:14:31 -0700 [thread overview]
Message-ID: <20130725001431.GA12364@kmo-pixel> (raw)
In-Reply-To: <51EEE9D9.7090207-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
On Tue, Jul 23, 2013 at 10:38:49PM +0200, Stefan Priebe wrote:
> Mhm works directly on block device but not with XFS on top.
That's odd...
Do you suppose you could look at what blktrace says is going down? If
you could compare what blktrace says is going to the bcache device with
and without XFS, hopefully that'll show what's going wrong...
Only thing I can think of that would cause it is for some reason XFS is
sending bios down in the wrong order... which normally wouldn't be _too_
painful since both the elevator and the disk's cache will reorder the
IOs, so I can see how that would slip by.
next prev parent reply other threads:[~2013-07-25 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 14:16 can't get bache's sequential_cutoff to work Stefan Priebe - Profihost AG
[not found] ` <CA+res+Ti1-tGANkb9wRAgF4sAcUqEv9RfGjDvbdX3bbxS=XK8g@mail.gmail.com>
[not found] ` <CA+res+Ti1-tGANkb9wRAgF4sAcUqEv9RfGjDvbdX3bbxS=XK8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-23 19:41 ` Stefan Priebe
[not found] ` <51EEDC73.5020101-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-23 20:31 ` Stefan Priebe
[not found] ` <51EEE805.7090200-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-23 20:38 ` Stefan Priebe
[not found] ` <51EEE9D9.7090207-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-25 0:14 ` Kent Overstreet [this message]
2013-07-25 7:17 ` Stefan Priebe - Profihost AG
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=20130725001431.GA12364@kmo-pixel \
--to=kmo-pezghdh756f8ursed/g0lq@public.gmane.org \
--cc=jack.wang.usish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox