All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
To: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
Cc: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: speed up dirty data cleaning
Date: Fri, 08 Nov 2013 08:19:08 +0100	[thread overview]
Message-ID: <527C906C.8000905@profihost.ag> (raw)
In-Reply-To: <20131108024904.GL3842@kmo>

Am 08.11.2013 03:49, schrieb Kent Overstreet:
> On Thu, Nov 07, 2013 at 04:18:35PM +0100, Stefan Priebe - Profihost AG wrote:
>> After some time it seems to start writing out all the data at a good
>> disk speed.
>>
>> But how does bcache determine when to write which kind of data out of
>> bcache.
> 
> There's a PD controller that tries to keep the amount of dirty data at
> writeback_percent percentage of your cache size. But, since the dirty data
> account was _still_ broken, that would screw up that PD controller.
> 
> Workaround is to set writeback_percent to 0

Tried that but it doesn't seem to start cleaning correctly.

Stefan

      reply	other threads:[~2013-11-08  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 13:09 speed up dirty data cleaning Stefan Priebe - Profihost AG
     [not found] ` <527B90EF.10404-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-11-07 15:18   ` Stefan Priebe - Profihost AG
     [not found]     ` <527BAF4B.9080609-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-11-08  2:49       ` Kent Overstreet
2013-11-08  7:19         ` Stefan Priebe - Profihost AG [this message]

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=527C906C.8000905@profihost.ag \
    --to=s.priebe-2lf/h1ldwehr5kwtpvns9a@public.gmane.org \
    --cc=kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.