linux-kernel - Re: [PATCH v2 2/3] zram: add async writeback infrastructure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46a544bd-a3dd-4a6f-967c-74c3bbe8f18c@acm.org>
Date: Thu, 31 Jul 2025 08:24:00 -0700
From: Bart Van Assche <bvanassche@....org>
To: Richard Chang <richardycc@...gle.com>, Minchan Kim <minchan@...nel.org>,
 Sergey Senozhatsky <senozhatsky@...omium.org>, Jens Axboe <axboe@...nel.dk>,
 Andrew Morton <akpm@...ux-foundation.org>
Cc: bgeffon@...gle.com, liumartin@...gle.com, linux-kernel@...r.kernel.org,
 linux-block@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v2 2/3] zram: add async writeback infrastructure

On 7/30/25 11:49 PM, Richard Chang wrote:
> Introduce the necessary infrastructure for performing writeback
> operations asynchronously.
> It adds a dedicated kernel thread (`zram_wb_thread`), a request queue
> for managing pending writebacks, and helper functions to deal with
> the writeback requests.

Why a new kernel thread instead of a workqueue? More memory (e.g. for
a stack) is required when a new kernel thread is created compared to
using the workqueue mechanism.

Bart.