linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Wool <vitaly.wool@konsulko.se>
To: David Hildenbrand <david@redhat.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	hannes@cmpxchg.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 0/3] mm: remove zpool
Date: Fri, 5 Sep 2025 07:36:20 +0200	[thread overview]
Message-ID: <bd3d2c7f-93a1-441c-b475-873d8d92e839@konsulko.se> (raw)
In-Reply-To: <8984f395-9043-49dd-a53d-bd344fd419bc@redhat.com>



On 9/4/25 13:26, David Hildenbrand wrote:
> On 04.09.25 12:13, Vlastimil Babka wrote:
>> On 9/4/25 11:33, Vitaly Wool wrote:
>>>> With zswap using zsmalloc directly, there are no more in-tree users of
>>>> this code. Remove it.
>>>>
>>>> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
>>>
>>> Per the previous discussions, this gets a *NACK* from my side. There is
>>> hardly anything _technical_ preventing new in-tree users of zpool API.
>>> zpool API is neutral and well-defined, I don’t see *any* good reason for
>>> it to be phased out.
>>
>> AFAIK it's a policy that unused code should be removed ASAP. And 
>> that's the
>> case for zpool after Patch 1, no? It could be different if another 
>> user was
>> about to be merged (to avoid unnecessary churn), but that doesn't seem 
>> the
>> case for zblock?
> 
> Right, and
> 
>   13 files changed, 84 insertions(+), 715 deletions(-)
> 
> speaks for itself if there is no new user anticipated.

Well, there surely is.

> IIRC, we did a similar approach when we removed frontswap.
> 



  reply	other threads:[~2025-09-05  5:36 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29 16:15 Johannes Weiner
2025-08-29 16:15 ` [PATCH 1/3] mm: zswap: interact directly with zsmalloc Johannes Weiner
2025-09-05 18:53   ` Yosry Ahmed
2025-09-09 15:01     ` Johannes Weiner
2025-09-09 20:10       ` Yosry Ahmed
2025-09-10 13:42         ` Johannes Weiner
2025-09-11 14:30           ` Yosry Ahmed
2025-09-15 15:36             ` Johannes Weiner
2025-09-15 19:33               ` Yosry Ahmed
2025-08-29 16:15 ` [PATCH 2/3] mm: remove unused zpool layer Johannes Weiner
2025-08-29 19:07   ` SeongJae Park
2025-09-09 15:13     ` Johannes Weiner
2025-09-10  3:14       ` SeongJae Park
2025-09-05 18:58   ` Yosry Ahmed
2025-09-09 15:16     ` Johannes Weiner
2025-09-09 20:08       ` Yosry Ahmed
2025-09-09 20:09         ` Yosry Ahmed
2025-09-10 13:46           ` Johannes Weiner
2025-08-29 16:15 ` [PATCH 3/3] mm: zpdesc: minor naming and comment corrections Johannes Weiner
2025-09-05 19:05   ` Yosry Ahmed
2025-09-09 15:11     ` Johannes Weiner
2025-09-09 20:08       ` Yosry Ahmed
2025-09-04  9:33 ` [PATCH 0/3] mm: remove zpool Vitaly Wool
2025-09-04 10:13   ` Vlastimil Babka
2025-09-04 11:26     ` David Hildenbrand
2025-09-05  5:36       ` Vitaly Wool [this message]
2025-09-04 14:11     ` Vitaly Wool
2025-09-05  7:03       ` Vlastimil Babka
2025-09-05 18:02       ` Nhat Pham
2025-09-05 22:42         ` Vitaly Wool
2025-09-05 19:57       ` Yosry Ahmed
2025-09-06  5:25         ` Sergey Senozhatsky
2025-09-08 12:18           ` Sergey Senozhatsky
2025-09-09 20:12             ` Yosry Ahmed
2025-09-13 13:55               ` Vitaly Wool
2025-09-15 19:37                 ` Yosry Ahmed
2025-09-16 11:16                   ` Vitaly Wool
2025-09-16  3:29                 ` Sergey Senozhatsky
2025-09-04 23:47   ` Andrew Morton
2025-09-05  5:42     ` Vitaly Wool
2025-09-05 18:30       ` Andrew Morton
2025-09-05 22:20         ` Vitaly Wool
2025-09-04  9:51 ` Vitaly Wool
2025-09-05 17:52 ` Nhat Pham
2025-09-05 19:45   ` Yosry Ahmed
2025-09-05 21:35     ` Nhat Pham
2025-09-09 15:03       ` Johannes Weiner
2025-09-09 20:11         ` Yosry Ahmed

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=bd3d2c7f-93a1-441c-b475-873d8d92e839@konsulko.se \
    --to=vitaly.wool@konsulko.se \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    /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