From: "Sridhar, Kanchana P" <kanchana.p.sridhar@intel.com>
To: Barry Song <21cnbao@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"yosryahmed@google.com" <yosryahmed@google.com>,
"nphamcs@gmail.com" <nphamcs@gmail.com>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
"Huang, Ying" <ying.huang@intel.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Zou, Nanhai" <nanhai.zou@intel.com>,
"Feghali, Wajdi K" <wajdi.k.feghali@intel.com>,
"Gopal, Vinodh" <vinodh.gopal@intel.com>,
"Sridhar, Kanchana P" <kanchana.p.sridhar@intel.com>
Subject: RE: [RFC PATCH v1 4/4] mm: page_io: Count successful mTHP zswap stores in vmstat.
Date: Wed, 14 Aug 2024 17:47:53 +0000 [thread overview]
Message-ID: <SJ0PR11MB5678D231DF60ED05FFA85C18C9872@SJ0PR11MB5678.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAGsJ_4yng2ES6C8OSA2qoW5AwQ+zNdEAYWcNpoXmOP+m84qprg@mail.gmail.com>
Hi Barry,
> -----Original Message-----
> From: Barry Song <21cnbao@gmail.com>
> Sent: Wednesday, August 14, 2024 12:53 AM
> To: Sridhar, Kanchana P <kanchana.p.sridhar@intel.com>
> Cc: linux-kernel@vger.kernel.org; linux-mm@kvack.org;
> hannes@cmpxchg.org; yosryahmed@google.com; nphamcs@gmail.com;
> ryan.roberts@arm.com; Huang, Ying <ying.huang@intel.com>; akpm@linux-
> foundation.org; Zou, Nanhai <nanhai.zou@intel.com>; Feghali, Wajdi K
> <wajdi.k.feghali@intel.com>; Gopal, Vinodh <vinodh.gopal@intel.com>
> Subject: Re: [RFC PATCH v1 4/4] mm: page_io: Count successful mTHP zswap
> stores in vmstat.
>
> On Wed, Aug 14, 2024 at 6:28 PM Kanchana P Sridhar
> <kanchana.p.sridhar@intel.com> wrote:
> >
> > Added count_zswap_thp_swpout_vm_event() that will increment the
> > appropriate mTHP/PMD vmstat event counters if zswap_store succeeds for
> > a large folio:
> >
> > zswap_store mTHP order [0, HPAGE_PMD_ORDER-1] will increment these
> > vmstat event counters:
> >
> > ZSWPOUT_4KB_FOLIO
> > mTHP_ZSWPOUT_8kB
> > mTHP_ZSWPOUT_16kB
> > mTHP_ZSWPOUT_32kB
> > mTHP_ZSWPOUT_64kB
> > mTHP_ZSWPOUT_128kB
> > mTHP_ZSWPOUT_256kB
> > mTHP_ZSWPOUT_512kB
> > mTHP_ZSWPOUT_1024kB
> >
> > zswap_store of a PMD-size THP, i.e., mTHP order HPAGE_PMD_ORDER, will
> > increment both these vmstat event counters:
> >
> > ZSWPOUT_PMD_THP_FOLIO
> > mTHP_ZSWPOUT_2048kB
> >
> > Signed-off-by: Kanchana P Sridhar <kanchana.p.sridhar@intel.com>
> > ---
> > mm/page_io.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 44 insertions(+)
> >
> > diff --git a/mm/page_io.c b/mm/page_io.c
> > index 0a150c240bf4..ab54d2060cc4 100644
> > --- a/mm/page_io.c
> > +++ b/mm/page_io.c
> > @@ -172,6 +172,49 @@ int generic_swapfile_activate(struct
> swap_info_struct *sis,
> > goto out;
> > }
> >
> > +/*
> > + * Count vmstats for ZSWAP store of large folios (mTHP and PMD-size THP).
> > + */
> > +static inline void count_zswap_thp_swpout_vm_event(struct folio *folio)
> > +{
> > + if (IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE) &&
> folio_test_pmd_mappable(folio)) {
> > + count_vm_event(ZSWPOUT_PMD_THP_FOLIO);
> > + count_vm_event(mTHP_ZSWPOUT_2048kB);
> > + } else if (folio_order(folio) == 0) {
> > + count_vm_event(ZSWPOUT_4KB_FOLIO);
> > + } else if (IS_ENABLED(CONFIG_THP_SWAP)) {
> > + switch (folio_order(folio)) {
> > + case 1:
> > + count_vm_event(mTHP_ZSWPOUT_8kB);
> > + break;
> > + case 2:
> > + count_vm_event(mTHP_ZSWPOUT_16kB);
> > + break;
> > + case 3:
> > + count_vm_event(mTHP_ZSWPOUT_32kB);
> > + break;
> > + case 4:
> > + count_vm_event(mTHP_ZSWPOUT_64kB);
> > + break;
> > + case 5:
> > + count_vm_event(mTHP_ZSWPOUT_128kB);
> > + break;
> > + case 6:
> > + count_vm_event(mTHP_ZSWPOUT_256kB);
> > + break;
> > + case 7:
> > + count_vm_event(mTHP_ZSWPOUT_512kB);
> > + break;
> > + case 8:
> > + count_vm_event(mTHP_ZSWPOUT_1024kB);
> > + break;
> > + case 9:
> > + count_vm_event(mTHP_ZSWPOUT_2048kB);
> > + break;
> > + }
>
> The number of orders is PMD_ORDER, also ilog2(MAX_PTRS_PER_PTE) .
> PMD_ORDER isn't necessarily 9. It seems we need some general way
> to handle this and avoid so many duplicated case 1, case 2.... case 9.
Thanks for this suggestion. The general way to do this appears to be
simply calling count_mthp_stat(folio_order(folio), MTHP_STAT_[Z]SWPOUT)
potentially with the addition of a new "MTHP_STAT_ZSWPOUT" to
"enum mthp_stat_item".
I will make this change in v2 accordingly.
Thanks,
Kanchana
>
> > + }
> > +}
> > +
> > /*
> > * We may have stale swap cache pages in memory: notice
> > * them here and get rid of the unnecessary final write.
> > @@ -196,6 +239,7 @@ int swap_writepage(struct page *page, struct
> writeback_control *wbc)
> > return ret;
> > }
> > if (zswap_store(folio)) {
> > + count_zswap_thp_swpout_vm_event(folio);
> > folio_start_writeback(folio);
> > folio_unlock(folio);
> > folio_end_writeback(folio);
> > --
> > 2.27.0
> >
>
> Thanks
> Barry
prev parent reply other threads:[~2024-08-14 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 6:28 [RFC PATCH v1 0/4] mm: ZSWAP swap-out of mTHP folios Kanchana P Sridhar
2024-08-14 6:28 ` [RFC PATCH v1 1/4] mm: zswap: zswap_is_folio_same_filled() takes an index in the folio Kanchana P Sridhar
2024-08-14 6:28 ` [RFC PATCH v1 2/4] mm: vmstat: Per mTHP-size zswap_store vmstat event counters Kanchana P Sridhar
2024-08-14 7:48 ` Barry Song
2024-08-14 17:40 ` Sridhar, Kanchana P
2024-08-14 23:24 ` Barry Song
2024-08-15 1:37 ` Sridhar, Kanchana P
2024-08-14 6:28 ` [RFC PATCH v1 3/4] mm: zswap: zswap_store() extended to handle mTHP folios Kanchana P Sridhar
2024-08-14 6:28 ` [RFC PATCH v1 4/4] mm: page_io: Count successful mTHP zswap stores in vmstat Kanchana P Sridhar
2024-08-14 7:53 ` Barry Song
2024-08-14 17:47 ` Sridhar, Kanchana P [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=SJ0PR11MB5678D231DF60ED05FFA85C18C9872@SJ0PR11MB5678.namprd11.prod.outlook.com \
--to=kanchana.p.sridhar@intel.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nanhai.zou@intel.com \
--cc=nphamcs@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=vinodh.gopal@intel.com \
--cc=wajdi.k.feghali@intel.com \
--cc=ying.huang@intel.com \
--cc=yosryahmed@google.com \
/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