From: Peter Kieser <peter@kieser.ca>
Cc: Daniel Smedegaard Buus <danielbuus@gmail.com>,
linux-bcache@vger.kernel.org
Subject: Re: [PATCH] bcache: fix writeback thread to sleep less intrusively
Date: Wed, 09 Jul 2014 08:53:46 -0700 [thread overview]
Message-ID: <53BD658A.9020100@kieser.ca> (raw)
In-Reply-To: <CAHnuAez0rb9PLLEU7sB79x2_w14bJre+4ZbkWKyO+YUF255Czw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On 2014-07-09 3:27 AM, Daniel Smedegaard Buus wrote:
> On Thu, May 1, 2014 at 11:53 PM, Slava Pestov<sp@datera.io> wrote:
>> >Hi Daniel and Darrick,
>> >
>> >I mailed a patch that attempts to fix the uninterruptible issue while taking
>> >Kent's feedback regarding your earlier patch into account. Please test it
>> >out and let me know what you think.
>> >
> Curious about what ever happened to this bug. This patch fixed the
> load bug, but with new problems added...
What other bugs did it introduce?
-Peter
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4504 bytes --]
next prev parent reply other threads:[~2014-07-09 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 0:26 [PATCH] bcache: fix writeback thread to sleep less intrusively Darrick J. Wong
2014-04-11 0:46 ` Kent Overstreet
2014-04-11 1:41 ` Darrick J. Wong
2014-04-12 2:31 ` Darrick J. Wong
2014-04-12 2:33 ` [PATCH] bcache: let the writeback thread run at least once at startup Darrick J. Wong
2014-04-30 11:51 ` [PATCH] bcache: fix writeback thread to sleep less intrusively Daniel Smedegaard Buus
2014-04-30 17:24 ` Darrick J. Wong
2014-05-01 9:38 ` Daniel Smedegaard Buus
2014-05-01 21:54 ` Slava Pestov
2014-05-20 7:07 ` Daniel J Blueman
[not found] ` <CACHGV4+mNu_KV7JazT-34D++3S2NKhDkOmc_wo0QfrfdqpccoQ@mail.gmail.com>
2014-07-09 10:27 ` Daniel Smedegaard Buus
2014-07-09 15:53 ` Peter Kieser [this message]
2014-07-09 18:02 ` Daniel Smedegaard Buus
2014-07-09 18:19 ` Slava Pestov
2014-07-09 19:18 ` Daniel Smedegaard Buus
2014-04-11 7:26 ` Francis Moreau
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=53BD658A.9020100@kieser.ca \
--to=peter@kieser.ca \
--cc=danielbuus@gmail.com \
--cc=linux-bcache@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).