All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kmo@daterainc.com>
To: "Stephen R. van den Berg" <srb@cuci.nl>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: 3.18.3 + latest bcache-dev
Date: Wed, 21 Jan 2015 00:00:17 -0800	[thread overview]
Message-ID: <CALJ65znLYCJaN2fHx0-7P8RQHPUVkaBpw=ckt0_tQjznth35rw@mail.gmail.com> (raw)
In-Reply-To: <20150121012424.GB5533@cuci.nl>

Try increasing btree_scan_ratelimit?

On Tue, Jan 20, 2015 at 5:24 PM, Stephen R. van den Berg <srb@cuci.nl> wrote:
> I have:
> 16GB RAM
> 16GB SSD swap
> 5 x 6TB HDD bcache backing storage
> 2 x 490GB SSD bcache cache (Crucial M550, 4KB block, 2M bucket size)
> writeback and trim enabled on bcache.
> I used the latestbcache tools from git.
>
> On the backing storage, I created a BTRFS using nossd and notrim.
>
> Now, whenever I boot, I end up with exactly 4 bcache_writebac
> processes pegged at  99 or 100% CPU.  This is on an octocore cpu.
> top shows it as 50% system time.  The four processes are marked as R,
> but I cannot trace them.
>
> Even after waiting for several minutes, the cpu load does not come down.
> The mounted volume simply seems to work, though.
>
> Any ideas?
> --
> Stephen.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-01-21  8:00 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 [this message]
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
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='CALJ65znLYCJaN2fHx0-7P8RQHPUVkaBpw=ckt0_tQjznth35rw@mail.gmail.com' \
    --to=kmo@daterainc.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=srb@cuci.nl \
    /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.