From: Coly Li <colyli@suse.de>
To: Michael Lyle <mlyle@lyle.org>, linux-bcache@vger.kernel.org
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH v4 00/13] bcache: device failure handling improvement
Date: Fri, 2 Feb 2018 10:04:15 +0800 [thread overview]
Message-ID: <aefd75a0-e7de-bbb6-386a-8e7f9a128e98@suse.de> (raw)
In-Reply-To: <2fde00b8-f605-d0d0-a51c-c126a2939326@lyle.org>
On 02/02/2018 5:52 AM, Michael Lyle wrote:
> On 01/27/2018 05:56 PM, Coly Li wrote:
>> Hi maintainers and folks,
>
> Hi Coly---
>
>> This patch set tries to improve bcache device failure handling, includes
>> cache device and backing device failures.
>
> I've skimmed this whole patchset and overall it looks good. I have
> taken some pieces (2,6) for possible-4.16. I understand you'll be
> sending out a v5 soon-- I'll perform a more detailed review then.
Hi Mike,
Since you will pick patch 2,6 from v4 patch set, I will not include them
in v5 patch set, and rebase the v5 cache set against the latest
bcache-for-next.
Thanks.
Coly Li
next prev parent reply other threads:[~2018-02-02 9:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 1:56 [PATCH v4 00/13] bcache: device failure handling improvement Coly Li
2018-01-28 1:56 ` [PATCH v4 01/13] bcache: set writeback_rate_update_seconds in range [1, 60] seconds Coly Li
2018-01-28 1:56 ` [PATCH v4 02/13] bcache: properly set task state in bch_writeback_thread() Coly Li
2018-01-28 1:56 ` [PATCH v4 03/13] bcache: fix cached_dev->count usage for bch_cache_set_error() Coly Li
2018-01-28 1:56 ` [PATCH v4 04/13] bcache: quit dc->writeback_thread when BCACHE_DEV_DETACHING is set Coly Li
2018-01-28 1:56 ` [PATCH v4 05/13] bcache: stop dc->writeback_rate_update properly Coly Li
2018-01-28 1:56 ` [PATCH v4 06/13] bcache: set error_limit correctly Coly Li
2018-01-28 1:56 ` [PATCH v4 07/13] bcache: add CACHE_SET_IO_DISABLE to struct cache_set flags Coly Li
2018-01-28 1:56 ` [PATCH v4 08/13] bcache: stop all attached bcache devices for a retired cache set Coly Li
2018-01-28 1:56 ` [PATCH v4 09/13] bcache: fix inaccurate io state for detached bcache devices Coly Li
2018-01-28 1:56 ` [PATCH v4 10/13] bcache: add backing_request_endio() for bi_end_io of attached backing device I/O Coly Li
2018-01-28 1:56 ` [PATCH v4 11/13] bcache: add io_disable to struct cached_dev Coly Li
2018-01-28 1:56 ` [PATCH v4 12/13] bcache: stop bcache device when backing device is offline Coly Li
2018-01-28 1:56 ` [PATCH v4 13/13] bcache: add stop_when_cache_set_failed to struct cached_dev Coly Li
2018-02-01 21:52 ` [PATCH v4 00/13] bcache: device failure handling improvement Michael Lyle
2018-02-02 2:04 ` Coly Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-27 14:23 Coly Li
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=aefd75a0-e7de-bbb6-386a-8e7f9a128e98@suse.de \
--to=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=mlyle@lyle.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