From: "Danilo Krummrich" <dakr@kernel.org>
To: "Daniel Almeida" <daniel.almeida@collabora.com>
Cc: <ojeda@kernel.org>, <alex.gaynor@gmail.com>,
<boqun.feng@gmail.com>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <lossin@kernel.org>,
<a.hindborg@kernel.org>, <aliceryhl@google.com>,
<tmgross@umich.edu>, <abdiel.janulgue@gmail.com>,
<acourbot@nvidia.com>, <rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH] rust: page: implement BorrowedPage
Date: Tue, 05 Aug 2025 14:53:26 +0200 [thread overview]
Message-ID: <DBUIBXEOODEH.R2NYIGUDBZC7@kernel.org> (raw)
In-Reply-To: <731A34A7-92AD-47EA-A17A-C25FA94A5144@collabora.com>
On Tue Aug 5, 2025 at 2:30 PM CEST, Daniel Almeida wrote:
> Hi Danilo,
>
>> On 4 Aug 2025, at 16:50, Danilo Krummrich <dakr@kernel.org> wrote:
>>
>> Currently, a Page always owns the underlying struct page.
>>
>> However, sometimes a struct page may be owned by some other entity, e.g.
>> a vmalloc allocation.
>>
>> Hence, introduce BorrowedPage to support such cases, until the Ownable
>> solution lands.
>
> I guess it’s a good idea to expand this part somewhat. Taken as it is,
> there is no way to know what “the Ownable solution” is.
What do you suggest?
I can link where the type has been proposed by Boqun [1].
[1] https://lore.kernel.org/rust-for-linux/ZnCzLIly3DRK2eab@boqun-archlinux/
>> This is required by the scatterlist abstractions.
>>
>> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
>> ---
>> rust/bindings/bindings_helper.h | 1 +
>> rust/kernel/page.rs | 83 ++++++++++++++++++++++++++++++++-
>> 2 files changed, 83 insertions(+), 1 deletion(-)
>>
>> diff --git a/rust/bindings/bindings_helper.h b/rust/bindings/bindings_helper.h
>> index 84d60635e8a9..0e140e07758b 100644
>> --- a/rust/bindings/bindings_helper.h
>> +++ b/rust/bindings/bindings_helper.h
>> @@ -57,6 +57,7 @@
>> #include <linux/jiffies.h>
>> #include <linux/jump_label.h>
>> #include <linux/mdio.h>
>> +#include <linux/mm.h>
>> #include <linux/miscdevice.h>
>> #include <linux/of_device.h>
>> #include <linux/pci.h>
>> diff --git a/rust/kernel/page.rs b/rust/kernel/page.rs
>> index 7c1b17246ed5..bea7f0ab91f4 100644
>> --- a/rust/kernel/page.rs
>> +++ b/rust/kernel/page.rs
>> @@ -9,7 +9,12 @@
>> error::Result,
>> uaccess::UserSliceReader,
>> };
>> -use core::ptr::{self, NonNull};
>> +use core::{
>> + marker::PhantomData,
>> + mem::ManuallyDrop,
>> + ops::Deref,
>> + ptr::{self, NonNull},
>> +};
>>
>> /// A bitwise shift for the page size.
>> pub const PAGE_SHIFT: usize = bindings::PAGE_SHIFT as usize;
>> @@ -30,6 +35,82 @@ pub const fn page_align(addr: usize) -> usize {
>> (addr + (PAGE_SIZE - 1)) & PAGE_MASK
>> }
>>
>> +/// Representation of a non-owning reference to a [`Page`].
>> +///
>> +/// This type provides a borrowed version of a [`Page`] that is owned by some other entity, e.g. a
>> +/// [`Vmalloc`] allocation such as [`VBox`].
>> +///
>> +/// # Example
>> +///
>> +/// ```
>> +/// # use kernel::{bindings, prelude::*};
>> +/// use kernel::page::{BorrowedPage, Page, PAGE_SIZE};
>> +/// # use core::ptr;
>> +/// # use core::ptr::NonNull;
>> +///
>> +/// trait PageOwner {
>
> What is this trait for? Perhaps this assumes some previous discussion that is
> not in the patch itself?
It's just example code to show how a BorrowedPage may be obtained from something
that owns a page, i.e. a PageOwner.
However, I'm actually working on a trait similar to this example one as well.
next prev parent reply other threads:[~2025-08-05 12:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 19:50 [PATCH] rust: page: implement BorrowedPage Danilo Krummrich
2025-08-04 20:02 ` Benno Lossin
2025-08-04 20:08 ` Danilo Krummrich
2025-08-05 12:15 ` Alexandre Courbot
2025-08-05 12:18 ` Alice Ryhl
2025-08-05 12:30 ` Daniel Almeida
2025-08-05 12:53 ` Danilo Krummrich [this message]
2025-08-05 13:20 ` Danilo Krummrich
2025-08-05 13:29 ` Daniel Almeida
2025-08-05 17:07 ` Andreas Hindborg
2025-08-05 17:18 ` Danilo Krummrich
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=DBUIBXEOODEH.R2NYIGUDBZC7@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=acourbot@nvidia.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.