From: Coly Li <colyli@suse.de>
To: axboe@kernel.dk
Cc: linux-block@vger.kernel.org, linux-bcache@vger.kernel.org,
Coly Li <colyli@suse.de>
Subject: [PATCH 0/3] bcache-6.10 20240528
Date: Tue, 28 May 2024 20:09:11 +0800 [thread overview]
Message-ID: <20240528120914.28705-1-colyli@suse.de> (raw)
Hi Jens,
This series is just for the patch from Dongsheng Yang, due to more
testing needed, it comes after the first wave.
Dongsheng's patch helps to improve the latency of cache space
allocation. This patch has been shipped in product more than one year
by his team. Robert Pang from Google introduces this patch has been
tested inside Google with quite extended hardware configurations. Eric
Wheeler also deploys this patch in his production for 1+ months.
So far there is no issue reported for this patch, except for a bug in
existed code and easier to be trigger by Dongsheng's patch. This is why
my first patch is composed. Another patch from me is just a code
cleanup cought my eyes during the fix.
Please consider to take them, and thank you in advance.
Coly Li
---
Coly Li (2):
bcache: call force_wake_up_gc() if necessary in check_should_bypass()
bcache: code cleanup in __bch_bucket_alloc_set()
Dongsheng Yang (1):
bcache: allow allocator to invalidate bucket in gc
drivers/md/bcache/alloc.c | 21 +++++++--------------
drivers/md/bcache/bcache.h | 1 +
drivers/md/bcache/btree.c | 7 ++++++-
drivers/md/bcache/request.c | 16 +++++++++++++++-
4 files changed, 29 insertions(+), 16 deletions(-)
--
2.35.3
next reply other threads:[~2024-05-28 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 12:09 Coly Li [this message]
2024-05-28 12:09 ` [PATCH 1/3] bcache: allow allocator to invalidate bucket in gc Coly Li
2024-05-28 12:09 ` [PATCH 2/3] bcache: call force_wake_up_gc() if necessary in check_should_bypass() Coly Li
2024-05-28 12:09 ` [PATCH 3/3] bcache: code cleanup in __bch_bucket_alloc_set() Coly Li
2024-05-28 12:57 ` [PATCH 0/3] bcache-6.10 20240528 Jens Axboe
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=20240528120914.28705-1-colyli@suse.de \
--to=colyli@suse.de \
--cc=axboe@kernel.dk \
--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