From: Kent Overstreet <kmo@daterainc.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org
Subject: Re: bcache: Fix a writeback performance regression
Date: Thu, 22 Aug 2013 00:42:54 -0700 [thread overview]
Message-ID: <20130822074253.GD14935@kmo-pixel> (raw)
In-Reply-To: <5215BEA4.6040101@profihost.ag>
On Thu, Aug 22, 2013 at 09:32:52AM +0200, Stefan Priebe - Profihost AG wrote:
> great!
>
> Everything seems to work fine now! Except read_dirty always going to
> negative values after a reboot.
That one's fixed in 3.11 :)
next prev parent reply other threads:[~2013-08-22 7:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 22:59 [GIT PULL] bcache fixes for 3.11 Kent Overstreet
2013-08-15 6:43 ` Stefan Priebe - Profihost AG
2013-08-15 7:07 ` Kent Overstreet
2013-08-16 10:11 ` Stefan Priebe - Profihost AG
2013-08-18 22:09 ` bcache: Fix a writeback performance regression Stefan Priebe
2013-08-19 22:27 ` Kent Overstreet
2013-08-20 8:01 ` Stefan Priebe - Profihost AG
2013-08-20 8:07 ` Stefan Priebe - Profihost AG
2013-08-21 21:10 ` Kent Overstreet
2013-08-21 23:47 ` Kent Overstreet
2013-08-22 5:25 ` Stefan Priebe
2013-08-22 5:27 ` Stefan Priebe
2013-08-22 5:43 ` Kent Overstreet
2013-08-22 5:59 ` Stefan Priebe
2013-08-22 6:02 ` Kent Overstreet
2013-08-22 7:32 ` Stefan Priebe - Profihost AG
2013-08-22 7:42 ` Kent Overstreet [this message]
2013-08-26 19:21 ` Stefan Priebe
2013-08-28 3:37 ` kernel neophyte
2013-08-28 6:05 ` Kent Overstreet
2013-08-28 18:12 ` kernel neophyte
2013-08-28 18:38 ` Stefan Priebe - Profihost AG
2013-08-28 18:47 ` kernel neophyte
2013-08-28 19:20 ` Stefan Priebe
2013-08-28 20:12 ` kernel neophyte
2013-08-28 20:15 ` Stefan Priebe
2013-08-28 22:45 ` kernel neophyte
2013-08-29 18:52 ` Stefan Priebe
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=20130822074253.GD14935@kmo-pixel \
--to=kmo@daterainc.com \
--cc=axboe@kernel.dk \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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;
as well as URLs for NNTP newsgroup(s).