From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: linmiaohe@huawei.com, william.roche@oracle.com,
harry.yoo@oracle.com, jane.chu@oracle.com,
nao.horiguchi@gmail.com, tony.luck@intel.com,
wangkefeng.wang@huawei.com, willy@infradead.org,
akpm@linux-foundation.org, osalvador@suse.de,
rientjes@google.com, duenwen@google.com, jthoughton@google.com,
jgg@nvidia.com, ankita@nvidia.com, peterx@redhat.com,
sidhartha.kumar@oracle.com, ziy@nvidia.com, david@redhat.com,
dave.hansen@linux.intel.com, muchun.song@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] memfd-based Userspace MFR Policy for HugeTLB
Date: Tue, 10 Nov 2026 10:16:26 +0000 [thread overview]
Message-ID: <avLunMb-pVIigmkT@gremlin> (raw)
In-Reply-To: <CACw3F51Q9TkMWr4WbnN07q60L6vj72-hFWwpqf0n6rf+drfb0A@mail.gmail.com>
On Mon, Nov 09, 2026 at 09:45:24PM -0800, Jiaqi Yan wrote:
> On Tue, May 26, 2026 at 9:23 AM Lorenzo Stoakes <ljs@kernel.org> wrote:
> >
> > Hi Jiaqi,
> >
> > It seems this series got stalled on review, wondered if you planned to
> > respin it at all?
>
> Hi Lorenzo,
>
> Sorry for the late reply.
>
> Yeah, I was stuck on the issue Miaohe pointed out for quite a long time...
>
> In offline chat with William <william.roche@oracle.com> he expressed
> interests in taking over this patch series. However, he seemed busy
> with something else and couldn't get to it.
>
> Fortunately we have more powerful AI now than we did six months ago.
> While I worked on [1] with an AI assistant since 2 weeks ago, I worked
> out a solution to the issue Miaohe raised [2] with the help from AI,
> and now a working draft patch series. I think by the end of this
> weekend, I can send out a v4 built on [1], the patch series I just
> posted for freeing high-order folio that has HWPoison subpages.
>
> [1] https://lore.kernel.org/linux-mm/20261110053331.2708996-1-jiaqiyan@google.com
> [2] https://lore.kernel.org/linux-mm/5e0fc743-eb44-b69f-01a2-da7b6f2eca8d@huawei.com/#t
Thanks for the update! Though do note [0], given the current wave of
AI-generated fixes this cycle is focused on that rather than new features (sorry
I know I chased this, but nobody anticipated how busy we would be with these!)
And since you mention AI, obligatory disclaimer: as with everything AI - please
rewrite all commit messages and comments in kernel mm style, and make sure you
understand every bit of the code when you submit! :)
--
Cheers, Lorenzo
[0]: https://lore.kernel.org/linux-mm/a2f584f6-e382-4876-aa6d-d5a34de6ee59@kernel.org/
prev parent reply other threads:[~2026-11-10 10:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 19:23 Jiaqi Yan
2026-02-03 19:23 ` [PATCH v3 1/3] mm: memfd/hugetlb: introduce memfd-based userspace MFR policy Jiaqi Yan
2026-02-04 17:29 ` William Roche
2026-02-10 4:46 ` Jiaqi Yan
2026-02-09 11:54 ` Miaohe Lin
2026-02-10 4:47 ` Jiaqi Yan
2026-02-10 7:31 ` Miaohe Lin
2026-02-13 5:01 ` Jiaqi Yan
2026-02-24 7:30 ` Miaohe Lin
2026-03-09 4:53 ` Jiaqi Yan
2026-03-09 7:41 ` Miaohe Lin
2026-03-09 15:47 ` Jiaqi Yan
2026-03-10 2:21 ` Miaohe Lin
2026-03-22 22:04 ` Jiaqi Yan
2026-03-30 7:33 ` Miaohe Lin
2026-02-03 19:23 ` [PATCH v3 2/3] selftests/mm: test userspace MFR for HugeTLB hugepage Jiaqi Yan
2026-02-04 17:53 ` William Roche
2026-02-12 3:11 ` Jiaqi Yan
2026-02-09 12:01 ` Miaohe Lin
2026-02-12 3:17 ` Jiaqi Yan
2026-02-03 19:23 ` [PATCH v3 3/3] Documentation: add documentation for MFD_MF_KEEP_UE_MAPPED Jiaqi Yan
2026-02-04 17:56 ` William Roche
2026-05-26 16:23 ` [PATCH v3 0/3] memfd-based Userspace MFR Policy for HugeTLB Lorenzo Stoakes
2026-11-10 5:45 ` Jiaqi Yan
2026-11-10 10:16 ` Lorenzo Stoakes (ARM) [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=avLunMb-pVIigmkT@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ankita@nvidia.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=duenwen@google.com \
--cc=harry.yoo@oracle.com \
--cc=jane.chu@oracle.com \
--cc=jgg@nvidia.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=peterx@redhat.com \
--cc=rientjes@google.com \
--cc=sidhartha.kumar@oracle.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.com \
--cc=william.roche@oracle.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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
all inboxes | Powered by JetHome®