[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7d25bdf0-f225-4bcf-a0cc-d0364bbfc7c7@redhat.com>
Date: Tue, 7 Oct 2025 22:23:02 +0200
From: David Hildenbrand <david@...hat.com>
To: Peter Xu <peterx@...hat.com>, "Liam R. Howlett"
<Liam.Howlett@...cle.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Axel Rasmussen <axelrasmussen@...gle.com>, Vlastimil Babka <vbabka@...e.cz>,
James Houghton <jthoughton@...gle.com>, Nikita Kalyazin
<kalyazin@...zon.com>, Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
Ujwal Kundur <ujwal.kundur@...il.com>, Mike Rapoport <rppt@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Andrea Arcangeli <aarcange@...hat.com>, Michal Hocko <mhocko@...e.com>,
Muchun Song <muchun.song@...ux.dev>, Oscar Salvador <osalvador@...e.de>,
Hugh Dickins <hughd@...gle.com>, Suren Baghdasaryan <surenb@...gle.com>
Subject: Re: [PATCH v3 1/4] mm: Introduce vm_uffd_ops API
> I believe that's what David mentioned very initially here:
>
> https://lore.kernel.org/r/f1da3505-f17f-4829-80c1-696b1d99057d@redhat.com
>
> I'd rather go with the two fields, but if we're trying to introduce another
> feature sets almost only for vm_uffd_ops, I'd prefer keeping it simple, and
> deduce the modes from ioctls.
>
> Is that ok for you? So it'll have (1) get_folio(), (2) supported_ioctls.
> That's all.
I cannot speak for Liam, but for me that looks like the best way forward
for now.
I'd hope that we could get this all cleaned up at some point --
including hugetlb, because it's a pain to have the hugetlb special
casing all over the place even if it's at some point a legacy thing (we
all know it will stick around for years to come).
--
Cheers
David / dhildenb
Powered by blists - more mailing lists