linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Lance Yang <ioworker0@gmail.com>
Cc: Baolin Wang <baolin.wang@linux.alibaba.com>,
	willy@infradead.org, sj@kernel.org, maskray@google.com,
	ziy@nvidia.com, ryan.roberts@arm.com, 21cnbao@gmail.com,
	mhocko@suse.com, fengwei.yin@intel.com, zokeefe@google.com,
	shy828301@gmail.com, xiehuan09@gmail.com, libang.li@antgroup.com,
	wangkefeng.wang@huawei.com, songmuchun@bytedance.com,
	peterx@redhat.com, minchan@kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/3] mm/rmap: integrate PMD-mapped folio splitting into pagewalk loop
Date: Tue, 7 May 2024 19:33:05 +0200	[thread overview]
Message-ID: <19645506-f17d-4202-807e-f0e5c99af742@redhat.com> (raw)
In-Reply-To: <20240507102241.0a09db69afd62efb5ce84f17@linux-foundation.org>

On 07.05.24 19:22, Andrew Morton wrote:
> On Tue, 7 May 2024 16:38:07 +0800 Lance Yang <ioworker0@gmail.com> wrote:
> 
>>>> Yep, I'll also set pvmw.ptl to NULL here if any corner cases arise.
>>>>
>>>
>>> This series already resides in mm-stable. I asked Andrew to remove it
>>> for now. If that doesn't work, we'll need fixup patches to address any
>>> review feedback.
>>
>> I'll patiently wait Andrew's response, and then submit the next version or
>> fixup patches accordingly.
> 
> Well, which series are we talking about?  "mm/madvise: enhance
> lazyfreeing with mTHP in madvise_free v10" or ""Reclaim lazyfree THP
> without splitting v4" or both?

See my other mail, "mm/madvise: enhance lazyfreeing with mTHP in 
madvise_free v10" is all acked/reviewed and good to go.

> 
> And how significant are the needed fixup patches?
> 
> And what is our confidence level after those fixups are in place?

I'm afraid I won't have time to review this series this/next week, so I 
cannot tell. I already assumed this would not be 6.10 material.

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-05-07 17:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01  4:26 [PATCH v4 0/3] Reclaim lazyfree THP without splitting Lance Yang
2024-05-01  4:26 ` [PATCH v4 1/3] mm/rmap: remove duplicated exit code in pagewalk loop Lance Yang
2024-05-07 14:51   ` Zi Yan
2024-05-07 14:53     ` Lance Yang
2024-05-01  4:26 ` [PATCH v4 2/3] mm/rmap: integrate PMD-mapped folio splitting into " Lance Yang
2024-05-07  3:40   ` Baolin Wang
2024-05-07  4:37     ` Lance Yang
2024-05-07  8:17       ` David Hildenbrand
2024-05-07  8:38         ` Lance Yang
2024-05-07 17:22           ` Andrew Morton
2024-05-07 17:33             ` David Hildenbrand [this message]
2024-05-07 17:38               ` Andrew Morton
2024-05-07 18:30                 ` David Hildenbrand
2024-05-07 15:26   ` Zi Yan
2024-05-08  5:43     ` Lance Yang
2024-05-08 14:07       ` Zi Yan
2024-05-08 14:35         ` Lance Yang
2024-05-08 14:48           ` Zi Yan
2024-05-08 14:56             ` Zi Yan
2024-05-08 15:52               ` Jason Gunthorpe
2024-05-08 16:22                 ` Zi Yan
2024-05-08 16:35                   ` Jason Gunthorpe
2024-05-09  8:21                     ` Lance Yang
2024-05-09 14:53                       ` Zi Yan
2024-05-09  8:56                     ` Lance Yang
2024-05-01  4:27 ` [PATCH v4 3/3] mm/vmscan: avoid split lazyfree THP during shrink_folio_list() Lance Yang
2024-05-07  4:00   ` Baolin Wang
2024-05-07  6:32     ` Lance Yang
2024-05-07  8:26       ` Lance Yang
2024-05-07  9:33         ` Baolin Wang
2024-05-07 11:37           ` Lance Yang
2024-05-09  9:36             ` Baolin Wang
2024-05-09 12:17               ` Lance Yang
2024-05-07 16:20   ` Zi Yan
2024-05-08  5:14     ` Lance Yang
2024-05-01 16:08 ` [PATCH v4 0/3] Reclaim lazyfree THP without splitting SeongJae Park
2024-05-02  0:30   ` Lance Yang

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=19645506-f17d-4202-807e-f0e5c99af742@redhat.com \
    --to=david@redhat.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=fengwei.yin@intel.com \
    --cc=ioworker0@gmail.com \
    --cc=libang.li@antgroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=maskray@google.com \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=peterx@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=shy828301@gmail.com \
    --cc=sj@kernel.org \
    --cc=songmuchun@bytedance.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --cc=xiehuan09@gmail.com \
    --cc=ziy@nvidia.com \
    --cc=zokeefe@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