From: David Hildenbrand <david@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>, yang.yang29@zte.com.cn
Cc: imbrenda@linux.ibm.com, jiang.xuexin@zte.com.cn,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
ran.xiaokai@zte.com.cn, xu.xin.sc@gmail.com, xu.xin16@zte.com.cn
Subject: Re: [PATCH v6 0/6] ksm: support tracking KSM-placed zero-pages
Date: Thu, 30 Mar 2023 06:47:17 +0200 [thread overview]
Message-ID: <78e35d88-8a4e-3b36-bbbd-94048c0c5b54@redhat.com> (raw)
In-Reply-To: <20230328153852.26c2577e4bd921c371c47a7e@linux-foundation.org>
On 29.03.23 00:38, Andrew Morton wrote:
> On Fri, 10 Feb 2023 09:15:22 +0800 (CST) <yang.yang29@zte.com.cn> wrote:
>
>> The core idea of this patch set is to enable users to perceive the number of any
>> pages merged by KSM, regardless of whether use_zero_page switch has been turned
>> on, so that users can know how much free memory increase is really due to their
>> madvise(MERGEABLE) actions. But the problem is, when enabling use_zero_pages,
>> all empty pages will be merged with kernel zero pages instead of with each
>> other as use_zero_pages is disabled, and then these zero-pages are no longer
>> monitored by KSM.
>
> We appear to have some outstanding activity on this quite old patchset.
> From my notes:
>
> - An unresponded-to question from Claudia:
> https://lkml.kernel.org/r/20230307192421.30ab869c@p-imbrenda
>
> - Hoping for overall review from David
I already shared some feedback in [1]. I think we should try to simplify
this handling, as proposed in that mail. Still waiting for a reply.
[1]
https://lore.kernel.org/all/9d7a8be3-ee9e-3492-841b-a0af9952ef36@redhat.com/
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-03-30 4:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 1:15 yang.yang29
2023-03-13 13:03 ` David Hildenbrand
2023-03-13 14:10 ` Claudio Imbrenda
2023-03-13 16:04 ` David Hildenbrand
2023-03-28 22:38 ` Andrew Morton
2023-03-30 4:47 ` David Hildenbrand [this message]
2023-03-30 12:06 ` xu xin
2023-04-03 15:20 ` David Hildenbrand
2023-04-14 1:35 ` xu xin
2023-04-14 8:40 ` Claudio Imbrenda
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=78e35d88-8a4e-3b36-bbbd-94048c0c5b54@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=imbrenda@linux.ibm.com \
--cc=jiang.xuexin@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=xu.xin.sc@gmail.com \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/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