linux-kernel - Re: [PATCH] mm/zswap: export zswap API to modules

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 for Android: free password hash cracker in your pocket

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

Message-ID: <24bacfdd-ec42-4819-9b2d-f94e29fb1fbe@konsulko.se>
Date: Mon, 23 Jun 2025 12:10:40 +0200
From: Vitaly Wool <vitaly.wool@...sulko.se>
To: Matthew Wilcox <willy@...radead.org>
Cc: linux-mm@...ck.org, akpm@...ux-foundation.org,
 linux-kernel@...r.kernel.org, Igor Belousov <igor.b@...dev.am>
Subject: Re: [PATCH] mm/zswap: export zswap API to modules



On 6/20/25 21:47, Matthew Wilcox wrote:
> On Fri, Jun 20, 2025 at 09:35:52PM +0200, Vitaly Wool wrote:
>> There is no reason to not let modules use zswap capabilies to
>> densely store unused pages in RAM. This will allow to remove some
>> homebrew solutions for e.g. GPU drivers in favor of plainly using
>> zswap pool.
> 
> I really think these should be _GPL exports.  And I'm not sure why the
> GPU drivers are using "homebrew solutions" instead of using the shmem
> APIs which work whether zswap is configured in or not.

shmem API adds an extra copy which would be nice to avoid. Changing 
exports to _GPL I have indeed no problem with.

~Vitaly