From: zhongjinji <zhongjinji@honor.com>
To: <tj@kernel.org>
Cc: <akpm@linux-foundation.org>, <axboe@kernel.dk>,
<cgroups@vger.kernel.org>, <christoph.boehmwalder@linbit.com>,
<corbet@lwn.net>, <drbd-dev@lists.linbit.com>, <dsterba@suse.com>,
<feng.han@honor.com>, <hannes@cmpxchg.org>,
<jinji.z.zhong@gmail.com>, <lars.ellenberg@linbit.com>,
<linux-block@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<liulu.liu@honor.com>, <mhocko@kernel.org>, <minchan@kernel.org>,
<mkoutny@suse.com>, <muchun.song@linux.dev>,
<philipp.reisner@linbit.com>, <roman.gushchin@linux.dev>,
<senozhatsky@chromium.org>, <shakeel.butt@linux.dev>,
<terrelln@fb.com>, <zhongjinji@honor.com>
Subject: Re: [RFC PATCH 0/3] Introduce per-cgroup compression priority
Date: Thu, 30 Oct 2025 17:22:58 +0800 [thread overview]
Message-ID: <20251030092258.2576-1-zhongjinji@honor.com> (raw)
In-Reply-To: <aP-Ymcsoyls04jov@slm.duckdns.org>
> 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.
Hello, Tejun,
There is also a layer of page tables between the process and the page,
so making it follow the process hierarchy would be complicated.
But you make a good point; it may indeed be unnecessary to introduce
a separate per-cgroup compression priority. As Nhat suggested,
we could try reusing the per-cgroup swap priority.
> --
> tejun
next prev parent reply other threads:[~2025-10-30 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 1:05 jinji zhong
2025-10-26 1:05 ` [RFC PATCH 1/3] mm/memcontrol: " jinji zhong
2025-10-26 1:05 ` [RFC PATCH 2/3] zram: Zram supports " jinji zhong
2025-10-26 1:05 ` [RFC PATCH 3/3] Doc: Update documentation for " jinji zhong
2025-10-27 16:06 ` [RFC PATCH 0/3] Introduce " Tejun Heo
2025-10-30 9:22 ` zhongjinji [this message]
2025-10-27 17:29 ` Shakeel Butt
2025-10-30 11:32 ` zhongjinji
2025-10-27 22:46 ` Nhat Pham
2025-10-28 3:31 ` Sergey Senozhatsky
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=20251030092258.2576-1-zhongjinji@honor.com \
--to=zhongjinji@honor.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=christoph.boehmwalder@linbit.com \
--cc=corbet@lwn.net \
--cc=drbd-dev@lists.linbit.com \
--cc=dsterba@suse.com \
--cc=feng.han@honor.com \
--cc=hannes@cmpxchg.org \
--cc=jinji.z.zhong@gmail.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liulu.liu@honor.com \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=philipp.reisner@linbit.com \
--cc=roman.gushchin@linux.dev \
--cc=senozhatsky@chromium.org \
--cc=shakeel.butt@linux.dev \
--cc=terrelln@fb.com \
--cc=tj@kernel.org \
/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