linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Barry Song <baohua@kernel.org>
To: Usama Arif <usamaarif642@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	hannes@cmpxchg.org,  riel@surriel.com, shakeel.butt@linux.dev,
	roman.gushchin@linux.dev,  yuzhao@google.com, david@redhat.com,
	ryan.roberts@arm.com, rppt@kernel.org,  willy@infradead.org,
	cerasuolodomenico@gmail.com, ryncsn@gmail.com,  corbet@lwn.net,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	 kernel-team@meta.com
Subject: Re: [PATCH v4 4/6] mm: Introduce a pageflag for partially mapped folios
Date: Thu, 22 Aug 2024 05:25:03 +0800	[thread overview]
Message-ID: <CAGsJ_4yg5vEPfgdrjarenpscAMdih7pS7gW+RJG94TRX0BGrOg@mail.gmail.com> (raw)
In-Reply-To: <5ed479c9-21eb-4bc8-8c17-79e1b6081355@gmail.com>

On Thu, Aug 22, 2024 at 3:04 AM Usama Arif <usamaarif642@gmail.com> wrote:
>
>
>
> On 20/08/2024 17:30, Barry Song wrote:
>
> > Hi Usama,
> > thanks! I can't judge if we need this partially_mapped flag. but if we
> > need, the code
> > looks correct to me. I'd like to leave this to David and other experts to ack.
> >
>
> Thanks for the reviews!
>
> > an alternative approach might be two lists? one for entirely_mapped,
> > the other one
> > for split_deferred. also seems ugly ?
> >
>
> That was my very first prototype! I shifted to using a bool which I sent in v1, and then a bit in _flags_1 as David suggested. I believe a bit in _flags_1 is the best way forward, as it leaves the most space in folio for future work.
>

Thanks for the explanation; I missed the earlier discussion.

> > On the other hand, when we want to extend your patchset to mTHP other than PMD-
> > order, will the only deferred_list create huge lock contention while
> > adding or removing
> > folios from it?
> >
>
> Yes, I would imagine so. the deferred_split_queue is per memcg/node, so that helps.
>

Right.

> Also, this work is tied to khugepaged. So would need some thought when doing it for mTHP.
>
> I would imagine doing underused shrinker for mTHP would be less beneficial compared to doing it for 2M THP. But probably needs experimentation.
>

Agreed. I suspect this will be also useful for larger mTHPs like 1M and 512KB.
While lock contention might be a concern, it shouldn't be a barrier to
proceeding
with your patchset, which only supports PMD-order.

> Thanks
>

Thanks
Barry


  reply	other threads:[~2024-08-21 21:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  2:30 [PATCH v4 0/6] mm: split underused THPs Usama Arif
2024-08-19  2:30 ` [PATCH v4 1/6] mm: free zapped tail pages when splitting isolated thp Usama Arif
2024-08-19  2:30 ` [PATCH v4 2/6] mm: remap unused subpages to shared zeropage " Usama Arif
2024-08-19  2:30 ` [PATCH v4 3/6] mm: selftest to verify zero-filled pages are mapped to zeropage Usama Arif
2024-08-21 19:09   ` Usama Arif
2024-08-19  2:30 ` [PATCH v4 4/6] mm: Introduce a pageflag for partially mapped folios Usama Arif
2024-08-19  8:29   ` Barry Song
2024-08-19  8:30     ` Barry Song
2024-08-19 14:17     ` Usama Arif
2024-08-19 19:00       ` Barry Song
2024-08-19 20:16         ` Usama Arif
2024-08-19 21:34           ` Barry Song
2024-08-19 21:55             ` Barry Song
2024-08-20 19:35               ` Usama Arif
2024-08-20 21:30                 ` Barry Song
2024-08-21 19:04                   ` Usama Arif
2024-08-21 21:25                     ` Barry Song [this message]
2024-09-01 12:48                     ` Bang Li
2024-09-02 10:09                       ` Usama Arif
2024-08-19  2:30 ` [PATCH v4 5/6] mm: split underused THPs Usama Arif
2024-08-19  2:30 ` [PATCH v4 6/6] mm: add sysfs entry to disable splitting " Usama Arif

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=CAGsJ_4yg5vEPfgdrjarenpscAMdih7pS7gW+RJG94TRX0BGrOg@mail.gmail.com \
    --to=baohua@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cerasuolodomenico@gmail.com \
    --cc=corbet@lwn.net \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@meta.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@surriel.com \
    --cc=roman.gushchin@linux.dev \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=ryncsn@gmail.com \
    --cc=shakeel.butt@linux.dev \
    --cc=usamaarif642@gmail.com \
    --cc=willy@infradead.org \
    --cc=yuzhao@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