linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Norman.Kern" <norman.kern@gmx.com>
To: Coly Li <colyli@suse.de>
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Large latency with bcache for Ceph OSD(new mail thread)
Date: Tue, 2 Mar 2021 18:20:25 +0800	[thread overview]
Message-ID: <9b7dfd49-67b0-53b1-96e1-3b90c2d9d09a@gmx.com> (raw)

Sorry for creating a new mail thread(the origin is so long...)


I made a test again and get more infomation:

root@WXS0089:~# cat /sys/block/bcache0/bcache/dirty_data
0.0k
root@WXS0089:~# lsblk /dev/sda
NAME      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda         8:0    0 447.1G  0 disk
`-bcache0 252:0    0  10.9T  0 disk
root@WXS0089:~# cat /sys/block/sda/bcache/priority_stats
Unused:         1%
Clean:          29%
Dirty:          70%
Metadata:       0%
Average:        49
Sectors per Q:  29184768
Quantiles:      [1 2 3 5 6 8 9 11 13 14 16 19 21 23 26 29 32 36 39 43 48 53 59 65 73 83 94 109 129 156 203]
root@WXS0089:~# cat /sys/fs/bcache/066319e1-8680-4b5b-adb8-49596319154b/internal/gc_after_writeback
1
You have new mail in /var/mail/root
root@WXS0089:~# cat /sys/fs/bcache/066319e1-8680-4b5b-adb8-49596319154b/cache_available_percent
28

I read the source codes and found if cache_available_percent > 50, it should wakeup gc while doing writeback, but it seemed not work right.


             reply	other threads:[~2021-03-02 23:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 10:20 Norman.Kern [this message]
2021-03-02 13:20 ` Large latency with bcache for Ceph OSD(new mail thread) Coly Li
2021-03-03  3:25   ` Norman.Kern
2021-03-05  9:00   ` Norman.Kern
2021-03-05 10:03     ` Coly Li
2021-03-08  5:47       ` Norman.Kern

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=9b7dfd49-67b0-53b1-96e1-3b90c2d9d09a@gmx.com \
    --to=norman.kern@gmx.com \
    --cc=colyli@suse.de \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-block@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).