All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: bcache kernel 3.10 wrong bypassed values
Date: Thu, 04 Jul 2013 10:13:20 +0200	[thread overview]
Message-ID: <51D52EA0.80302@profihost.ag> (raw)

Hello list,

while testing bcache i noticed that while writing a big 48GB file the
sequential cutoff works fine i see only I/O on the disk but not on the
cache. I thought i would afterwards see a bypassed value of around 48GB
but it is only 1.2GB.

Is this expected? Is bcache in kernel 3.10 stable for production usage?

Greets,
Stefan

             reply	other threads:[~2013-07-04  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04  8:13 Stefan Priebe - Profihost AG [this message]
     [not found] ` <51D52EA0.80302-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12  1:55   ` bcache kernel 3.10 wrong bypassed values Kent Overstreet
2013-07-12  6:13     ` Stefan Priebe - Profihost AG
     [not found]       ` <51DF9E90.8070408-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12  8:20         ` Kent Overstreet
2013-07-12 11:18           ` 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=51D52EA0.80302@profihost.ag \
    --to=s.priebe-2lf/h1ldwehr5kwtpvns9a@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.