From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Kent Overstreet <kmo@daterainc.com>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: patch (Re: 3.18.3 + latest bcache-dev)
Date: Thu, 22 Jan 2015 13:56:25 +0100 [thread overview]
Message-ID: <20150122125625.GB23810@cuci.nl> (raw)
In-Reply-To: <20150122123332.GA23810@cuci.nl>
Stephen R. van den Berg wrote:
>d. Came back in a patched kernel, 100% CPU usage is gone.
I spoke too soon. After some more copying, the 100% CPU is back, but
different:
Before I had four or five HDDs, but in both cases I had four bcache_writebac
processes running at 100%.
Now I have four HDDs, and also four bcache_writebac processes, but
only three of those run at 100% CPU. The fourth one is idle (mostly).
--
Stephen.
next prev parent reply other threads:[~2015-01-22 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 1:24 3.18.3 + latest bcache-dev Stephen R. van den Berg
2015-01-21 8:00 ` Kent Overstreet
2015-01-21 11:04 ` Stephen R. van den Berg
2015-01-21 16:45 ` Stephen R. van den Berg
2015-01-22 12:33 ` patch (Re: 3.18.3 + latest bcache-dev) Stephen R. van den Berg
2015-01-22 12:56 ` Stephen R. van den Berg [this message]
2015-01-21 22:47 ` 3.18.3 + latest bcache-dev Slava Pestov
2015-01-21 23:04 ` Stephen R. van den Berg
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=20150122125625.GB23810@cuci.nl \
--to=srb@cuci.nl \
--cc=kmo@daterainc.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 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.