public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Dongsu Park <dongsu.park-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: backporting bcache-testing to kernel 3.4
Date: Mon, 22 Apr 2013 21:21:00 +0200	[thread overview]
Message-ID: <20130422192100.GA16221@gmail.com> (raw)

Hi,

has anyone succeeded backporting bcache(-testing) branch to kernel 3.4?

I tried to get it working, patching commits from bcache-testing branch
as well as block patches by Kent, on top of Kernel 3.4.23.

* writeback mode
* backing device: MD-RAID0, or a HDD
* cache device: loopback device on tmpfs (for test)
* testing command:
   dd if=/dev/zero of=/dev/bcache0 bs=4K count=1M oflag=sync

Everything works fine, except for a problem of sync operation.
Every write request is being immediately flushed into backing device.
That's actually what I want to avoid in writeback caches.
Observing block I/Os with iostat, it's weird that no data is actually
written to backing device, despite of high IOPs. e.g.:

Device:  rrqm/s   wrqm/s  r/s     w/s    rMB/s    wMB/s
avgrq-sz avgqu-sz   await r_await w_await svctm  %util
vdb      0.00     0.00    0.00 2550.00    0.00     0.00
0.00     2.05       0.81  0.00    0.81    0.26   67.00

If I test bcache-testing branch based on kernel 3.9-rc3, which means
without backporting, then it works well without such massive bogus syncs.
bcache-3.2 is also fine. So I suppose there might be any change on the
block layer between 3.4 and 3.9, making bcache work in such a strange way.

Any idea?

Dongsu

             reply	other threads:[~2013-04-22 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 19:21 Dongsu Park [this message]
     [not found] ` <20130422192100.GA16221-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-24 20:41   ` backporting bcache-testing to kernel 3.4 Kent Overstreet

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=20130422192100.GA16221@gmail.com \
    --to=dongsu.park-eikl63zcoxah+58jc4qpia@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