[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3vua4ekiwivbeulfirygpll2vhkrtjj7ezafolwyxjuujrcelx@iyx2apjk7oay>
Date: Thu, 13 Nov 2025 11:11:14 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Yuwen Chen <ywen.chen@...mail.com>
Cc: axboe@...nel.dk, akpm@...ux-foundation.org, bgeffon@...gle.com,
licayy@...look.com, linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, liumartin@...gle.com, minchan@...nel.org, richardycc@...gle.com,
senozhatsky@...omium.org
Subject: Re: [PATCH v4] zram: Implement multi-page write-back
On (25/11/06 09:49), Yuwen Chen wrote:
[..]
> +static int zram_writeback_slots(struct zram *zram, struct zram_pp_ctl *ctl)
> +{
[..]
> + struct zram_wb_request req_prealloc[2] = {0};
[..]
> + /* allocate memory for req_pool */
> + req_pool = kzalloc(sizeof(*req) * ZRAM_WB_REQ_CNT, GFP_KERNEL);
> + if (req_pool) {
> + req_pool_cnt = ZRAM_WB_REQ_CNT;
> + } else {
> + req_pool = req_prealloc;
> + req_pool_cnt = ARRAY_SIZE(req_prealloc);
> + }
This looks like a preliminary optimization, I'd probably prefer
to not have req_prealloc entirely.
Powered by blists - more mailing lists