[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aP-Ymcsoyls04jov@slm.duckdns.org>
Date: Mon, 27 Oct 2025 06:06:49 -1000
From: Tejun Heo <tj@...nel.org>
To: jinji zhong <jinji.z.zhong@...il.com>
Cc: minchan@...nel.org, senozhatsky@...omium.org,
philipp.reisner@...bit.com, lars.ellenberg@...bit.com,
christoph.boehmwalder@...bit.com, corbet@....net,
hannes@...xchg.org, mkoutny@...e.com, axboe@...nel.dk,
mhocko@...nel.org, roman.gushchin@...ux.dev, shakeel.butt@...ux.dev,
akpm@...ux-foundation.org, terrelln@...com, dsterba@...e.com,
muchun.song@...ux.dev, linux-kernel@...r.kernel.org,
drbd-dev@...ts.linbit.com, linux-doc@...r.kernel.org,
cgroups@...r.kernel.org, linux-block@...r.kernel.org,
linux-mm@...ck.org, zhongjinji@...or.com, liulu.liu@...or.com,
feng.han@...or.com
Subject: Re: [RFC PATCH 0/3] Introduce per-cgroup compression priority
Hello,
On Sun, Oct 26, 2025 at 01:05:07AM +0000, jinji zhong wrote:
> This patch introduces a per-cgroup compression priority mechanism,
> where different compression priorities map to different algorithms.
> This allows administrators to select appropriate compression
> algorithms on a per-cgroup basis.
I don't think it makes sense to tie this to cgroups. Is there something
preventing this from following the process hierarchy?
Thanks.
--
tejun
Powered by blists - more mailing lists