rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hindborg <a.hindborg@kernel.org>
To: Daniel Almeida <daniel.almeida@collabora.com>,
	Danilo Krummrich <dakr@kernel.org>
Cc: ojeda@kernel.org, alex.gaynor@gmail.com, boqun.feng@gmail.com,
	gary@garyguo.net, bjorn3_gh@protonmail.com, lossin@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 19:07:50 +0200	[thread overview]
Message-ID: <87sei58zo9.fsf@kernel.org> (raw)
In-Reply-To: <B8A7994C-62C0-4BDA-A401-C788444C8934@collabora.com>

"Daniel Almeida" <daniel.almeida@collabora.com> writes:

>> On 5 Aug 2025, at 09:53, Danilo Krummrich <dakr@kernel.org> wrote:
>>
>> 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/
>
> Just this link is fine IMHO. I wasn’t aware of this discussion.
>

As far as I know, "[PATCH v11 0/4] New trait OwnableRefCounted for
ARef<->Owned conversion." [1] is the latest and greatest.


Best regards,
Andreas Hindborg


[1] https://lore.kernel.org/r/20250618-unique-ref-v11-0-49eadcdc0aa6@pm.me


  reply	other threads:[~2025-08-05 17:07 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
2025-08-05 13:20     ` Danilo Krummrich
2025-08-05 13:29     ` Daniel Almeida
2025-08-05 17:07       ` Andreas Hindborg [this message]
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=87sei58zo9.fsf@kernel.org \
    --to=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=dakr@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).