From: Coly Li <colyli@suse.de>
To: Yaowei Bai <baiyaowei@cmss.chinamobile.com>, kent.overstreet@gmail.com
Cc: linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] bcache: use allocator reserves instead of watermarks
Date: Sat, 27 Jul 2019 22:13:22 +0800 [thread overview]
Message-ID: <4bc32702-9d83-1ac5-4c79-2d9e45123da8@suse.de> (raw)
In-Reply-To: <1564222799-10603-2-git-send-email-baiyaowei@cmss.chinamobile.com>
On 2019/7/27 6:19 下午, Yaowei Bai wrote:
> Commit 78365411b344 ("bcache: Rework allocator reserves") introduced
> allocator reserves and dropped watermarks, let's keep this consistent
> to avoid confusing.
>
> Signed-off-by: Yaowei Bai <baiyaowei@cmss.chinamobile.com>
It is OK to me, I will add it to my for-test.
Thanks.
Coly Li
> ---
> drivers/md/bcache/alloc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/md/bcache/alloc.c b/drivers/md/bcache/alloc.c
> index c22c260..609df38 100644
> --- a/drivers/md/bcache/alloc.c
> +++ b/drivers/md/bcache/alloc.c
> @@ -622,13 +622,13 @@ bool bch_alloc_sectors(struct cache_set *c,
> spin_lock(&c->data_bucket_lock);
>
> while (!(b = pick_data_bucket(c, k, write_point, &alloc.key))) {
> - unsigned int watermark = write_prio
> + unsigned int reserve = write_prio
> ? RESERVE_MOVINGGC
> : RESERVE_NONE;
>
> spin_unlock(&c->data_bucket_lock);
>
> - if (bch_bucket_alloc_set(c, watermark, &alloc.key, 1, wait))
> + if (bch_bucket_alloc_set(c, reserve, &alloc.key, 1, wait))
> return false;
>
> spin_lock(&c->data_bucket_lock);
>
next prev parent reply other threads:[~2019-07-27 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 10:19 [PATCH 1/3] bcache: drop obsolete comments Yaowei Bai
2019-07-27 10:19 ` [PATCH 2/3] bcache: use allocator reserves instead of watermarks Yaowei Bai
2019-07-27 14:13 ` Coly Li [this message]
2019-07-27 10:19 ` [PATCH 3/3] bcache: count cache_available_percent accurately Yaowei Bai
2019-07-27 14:39 ` Coly Li
2019-07-27 14:12 ` [PATCH 1/3] bcache: drop obsolete comments 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=4bc32702-9d83-1ac5-4c79-2d9e45123da8@suse.de \
--to=colyli@suse.de \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®