From: xu xin <xu.xin.sc@gmail.com>
To: akpm@linux-foundation.org
Cc: david@redhat.com, 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, yang.yang29@zte.com.cn
Subject: Re: [PATCH v6 0/6] ksm: support tracking KSM-placed zero-pages
Date: Fri, 14 Apr 2023 09:35:07 +0800 [thread overview]
Message-ID: <20230414013507.184195-1-xu.xin16@zte.com.cn> (raw)
In-Reply-To: <20230328153852.26c2577e4bd921c371c47a7e@linux-foundation.org>
>> 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 have sent the v7 series, so some old codes might be changed, and no need to talk
more.
>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
>
Claudia is right, but the v7 patches don't rely on rmap_items now, so we can skip
this comment.
>- Hoping for overall review from David
>
David's review is great, and we accept his advice on the basic approach in v7 patches
to track the ksm zero pages. and now the v7 patches use pte_dirty to mark the
KSM-placed zere pages. But since pte_dirty is related to architectures, and some
architecture may treat pte_dirty as writable, so we restrict the feature of tracking
ksm zero pages only to the tested and well-working architecture.
>- Another query from Claudia, and a response indicating that a v7 is
> in the works.
> https://lore.kernel.org/all/20230307194320.79373a26@p-imbrenda/T/#u
The v7 series don't changed it there now, then we can skip it.
>
>- Another unresponded-to review query:
> https://lkml.kernel.org/r/20230307195119.745d0b46@p-imbrenda
>
The v7 series have referred to Claudia's review but made a few modifications.
>- Another response indicating that a v7 is coming
> https://lkml.kernel.org/r/20230307195313.2e21245a@p-imbrenda
>
> So I think I'll drop the v6 series. Please address all these things in
> the next version and let's start over.
Yes, the next version is here:
https://lore.kernel.org/lkml/202304131346489021903@zte.com.cn/
next prev parent reply other threads:[~2023-04-14 1:35 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
2023-03-30 12:06 ` xu xin
2023-04-03 15:20 ` David Hildenbrand
2023-04-14 1:35 ` xu xin [this message]
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=20230414013507.184195-1-xu.xin16@zte.com.cn \
--to=xu.xin.sc@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--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.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