public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
To: Jack Wang <jack.wang.usish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
Subject: Re: can't get bache's sequential_cutoff to work
Date: Tue, 23 Jul 2013 21:41:39 +0200	[thread overview]
Message-ID: <51EEDC73.5020101@profihost.ag> (raw)
In-Reply-To: <CA+res+Ti1-tGANkb9wRAgF4sAcUqEv9RfGjDvbdX3bbxS=XK8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

It's 3.10 with bcache Updates from kent's for 3.10 branch.

Stefan

This mail was sent with my iPhone.

Am 23.07.2013 um 18:00 schrieb Jack Wang <jack.wang.usish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 
<mailto:jack.wang.usish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>>:

> Hi Stefan,
>
> Strange, I tested bcache 2 month ago, mostly bcache-3.2 branch in 
> writeback mode, it works as claimed.
>
> which kernel version are you using?
>
> Jack
>
>
> 2013/7/23 Stefan Priebe - Profihost AG <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org 
> <mailto:s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>>
>
>     Hi,
>
>     maybe i missed something or maybe i'm just wrong.
>
>
>     # cat /sys/block/bcache2/bcache/sequential_cutoff
>     512k
>
>     # cat /sys/block/bcache2/bcache/stats_five_minute/bypassed
>     64.3M
>
>     # dd if=/dev/zero of=/mnt/bcache2/ttt bs=4M count=1000 oflag=direct
>     1000+0 records in
>     1000+0 records out
>     4194304000 bytes (4,2 GB) copied, 11,0348 s, 380 MB/s
>
>     # cat /sys/block/bcache2/bcache/stats_five_minute/bypassed
>     69.3M
>
>     I also see only IOP/s an writes go to the SSD but not to the disk
>     behind. What's wrong?
>
>     Greets,
>     Stefan
>     --
>     To unsubscribe from this list: send the line "unsubscribe
>     linux-bcache" in
>     the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>     <mailto:majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
>     More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>

  parent reply	other threads:[~2013-07-23 19:41 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 [this message]
     [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
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=51EEDC73.5020101@profihost.ag \
    --to=s.priebe-2lf/h1ldwehr5kwtpvns9a@public.gmane.org \
    --cc=jack.wang.usish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kmo-PEzghdH756F8UrSeD/g0lQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox