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>] [day] [month] [year] [list]
Message-ID: <1709a150.2340.198c223db7a.Coremail.2023302111378@whu.edu.cn>
Date: Tue, 19 Aug 2025 19:43:06 +0800 (GMT+08:00)
From: 牛海程 <2023302111378@....edu.cn>
To: minchan@...nel.org
Cc: ngupta@...are.org, sergey.senozhatsky.work@...il.com, axboe@...nel.dk,
	linux-kernel@...r.kernel.org, linux-block@...r.kernel.org
Subject: [PATCH/RFC] Zram: Improved Compression with PID/VMA-aware Grouping

Dear Linux Kernel Zram Maintainers,

I am an open-source developer and have been working on some potential improvements to the Zram module, focusing on optimizing compression rates.My work is based on the Linux kernel version 5.10.240.

My recent work introduces the following changes:

1.PID and Virtual Address Tracking: During page swap-in operations at the swap layer, I've implemented a mechanism to record the Process ID (PID) and the corresponding virtual address of the page.
2.PID-aware Grouping and VMA Merging in Zram: Within the Zram layer, pages are now grouped based on their recorded PIDs. Following this grouping, pages with similar or contiguous virtual addresses within each PID group are merged before compression. The rationale behind this is that pages belonging to the same process and located adjacently in virtual memory are likely to contain related data, which could lead to better compression ratios when processed together.

Preliminary experiments using this approach have shown promising results:

With the LZ4 compression algorithm, we observed an approximate 3% increase in the overall compression rate.
With the ZSTD compression algorithm, the improvement was even more significant, reaching an approximate 4% increase in the overall compression rate.

I am writing to inquire if you believe this approach and its observed benefits are significant enough to warrant further consideration for upstreaming into the main Linux kernel. I would greatly appreciate your thoughts on the utility and potential implications of these changes, as well as any guidance on how to proceed with further development or formal submission.

Thank you for your time and consideration.
Best regards,
Haicheng Niu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ