linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Sridhar, Kanchana P" <kanchana.p.sridhar@intel.com>
To: Yosry Ahmed <yosryahmed@google.com>, Nhat Pham <nphamcs@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>,
	"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
	"Huang, Ying" <ying.huang@intel.com>,
	"21cnbao@gmail.com" <21cnbao@gmail.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: [PATCH v4 0/4] mm: ZSWAP swap-out of mTHP folios
Date: Sat, 24 Aug 2024 06:24:14 +0000	[thread overview]
Message-ID: <SJ0PR11MB567847468457F7B094AF3AE5C9892@SJ0PR11MB5678.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJD7tka1KcL7O+=YanStLz9VnsJtoKkB0d5SDyFUrezno0Z2Sg@mail.gmail.com>

Hi Yosry,

> -----Original Message-----
> From: Yosry Ahmed <yosryahmed@google.com>
> Sent: Friday, August 23, 2024 8:10 PM
> To: Nhat Pham <nphamcs@gmail.com>
> Cc: Sridhar, Kanchana P <kanchana.p.sridhar@intel.com>; linux-
> kernel@vger.kernel.org; linux-mm@kvack.org; hannes@cmpxchg.org;
> ryan.roberts@arm.com; Huang, Ying <ying.huang@intel.com>;
> 21cnbao@gmail.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: [PATCH v4 0/4] mm: ZSWAP swap-out of mTHP folios
> 
> [..]
> >
> > I'm not trying to delay this patch - I fully believe in supporting
> > zswap for larger pages (both mTHP and THP - whatever the memory
> > reclaim subsystem throws at us).
> >
> > But we need to get to the bottom of this :) These are very suspicious
> > and concerning data. If this is something urgent, I can live with a
> > gate to enable/disable this, but I'd much prefer we understand what's
> > going on here.
> 
> Agreed. I don't think merging this support is urgent, so I think we
> should better understand what is happening here. If there is a problem
> with how we charge compressed memory today (temporary double charges),
> we need to sort this out before the the mTHP support, as it will only
> make things worse.
> 
> I have to admit I didn't take a deep look at the discussion and data,
> so there may be other problems that I didn't notice. It seems to me
> like Kanchana is doing more debugging to understand what is happening,
> so that's great!

This sounds good. I just shared the data and my learnings from some
debugging experiments. I would appreciate it if you can review this and
suggest next steps.

> 
> As for the patches, we should sort out the impact on a higher level
> before discussing implementation details. From a quick look though it
> seems like the first patch can be dropped after Usama's patches that
> remove the same-filled handling from zswap land, and the last two
> patches can be squashed.

Sure, this sounds good.

Thanks,
Kanchana

  reply	other threads:[~2024-08-24  6:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  2:16 Kanchana P Sridhar
2024-08-19  2:16 ` [PATCH v4 1/4] mm: zswap: zswap_is_folio_same_filled() takes an index in the folio Kanchana P Sridhar
2024-08-19  2:16 ` [PATCH v4 2/4] mm: zswap: zswap_store() extended to handle mTHP folios Kanchana P Sridhar
2024-08-20 20:03   ` Sridhar, Kanchana P
2024-08-19  2:16 ` [PATCH v4 3/4] mm: Add MTHP_STAT_ZSWPOUT to sysfs per-order mthp stats Kanchana P Sridhar
2024-08-19  2:16 ` [PATCH v4 4/4] mm: swap: Count successful mTHP ZSWAP stores in sysfs mTHP stats Kanchana P Sridhar
2024-08-19  3:16 ` [PATCH v4 0/4] mm: ZSWAP swap-out of mTHP folios Huang, Ying
2024-08-19  5:12   ` Sridhar, Kanchana P
2024-08-19  5:51     ` Huang, Ying
2024-08-20  3:00       ` Sridhar, Kanchana P
2024-08-20 21:13         ` Nhat Pham
2024-08-20 22:09           ` Sridhar, Kanchana P
2024-08-21 14:42 ` Nhat Pham
2024-08-21 19:07   ` Sridhar, Kanchana P
2024-08-24  6:21     ` Sridhar, Kanchana P
2024-08-26 14:12       ` Nhat Pham
2024-08-27  6:08         ` Sridhar, Kanchana P
2024-08-27 15:23           ` Nhat Pham
2024-08-27 15:30             ` Nhat Pham
2024-08-27 18:43               ` Sridhar, Kanchana P
2024-08-28  7:27                 ` Sridhar, Kanchana P
2024-08-27 18:42             ` Sridhar, Kanchana P
2024-08-28  7:24               ` Sridhar, Kanchana P
2024-08-28  7:43                 ` Yosry Ahmed
2024-08-28 18:50                   ` Sridhar, Kanchana P
2024-08-28 22:34                     ` Yosry Ahmed
2024-08-29  0:14                       ` Sridhar, Kanchana P
2024-08-24  3:09   ` Yosry Ahmed
2024-08-24  6:24     ` Sridhar, Kanchana P [this message]
2024-08-27 14:55 ` Nhat Pham
2024-08-27 18:09   ` Sridhar, Kanchana P

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=SJ0PR11MB567847468457F7B094AF3AE5C9892@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