linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nanyong Sun <sunnanyong@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <xu.xin16@zte.com.cn>, <wangkefeng.wang@huawei.com>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH] mm/ksm: delete the redundant ksm_merging_pages interafce in proc
Date: Wed, 28 Jun 2023 10:44:34 +0800	[thread overview]
Message-ID: <000d6e0d-d4fc-abbf-5764-ab763e5dc8b2@huawei.com> (raw)
In-Reply-To: <20230627122201.6e25819493823dfc7cca4741@linux-foundation.org>

On 2023/6/28 3:22, Andrew Morton wrote:

> On Tue, 27 Jun 2023 21:35:42 +0800 Nanyong Sun <sunnanyong@huawei.com> wrote:
>
>> Since the ksm_merging_pages information already included in
>> /proc/<pid>/ksm_stat, we can delete /proc/<pid>/ksm_merging_pages to
>> make the directory more clean, and can save a little bit resources.
> Well, this is a non backward compatible change - any userspace
> which depends on ksm_merging_pages will break.
>
> Yes, we could remove this but it will be a lengthy process involving
> emitting a "please use ksm_stat instead" message for a few
> years before removal.
> .

This interface was just added last year(Apr 28 2022) in commit 7609385337a4

("ksm: count ksm merging pages for each process"), it does not have 
historical baggage.

Additionally, as stated in the commit message, this interface is mainly 
used to query the deduplication effect

of the application for the upper application optimization during the 
development phase,

so deleting it would have a very small impact.



  reply	other threads:[~2023-06-28  2:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 13:35 Nanyong Sun
2023-06-27 19:22 ` Andrew Morton
2023-06-28  2:44   ` Nanyong Sun [this message]
     [not found] ` <20230628031233.9734-1-xu.xin16@zte.com.cn>
2023-06-28  9:07   ` David Hildenbrand

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=000d6e0d-d4fc-abbf-5764-ab763e5dc8b2@huawei.com \
    --to=sunnanyong@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wangkefeng.wang@huawei.com \
    --cc=xu.xin16@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