[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a4f42004-7c99-8c4e-259b-903254501529@gmail.com>
Date: Thu, 31 Mar 2022 18:44:31 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: cgel.zte@...il.com, akpm@...ux-foundation.org, david@...hat.com,
willy@...radead.org
Cc: corbet@....net, yang.yang29@....com.cn, yang.shi@...ux.alibaba.com,
dave.hansen@...ux.intel.com, saravanand@...com, minchan@...nel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, jhubbard@...dia.com,
xu xin <xu.xin16@....com.cn>,
Ran Xiaokai <ran.xiaokai@....com.cn>
Subject: Re: [PATCH v5] mm/vmstat: add events for ksm cow
On 31/03/22 10.56, cgel.zte@...il.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"?
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists