From: CGEL <cgel.zte@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: akpm@linux-foundation.org, david@redhat.com, willy@infradead.org,
corbet@lwn.net, yang.yang29@zte.com.cn,
yang.shi@linux.alibaba.com, dave.hansen@linux.intel.com,
saravanand@fb.com, minchan@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
jhubbard@nvidia.com, xu xin <xu.xin16@zte.com.cn>,
Ran Xiaokai <ran.xiaokai@zte.com.cn>
Subject: Re: [PATCH v5] mm/vmstat: add events for ksm cow
Date: Fri, 1 Apr 2022 01:35:00 +0000 [thread overview]
Message-ID: <624656c7.1c69fb81.9e8ee.5657@mx.google.com> (raw)
In-Reply-To: <a4f42004-7c99-8c4e-259b-903254501529@gmail.com>
On Thu, Mar 31, 2022 at 06:44:31PM +0700, Bagas Sanjaya wrote:
> On 31/03/22 10.56, cgel.zte@gmail.com wrote:
> > +Monitoring KSM events
> > +=====================
> > +
> > +There are some counters in /proc/vmstat that may be used to monitor KSM events.
> > +KSM might help save memory, it's a tradeoff by may suffering delay on KSM COW
> > +or on swapping in copy. Those events could help users evaluate whether or how
> > +to use KSM. For example, if cow_ksm increases too fast, user may decrease the
> > +range of madvise(, , MADV_MERGEABLE).
> > +
>
> Did you mean "tradeoff between possible delay on KSM COW and swapping
> in copy"?
>
I mean both are tradeoff, or in other words KSM sacrifices time to gain space.
KSM COW please see do_wp_page(), KSM swapping in copy see ksm_might_need_to_copy().
Thanks.
> --
> An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2022-04-01 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 3:56 cgel.zte
2022-03-31 11:44 ` Bagas Sanjaya
2022-04-01 1:35 ` CGEL [this message]
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=624656c7.1c69fb81.9e8ee.5657@mx.google.com \
--to=cgel.zte@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=saravanand@fb.com \
--cc=willy@infradead.org \
--cc=xu.xin16@zte.com.cn \
--cc=yang.shi@linux.alibaba.com \
--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