[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eabdd49c-d69c-91f3-c780-9bbf661f704c@redhat.com>
Date: Thu, 24 Mar 2022 13:49:25 +0100
From: David Hildenbrand <david@...hat.com>
To: Matthew Wilcox <willy@...radead.org>, cgel.zte@...il.com
Cc: akpm@...ux-foundation.org, yang.yang29@....com.cn,
ran.xiaokai@....com.cn, yang.shi@...ux.alibaba.com,
dave.hansen@...ux.intel.com, minchan@...nel.org, saravanand@...com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
xu xin <xu.xin16@....com.cn>
Subject: Re: [PATCH v3] mm/vmstat: add events for ksm cow
On 24.03.22 13:45, Matthew Wilcox wrote:
> On Thu, Mar 24, 2022 at 10:43:33AM +0000, cgel.zte@...il.com wrote:
>> +++ b/include/linux/vm_event_item.h
>> @@ -131,6 +131,7 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,
>> SWAP_RA_HIT,
>> #ifdef CONFIG_KSM
>> KSM_SWPIN_COPY,
>> + COW_KSM,
>
> Shouldn't we call this KSM_COW?
I guess I proposed COW_KSM because ideally we'll have COW_ANON,
COW_ZERO, COW_OTHER, ... so it'd be under the "COW" namespace. No strong
opinion, though.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists