linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Brian Geffon <bgeffon@google.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Minchan Kim <minchan@kernel.org>,
	 Yuwen Chen <ywen.chen@foxmail.com>,
	Richard Chang <richardycc@google.com>,
	 Fengyu Lian <licayy@outlook.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 linux-block@vger.kernel.org
Subject: Re: [RFC PATCHv5 5/6] zram: rework bdev block allocation
Date: Thu, 20 Nov 2025 11:35:58 -0500	[thread overview]
Message-ID: <CADyq12xHEQ4aFRdVDMkmuA1-r+FU7N4O7-8UUTpD9ACFo3tuZA@mail.gmail.com> (raw)
In-Reply-To: <20251120152126.3126298-6-senozhatsky@chromium.org>

On Thu, Nov 20, 2025 at 10:22 AM Sergey Senozhatsky
<senozhatsky@chromium.org> wrote:
>
> First, writeback bdev ->bitmap bits are set only from one
> context, as we can have only one single task performing
> writeback, so we cannot race with anything else.  Remove
> retry path.
>
> Second, we always check ZRAM_WB flag to distinguish writtenback
> slots, so we should not confuse 0 bdev block index and 0 handle.
> We can use first bdev block (0 bit) for writeback as well.
>
> While at it, give functions slightly more accurate names, as
> we don't alloc/free anything there, we reserve a block for
> async writeback or release the block.
>
> Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>

Reviewed-by: Brian Geffon <bgeffon@google.com>

> ---
>  drivers/block/zram/zram_drv.c | 37 +++++++++++++++++------------------
>  1 file changed, 18 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> index 671ef2ec9b11..ecbd9b25dfed 100644
> --- a/drivers/block/zram/zram_drv.c
> +++ b/drivers/block/zram/zram_drv.c
> @@ -500,6 +500,8 @@ static ssize_t idle_store(struct device *dev,
>  }
>
>  #ifdef CONFIG_ZRAM_WRITEBACK
> +#define INVALID_BDEV_BLOCK             (~0UL)
> +
>  struct zram_wb_ctl {
>         struct list_head idle_reqs;
>         struct list_head done_reqs;
> @@ -746,23 +748,20 @@ static ssize_t backing_dev_store(struct device *dev,
>         return err;
>  }
>
> -static unsigned long alloc_block_bdev(struct zram *zram)
> +static unsigned long zram_reserve_bdev_block(struct zram *zram)
>  {
> -       unsigned long blk_idx = 1;
> -retry:
> -       /* skip 0 bit to confuse zram.handle = 0 */
> -       blk_idx = find_next_zero_bit(zram->bitmap, zram->nr_pages, blk_idx);
> -       if (blk_idx == zram->nr_pages)
> -               return 0;
> +       unsigned long blk_idx;
>
> -       if (test_and_set_bit(blk_idx, zram->bitmap))
> -               goto retry;
> +       blk_idx = find_next_zero_bit(zram->bitmap, zram->nr_pages, 0);
> +       if (blk_idx == zram->nr_pages)
> +               return INVALID_BDEV_BLOCK;
>
> +       set_bit(blk_idx, zram->bitmap);
>         atomic64_inc(&zram->stats.bd_count);
>         return blk_idx;
>  }
>
> -static void free_block_bdev(struct zram *zram, unsigned long blk_idx)
> +static void zram_release_bdev_block(struct zram *zram, unsigned long blk_idx)
>  {
>         int was_set;
>
> @@ -887,7 +886,7 @@ static int zram_writeback_complete(struct zram *zram, struct zram_wb_req *req)
>                  * (if enabled).
>                  */
>                 zram_account_writeback_rollback(zram);
> -               free_block_bdev(zram, req->blk_idx);
> +               zram_release_bdev_block(zram, req->blk_idx);
>                 return err;
>         }
>
> @@ -901,7 +900,7 @@ static int zram_writeback_complete(struct zram *zram, struct zram_wb_req *req)
>          * finishes.
>          */
>         if (!zram_test_flag(zram, index, ZRAM_PP_SLOT)) {
> -               free_block_bdev(zram, req->blk_idx);
> +               zram_release_bdev_block(zram, req->blk_idx);
>                 goto out;
>         }
>
> @@ -989,8 +988,8 @@ static int zram_writeback_slots(struct zram *zram,
>                                 struct zram_pp_ctl *ctl,
>                                 struct zram_wb_ctl *wb_ctl)
>  {
> +       unsigned long blk_idx = INVALID_BDEV_BLOCK;
>         struct zram_wb_req *req = NULL;
> -       unsigned long blk_idx = 0;
>         struct zram_pp_slot *pps;
>         int ret = 0, err = 0;
>         u32 index = 0;
> @@ -1022,9 +1021,9 @@ static int zram_writeback_slots(struct zram *zram,
>                                 ret = err;
>                 }
>
> -               if (!blk_idx) {
> -                       blk_idx = alloc_block_bdev(zram);
> -                       if (!blk_idx) {
> +               if (blk_idx == INVALID_BDEV_BLOCK) {
> +                       blk_idx = zram_reserve_bdev_block(zram);
> +                       if (blk_idx == INVALID_BDEV_BLOCK) {
>                                 ret = -ENOSPC;
>                                 break;
>                         }
> @@ -1058,7 +1057,7 @@ static int zram_writeback_slots(struct zram *zram,
>                 __bio_add_page(&req->bio, req->page, PAGE_SIZE, 0);
>
>                 zram_submit_wb_request(zram, wb_ctl, req);
> -               blk_idx = 0;
> +               blk_idx = INVALID_BDEV_BLOCK;
>                 req = NULL;
>                 cond_resched();
>                 continue;
> @@ -1365,7 +1364,7 @@ static int read_from_bdev(struct zram *zram, struct page *page,
>         return -EIO;
>  }
>
> -static void free_block_bdev(struct zram *zram, unsigned long blk_idx)
> +static void zram_release_bdev_block(struct zram *zram, unsigned long blk_idx)
>  {
>  }
>  #endif
> @@ -1889,7 +1888,7 @@ static void zram_free_page(struct zram *zram, size_t index)
>
>         if (zram_test_flag(zram, index, ZRAM_WB)) {
>                 zram_clear_flag(zram, index, ZRAM_WB);
> -               free_block_bdev(zram, zram_get_handle(zram, index));
> +               zram_release_bdev_block(zram, zram_get_handle(zram, index));
>                 goto out;
>         }
>
> --
> 2.52.0.rc1.455.g30608eb744-goog
>


  reply	other threads:[~2025-11-20 16:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 15:21 [RFC PATCHv5 0/6] zram: introduce writeback bio batching Sergey Senozhatsky
2025-11-20 15:21 ` [RFC PATCHv5 1/6] " Sergey Senozhatsky
2025-11-21  7:05   ` Yuwen Chen
2025-11-21  7:18     ` Sergey Senozhatsky
2025-11-21  7:40   ` Hannes Reinecke
2025-11-21  7:47     ` Sergey Senozhatsky
2025-11-20 15:21 ` [RFC PATCHv5 2/6] zram: add writeback batch size device attr Sergey Senozhatsky
2025-11-20 15:57   ` Brian Geffon
2025-11-21  1:56     ` Sergey Senozhatsky
2025-11-21  2:48   ` Sergey Senozhatsky
2025-11-20 15:21 ` [RFC PATCHv5 3/6] zram: take write lock in wb limit store handlers Sergey Senozhatsky
2025-11-20 16:03   ` Brian Geffon
2025-11-20 15:21 ` [RFC PATCHv5 4/6] zram: drop wb_limit_lock Sergey Senozhatsky
2025-11-20 16:03   ` Brian Geffon
2025-11-20 15:21 ` [RFC PATCHv5 5/6] zram: rework bdev block allocation Sergey Senozhatsky
2025-11-20 16:35   ` Brian Geffon [this message]
2025-11-20 15:21 ` [RFC PATCHv5 6/6] zram: read slot block idx under slot lock Sergey Senozhatsky
2025-11-20 18:13   ` Brian Geffon
2025-11-24 14:49   ` Brian Geffon
2025-11-21  7:14 ` [RFC PATCHv5 0/6] zram: introduce writeback bio batching Yuwen Chen
2025-11-21  7:32   ` Sergey Senozhatsky
2025-11-21  7:44     ` Yuwen Chen
2025-11-21  7:58       ` Sergey Senozhatsky
2025-11-21  8:23         ` Yuwen Chen
2025-11-21  9:12           ` Sergey Senozhatsky
2025-11-21 12:21             ` Gao Xiang
2025-11-21 12:43               ` Gao Xiang
2025-11-22 10:07               ` Sergey Senozhatsky
2025-11-22 12:24                 ` Gao Xiang
2025-11-22 13:43                   ` Sergey Senozhatsky
2025-11-22 14:09                     ` Gao Xiang
2025-11-23  0:08                       ` Sergey Senozhatsky
2025-11-23  1:23                         ` Gao Xiang
2025-11-23  3:07                           ` Sergey Senozhatsky
2025-11-23  0:22                   ` Sergey Senozhatsky
2025-11-23  1:39                     ` Gao Xiang

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=CADyq12xHEQ4aFRdVDMkmuA1-r+FU7N4O7-8UUTpD9ACFo3tuZA@mail.gmail.com \
    --to=bgeffon@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=licayy@outlook.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=richardycc@google.com \
    --cc=senozhatsky@chromium.org \
    --cc=ywen.chen@foxmail.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