Displaying 3 results from an estimated 3 matches for "folio_ops".
2024 Nov 12
1
[RFC PATCH v1 00/10] mm: Introduce and use folio_owner_ops
...te that this has "owner_ops"
meaning. We'll have to make hugetlb not use folio->private and make
others not use bitX. Might be harder and overkill, because right now we
only really need the callback when refcount==0.
(c) Use some other indication that folio->private contains folio_ops.
--
Cheers,
David / dhildenb
2024 Nov 13
2
[RFC PATCH v1 00/10] mm: Introduce and use folio_owner_ops
...;owner_ops"
> meaning. We'll have to make hugetlb not use folio->private and make others
> not use bitX. Might be harder and overkill, because right now we only really
> need the callback when refcount==0.
>
> (c) Use some other indication that folio->private contains folio_ops.
I really don't want to use folio_ops / folio_owner_ops. I read
https://lore.kernel.org/all/CAGtprH_JP2w-4rq02h_Ugvq5KuHX7TUvegOS7xUs_iy5hriE7g at mail.gmail.com/
and I still don't understand what you're trying to do.
Would it work to use aops->free_folio() to notify you when the...
2024 Nov 12
1
[RFC PATCH v1 00/10] mm: Introduce and use folio_owner_ops
On Tue, Nov 12, 2024 at 10:10:06AM +0100, David Hildenbrand wrote:
> On 12.11.24 06:26, Matthew Wilcox wrote:
> > On Mon, Nov 11, 2024 at 08:26:54AM +0000, Fuad Tabba wrote:
> > > Thanks for your comments Jason, and for clarifying my cover letter
> > > David. I think David has covered everything, and I'll make sure to
> > > clarify this in the cover letter