Displaying 3 results from an estimated 3 matches for "owner_op".
Did you mean:
owner_ops
2024 Nov 12
1
[RFC PATCH v1 00/10] mm: Introduce and use folio_owner_ops
...memdescs for hugetlb/guest_memfd that extend folios
in the future? I don't know, maybe.
I'm currently wondering if we can use folio->private for the time being.
Either
(a) If folio->private is still set once the refcount drops to 0, it
indicates that there is a freeing callback/owner_ops. We'll have to make
hugetlb not use folio->private and convert others to clear
folio->private before freeing.
(b) Use bitX of folio->private to indicate that this has "owner_ops"
meaning. We'll have to make hugetlb not use folio->private and make
others not use b...
2024 Nov 13
2
[RFC PATCH v1 00/10] mm: Introduce and use folio_owner_ops
...ed for ext4.
I don't know if Rust lets you do something like that.
> I'm currently wondering if we can use folio->private for the time being.
> Either
>
> (a) If folio->private is still set once the refcount drops to 0, it
> indicates that there is a freeing callback/owner_ops. We'll have to make
> hugetlb not use folio->private and convert others to clear folio->private
> before freeing.
>
> (b) Use bitX of folio->private to indicate that this has "owner_ops"
> meaning. We'll have to make hugetlb not use folio->private and...
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