[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH5fLgjfiE6xNpKVBAgXu=eFyE65k+RxWqNt10J+44pK-mJgTw@mail.gmail.com>
Date: Fri, 26 Jul 2024 10:32:33 +0200
From: Alice Ryhl <aliceryhl@...gle.com>
To: Benno Lossin <benno.lossin@...ton.me>
Cc: Miguel Ojeda <ojeda@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>,
Alex Gaynor <alex.gaynor@...il.com>, Wedson Almeida Filho <wedsonaf@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Andreas Hindborg <a.hindborg@...sung.com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
rust-for-linux@...r.kernel.org
Subject: Re: [PATCH] rust: mm: add abstractions for mm_struct and vm_area_struct
On Fri, Jul 26, 2024 at 10:11 AM Benno Lossin <benno.lossin@...ton.me> wrote:
>
> On 23.07.24 16:32, Alice Ryhl wrote:
> > This is a follow-up to the page abstractions [1] that were recently
> > merged in 6.11. Rust Binder will need these abstractions to manipulate
> > the vma in its implementation of the mmap fop on the Binder file.
> >
> > The ARef wrapper is not used for mm_struct because there are several
> > different types of refcounts.
>
> I am confused, why can't you use the `ARef` wrapper for the different
> types that you create below?
Well, maybe I can, but it means we have several wrapper structs of
Opaque<mm_struct>. Would it not be confusing? Could you suggest a
naming scheme for the structs I should have?
Alice
Powered by blists - more mailing lists