Re: [PATCH v5 00/18] zsmalloc/zram: there be preemption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Sergey Senozhatsky <senozhatsky@xxxxxxxxxxxx>
Subject: Re: [PATCH v5 00/18] zsmalloc/zram: there be preemption
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 12 Feb 2025 16:09:56 -0800
Cc: Yosry Ahmed <yosry.ahmed@xxxxxxxxx>, Kairui Song <ryncsn@xxxxxxxxx>, Minchan Kim <minchan@xxxxxxxxxx>, linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20250212063153.179231-1-senozhatsky@chromium.org>
References: <20250212063153.179231-1-senozhatsky@chromium.org>

On Wed, 12 Feb 2025 15:26:58 +0900 Sergey Senozhatsky <senozhatsky@xxxxxxxxxxxx> wrote:

> First, zsmalloc is converted to use sleepable RW-"lock" (it's atomic_t
> in fact) for zspage migration protection.

This sentence is stale?

Follow-Ups:
- Re: [PATCH v5 00/18] zsmalloc/zram: there be preemption
  - From: Sergey Senozhatsky

References:
- [PATCH v5 00/18] zsmalloc/zram: there be preemption
  - From: Sergey Senozhatsky

Prev by Date: Re: [PATCH v5 01/18] zram: sleepable entry locking
Next by Date: Re: [PATCH] mm: Fix possible NULL pointer dereference in __swap_duplicate
Previous by thread: [PATCH v5 16/18] zram: do not leak page on recompress_store error path
Next by thread: Re: [PATCH v5 00/18] zsmalloc/zram: there be preemption
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux