From: Zou Mingzhe <mingzhe.zou@easystack.cn>
To: Coly Li <colyli@suse.de>
Cc: linux-bcache@vger.kernel.org, dongsheng.yang@easystack.cn,
zoumingzhe@qq.com
Subject: Re: [PATCH] bcache: try to reuse the slot of invalid_uuid
Date: Mon, 6 Jun 2022 17:36:24 +0800 [thread overview]
Message-ID: <34d760d4-9d1b-7ec0-af90-3c8777fbe971@easystack.cn> (raw)
In-Reply-To: <780B6E6E-F4A8-4801-AED3-8DF81054D491@suse.de>
在 2022/6/6 16:57, Coly Li 写道:
>
>> 2022年6月6日 16:45,mingzhe.zou@easystack.cn 写道:
>>
>> From: mingzhe <mingzhe.zou@easystack.cn>
>>
>>
> [snipped]
>
>> We want to use those invalid_uuid slots carefully. Because, the bkey of the inode
>> may still exist in the btree. So, we need to check the btree before reuse it.
>>
>> Signed-off-by: mingzhe <mingzhe.zou@easystack.cn>
>> ---
>> drivers/md/bcache/btree.c | 35 +++++++++++++++++++++++++++++++++++
>> drivers/md/bcache/btree.h | 1 +
>> drivers/md/bcache/super.c | 15 ++++++++++++++-
>> 3 files changed, 50 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/md/bcache/btree.c b/drivers/md/bcache/btree.c
>> index e136d6edc1ed..a5d54af73111 100644
>> --- a/drivers/md/bcache/btree.c
>> +++ b/drivers/md/bcache/btree.c
>> @@ -2755,6 +2755,41 @@ struct keybuf_key *bch_keybuf_next_rescan(struct cache_set *c,
>> return ret;
>> }
>>
>> +static bool check_pred(struct keybuf *buf, struct bkey *k)
>> +{
>> + return true;
>> +}
>> +
>> +bool bch_btree_can_inode_reuse(struct cache_set *c, size_t inode)
>> +{
>> + bool ret = true;
>> + struct keybuf_key *k;
>> + struct bkey end_key = KEY(inode, MAX_KEY_OFFSET, 0);
>> + struct keybuf *keys = kzalloc(sizeof(struct keybuf), GFP_KERNEL);
>> +
>> + if (!keys) {
>> + ret = false;
>> + goto out;
>> + }
>> +
>> + bch_keybuf_init(keys);
>> + keys->last_scanned = KEY(inode, 0, 0);
>> +
>> + while (ret) {
>> + k = bch_keybuf_next_rescan(c, keys, &end_key, check_pred);
>> + if (!k)
>
> This is a single thread iteration, for a large filled cache device it can be very slow. I observed 40+ minutes during my testing.
>
>
> Coly Li
>
Hi, Coly
We first use the zero_uuid slot, and reuse only if there is no zero_uuid
slot. This is just an imperfect solution to make bcache available, so we
haven't tested its performance. We think we will eventually need to
actively clean up these bkeys in a new thread and reset the invalid_uuid
to zero_uuid.
mingzhe
>
>> + break;
>> +
>> + if (KEY_INODE(&k->key) == inode)
>> + ret = false;
>> + bch_keybuf_del(keys, k);
>> + }
>> +
>> + kfree(keys);
>> +out:
>> + return ret;
>> +}
>> +
>> void bch_keybuf_init(struct keybuf *buf)
>> {
>> buf->last_scanned = MAX_KEY;
>> diff --git a/drivers/md/bcache/btree.h b/drivers/md/bcache/btree.h
>> index 1b5fdbc0d83e..c3e6094adb62 100644
>> --- a/drivers/md/bcache/btree.h
>> +++ b/drivers/md/bcache/btree.h
>> @@ -413,4 +413,5 @@ struct keybuf_key *bch_keybuf_next_rescan(struct cache_set *c,
>> struct bkey *end,
>> keybuf_pred_fn *pred);
>> void bch_update_bucket_in_use(struct cache_set *c, struct gc_stat *stats);
>> +bool bch_btree_can_inode_reuse(struct cache_set *c, size_t inode);
>> #endif
>> diff --git a/drivers/md/bcache/super.c b/drivers/md/bcache/super.c
>> index 3563d15dbaf2..31f7aa347561 100644
>> --- a/drivers/md/bcache/super.c
>> +++ b/drivers/md/bcache/super.c
>> @@ -544,11 +544,24 @@ static struct uuid_entry *uuid_find(struct cache_set *c, const char *uuid)
>> return NULL;
>> }
>>
>> +static struct uuid_entry *uuid_find_reuse(struct cache_set *c)
>> +{
>> + struct uuid_entry *u;
>> +
>> + for (u = c->uuids; u < c->uuids + c->nr_uuids; u++)
>> + if (!memcmp(u->uuid, invalid_uuid, 16) &&
>> + bch_btree_can_inode_reuse(c, u - c->uuids))
>> + return u;
>> +
>> + return NULL;
>> +}
>> +
>> static struct uuid_entry *uuid_find_empty(struct cache_set *c)
>> {
>> static const char zero_uuid[16] = "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0";
>> + struct uuid_entry *u = uuid_find(c, zero_uuid);
>>
>> - return uuid_find(c, zero_uuid);
>> + return u ? u : uuid_find_reuse(c);
>> }
>>
>> /*
>> --
>> 2.17.1
>>
>
next prev parent reply other threads:[~2022-06-06 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 8:45 [PATCH] bcache: try to reuse the slot of invalid_uuid mingzhe.zou
2022-06-06 8:57 ` Coly Li
2022-06-06 9:36 ` Zou Mingzhe [this message]
[not found] ` <f19c392f-6ad8-9e0c-a8f7-de2339f76cb6@easystack.cn>
2022-06-06 10:34 ` Coly Li
2022-06-13 8:20 ` Zou Mingzhe
2022-06-13 8:35 ` Coly Li
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=34d760d4-9d1b-7ec0-af90-3c8777fbe971@easystack.cn \
--to=mingzhe.zou@easystack.cn \
--cc=colyli@suse.de \
--cc=dongsheng.yang@easystack.cn \
--cc=linux-bcache@vger.kernel.org \
--cc=zoumingzhe@qq.com \
/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