From: Michal Hocko <mhocko@suse.com>
To: Zhongkun He <hezhongkun.hzk@bytedance.com>
Cc: minchan@kernel.org, senozhatsky@chromium.org, david@redhat.com,
yosryahmed@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] zram: objects charge to mem_cgroup
Date: Fri, 7 Jul 2023 09:57:09 +0200 [thread overview]
Message-ID: <ZKfFVfZovt4PnMsy@dhcp22.suse.cz> (raw)
In-Reply-To: <20230707044613.1169103-1-hezhongkun.hzk@bytedance.com>
On Fri 07-07-23 12:46:13, Zhongkun He wrote:
> This is a new solution to charge ZRAM objects,more simple than
> previous one[1],The compressed RAM is currently charged to
> kernel,not to any memory cgroup.
>
> As we know, zram can be used in two ways, direct and
> indirect, this patchset can charge memory in both cases.
> Direct zram usage by process within a cgroup will fail
> to charge if there is no memory. Indirect zram usage by
> process within a cgroup via swap in PF_MEMALLOC context,
> will charge successfully.
Please state the objective you are trying to achieve by this patchset.
It is always good to summarize the previous discussion and mention what
is done differently or how previous review feedback has been addressed
but the overall idea/purpose should be always explicit.
Please elaborate more about both.
> [1]
> https://lore.kernel.org/all/20230615034830.1361853-1-hezhongkun.hzk@bytedance.com/
>
> Zhongkun He (2):
> memcg: Add support for zram object charge
> zram: charge the compressed RAM to the page's memcgroup
>
> drivers/block/zram/zram_drv.c | 43 +++++++++++++++++++++++++++++++++++
> drivers/block/zram/zram_drv.h | 1 +
> include/linux/memcontrol.h | 10 ++++++++
> mm/memcontrol.c | 23 +++++++++++++++++++
> 4 files changed, 77 insertions(+)
>
> --
> 2.25.1
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2023-07-07 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 4:46 Zhongkun He
2023-07-07 7:57 ` Michal Hocko [this message]
2023-07-07 14:25 ` [External] " 贺中坤
2023-07-07 14:44 ` Michal Hocko
2023-07-10 9:35 ` 贺中坤
2023-07-10 10:41 ` Michal Hocko
2023-07-10 13:16 ` 贺中坤
2023-07-10 13:34 ` Michal Hocko
2023-07-10 15:02 ` 贺中坤
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=ZKfFVfZovt4PnMsy@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=david@redhat.com \
--cc=hezhongkun.hzk@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=yosryahmed@google.com \
/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
all inboxes | Powered by JetHome®