rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@redhat.com>
To: Wedson Almeida Filho <wedsonaf@gmail.com>,
	Zhi Wang <zhiw@nvidia.com>,
	rust-for-linux@vger.kernel.org
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@samsung.com>,
	"Alice Ryhl" <aliceryhl@google.com>,
	linux-kernel@vger.kernel.org,
	"Wedson Almeida Filho" <walmeida@microsoft.com>,
	ajanulgu@redhat.com, "Andy Currid" <acurrid@nvidia.com>,
	"Neo Jia" <cjia@nvidia.com>, "John Hubbard" <jhubbard@nvidia.com>
Subject: Re: [PATCH v3 00/10] Allocation APIs
Date: Thu, 25 Apr 2024 17:36:20 +0200	[thread overview]
Message-ID: <Zip4dFpt8xhk7UBL@cassiopeiae> (raw)
In-Reply-To: <cbeae504-2752-4ef0-b103-e62fcf45ab93@redhat.com>

(adding folks from [1])

On Tue, Apr 23, 2024 at 05:43:08PM +0200, Danilo Krummrich wrote:
> Hi all,
> 
> On 3/28/24 02:35, Wedson Almeida Filho wrote:
> > From: Wedson Almeida Filho <walmeida@microsoft.com>
> > 
> > Revamp how we use the `alloc` crate.
> > 
> > We currently have a fork of the crate with changes to `Vec`; other
> > changes have been upstreamed (to the Rust project). This series removes
> > the fork and exposes all the functionality as extension traits.
> > 
> > Additionally, it also introduces allocation flag parameters to all
> > functions that may result in allocations (e.g., `Box::new`, `Arc::new`,
> > `Vec::push`, etc.) without the `try_` prefix -- the names are available
> > because we build `alloc` with `no_global_oom_handling`.
> > 
> > Lastly, the series also removes our reliance on the `allocator_api`
> > unstable feature.
> > 
> > Long term, we still want to make such functionality available in
> > upstream Rust, but this allows us to make progress now and reduces our
> > maintainance burden.
> > 
> > In summary:
> > 1. Removes `alloc` fork
> > 2. Removes use of `allocator_api` unstable feature
> > 3. Introduces flags (e.g., GFP_KERNEL, GFP_ATOMIC) when allocating
> 
> With that series, how do we implement alternative allocators, such as
> (k)vmalloc or DMA coherent?
> 
> For instance, I recently sketched up some firmware bindings we want to
> use in Nova providing
> 
> fn copy<A: core::alloc::Allocator>(&self, alloc: A) -> Result<Vec<u8, A>>
> [1]
> 
> making use of Vec::try_with_capacity_in(). How would I implement
> something similar now?

I want to follow up on this topic after also bringing it up in yesterday's
weekly Rust call.

In the call a few ideas were discussed, e.g. whether we could just re-enable the
allocator_api feature and try getting it stabilized.

With the introduction of alloc::Flags (gfp_t abstraction) allocator_api might
not be a viable choice anymore.

I think it would work for (k)vmalloc, where we could pass the page flags through
const generics for instance.

But I don't see how it could work with kmem_cache, where we can't just create a
new allocator instance when we want to change the page flags, but need to
support allocations with different page flags on the same allocator (same
kmem_cache) instance.

So, I think we have to create our own allocator trait / API.

Any other thoughts on that?

- Danilo

[1] https://lore.kernel.org/rust-for-linux/20240408094738.00005e59.zhiw@nvidia.com/

> 
> - Danilo
> 
> [1] https://gitlab.freedesktop.org/drm/nova/-/blob/topic/firmware/rust/kernel/firmware.rs?ref_type=heads#L63
> 
> > 
> > ---
> > 
> > Changes in v3:
> > - Rebased on top of the latest `rust-next` branch.
> > - Updated `krealloc_aligned` to use `Flags` instead of `bindings::gfp_t`.
> > - Added __GFP_ZERO to flags, as part of the previous change.
> > - Avoiding temporary stack value in `Box::new_uninit`.
> > - Implement `Box::new` using `Box::new_uninit` (so only one of them actually
> >    allocates).
> > - Added examples/tests to `VecExt` methods.
> > - Fixed bug in length in `extend_from_slice`
> > - Link to v2: https://lore.kernel.org/rust-for-linux/20240327023531.187880-1-wedsonaf@gmail.com/T/#t
> > 
> > Changes in v2:
> > - Updated description of `alloc` crate.
> > - Renamed vecext and boxext modules to vec_ext and box_ext.
> > - Added derive directive to `AllocError`.
> > - Updated safety comment in `BoxExt::new`.
> > - Updated `VecExt::push` and `VecExt::extend_from_slice` to use
> >    `spare_capacity_mut`
> > - Added directive to not compile `destructure` and `rebuild` when `test` or
> >    `testlib` are configured. Otherwise we have a warning because `push` and
> >    `extend_from_slice` don't use them anymore.
> > - Updated indentation in `Arc::new_uninit`
> > - Moved the removal of `TryReserveError` convesion to `Error` to patch 7, where
> >    usage of `TryReserveError` is actually removed.
> > - Link to v1: https://lore.kernel.org/rust-for-linux/20240325195418.166013-1-wedsonaf@gmail.com/T/#t
> > 
> > Wedson Almeida Filho (10):
> >    rust: kernel: move `allocator` module under `alloc`
> >    rust: alloc: introduce the `VecExt` trait
> >    kbuild: use the upstream `alloc` crate
> >    rust: alloc: remove our fork of the `alloc` crate
> >    rust: alloc: introduce allocation flags
> >    rust: alloc: introduce the `BoxExt` trait
> >    rust: alloc: update `VecExt` to take allocation flags
> >    rust: sync: update `Arc` and `UniqueArc` to take allocation flags
> >    rust: init: update `init` module to take allocation flags
> >    rust: kernel: remove usage of `allocator_api` unstable feature
> > 
> >   rust/Makefile                        |   16 +-
> >   rust/alloc/README.md                 |   36 -
> >   rust/alloc/alloc.rs                  |  452 ----
> >   rust/alloc/boxed.rs                  | 2463 -----------------
> >   rust/alloc/collections/mod.rs        |  160 --
> >   rust/alloc/lib.rs                    |  288 --
> >   rust/alloc/raw_vec.rs                |  611 -----
> >   rust/alloc/slice.rs                  |  890 -------
> >   rust/alloc/vec/drain.rs              |  255 --
> >   rust/alloc/vec/extract_if.rs         |  115 -
> >   rust/alloc/vec/into_iter.rs          |  454 ----
> >   rust/alloc/vec/is_zero.rs            |  204 --
> >   rust/alloc/vec/mod.rs                | 3683 --------------------------
> >   rust/alloc/vec/partial_eq.rs         |   49 -
> >   rust/alloc/vec/set_len_on_drop.rs    |   35 -
> >   rust/alloc/vec/spec_extend.rs        |  119 -
> >   rust/bindings/bindings_helper.h      |    3 +
> >   rust/kernel/alloc.rs                 |   74 +
> >   rust/kernel/{ => alloc}/allocator.rs |   17 +-
> >   rust/kernel/alloc/box_ext.rs         |   59 +
> >   rust/kernel/alloc/vec_ext.rs         |  176 ++
> >   rust/kernel/error.rs                 |   13 +-
> >   rust/kernel/init.rs                  |   57 +-
> >   rust/kernel/lib.rs                   |    5 +-
> >   rust/kernel/prelude.rs               |    2 +
> >   rust/kernel/str.rs                   |    6 +-
> >   rust/kernel/sync/arc.rs              |   50 +-
> >   rust/kernel/sync/condvar.rs          |    2 +-
> >   rust/kernel/sync/lock/mutex.rs       |    2 +-
> >   rust/kernel/sync/lock/spinlock.rs    |    2 +-
> >   rust/kernel/types.rs                 |    4 +-
> >   rust/kernel/workqueue.rs             |   14 +-
> >   samples/rust/rust_minimal.rs         |    6 +-
> >   samples/rust/rust_print.rs           |    4 +-
> >   scripts/generate_rust_analyzer.py    |    2 +-
> >   35 files changed, 405 insertions(+), 9923 deletions(-)
> >   delete mode 100644 rust/alloc/README.md
> >   delete mode 100644 rust/alloc/alloc.rs
> >   delete mode 100644 rust/alloc/boxed.rs
> >   delete mode 100644 rust/alloc/collections/mod.rs
> >   delete mode 100644 rust/alloc/lib.rs
> >   delete mode 100644 rust/alloc/raw_vec.rs
> >   delete mode 100644 rust/alloc/slice.rs
> >   delete mode 100644 rust/alloc/vec/drain.rs
> >   delete mode 100644 rust/alloc/vec/extract_if.rs
> >   delete mode 100644 rust/alloc/vec/into_iter.rs
> >   delete mode 100644 rust/alloc/vec/is_zero.rs
> >   delete mode 100644 rust/alloc/vec/mod.rs
> >   delete mode 100644 rust/alloc/vec/partial_eq.rs
> >   delete mode 100644 rust/alloc/vec/set_len_on_drop.rs
> >   delete mode 100644 rust/alloc/vec/spec_extend.rs
> >   create mode 100644 rust/kernel/alloc.rs
> >   rename rust/kernel/{ => alloc}/allocator.rs (86%)
> >   create mode 100644 rust/kernel/alloc/box_ext.rs
> >   create mode 100644 rust/kernel/alloc/vec_ext.rs
> > 
> > 
> > base-commit: 768409cff6cc89fe1194da880537a09857b6e4db


  reply	other threads:[~2024-04-25 15:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  1:35 [PATCH v3 00/10] Allocation APIs Wedson Almeida Filho
2024-03-28  1:35 ` [PATCH v3 01/10] rust: kernel: move `allocator` module under `alloc` Wedson Almeida Filho
2024-03-28  1:35 ` [PATCH v3 02/10] rust: alloc: introduce the `VecExt` trait Wedson Almeida Filho
2024-03-28  1:35 ` [PATCH v3 03/10] kbuild: use the upstream `alloc` crate Wedson Almeida Filho
2024-03-28  1:35 ` [PATCH v3 04/10] rust: alloc: remove our fork of the " Wedson Almeida Filho
2024-03-28  1:35 ` [PATCH v3 05/10] rust: alloc: introduce allocation flags Wedson Almeida Filho
2024-03-28  1:35 ` [PATCH v3 06/10] rust: alloc: introduce the `BoxExt` trait Wedson Almeida Filho
2024-03-29 17:59   ` Boqun Feng
2024-03-30  0:57     ` Wedson Almeida Filho
2024-03-30 13:35   ` Benno Lossin
2024-03-28  1:36 ` [PATCH v3 07/10] rust: alloc: update `VecExt` to take allocation flags Wedson Almeida Filho
2024-03-30 13:30   ` Benno Lossin
2024-03-28  1:36 ` [PATCH v3 08/10] rust: sync: update `Arc` and `UniqueArc` " Wedson Almeida Filho
2024-03-28  1:36 ` [PATCH v3 09/10] rust: init: update `init` module " Wedson Almeida Filho
2024-03-28  1:36 ` [PATCH v3 10/10] rust: kernel: remove usage of `allocator_api` unstable feature Wedson Almeida Filho
2024-03-29 18:25 ` [PATCH v3 00/10] Allocation APIs Boqun Feng
2024-03-29 23:23   ` Boqun Feng
2024-03-30  0:54   ` Wedson Almeida Filho
2024-04-08  6:47 ` Zhi Wang
2024-05-01 22:06   ` Miguel Ojeda
2024-04-16 21:03 ` Miguel Ojeda
2024-04-23 15:43 ` Danilo Krummrich
2024-04-25 15:36   ` Danilo Krummrich [this message]
2024-04-25 16:09     ` Benno Lossin
2024-04-25 18:03       ` Zhi Wang
2024-04-25 18:42       ` Danilo Krummrich
2024-04-25 20:52         ` Benno Lossin
2024-04-25 22:57           ` Danilo Krummrich
2024-04-26  6:32             ` Benno Lossin
2024-04-26 10:31               ` Danilo Krummrich
2024-04-29 20:14                 ` 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=Zip4dFpt8xhk7UBL@cassiopeiae \
    --to=dakr@redhat.com \
    --cc=a.hindborg@samsung.com \
    --cc=acurrid@nvidia.com \
    --cc=ajanulgu@redhat.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=cjia@nvidia.com \
    --cc=gary@garyguo.net \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=walmeida@microsoft.com \
    --cc=wedsonaf@gmail.com \
    --cc=zhiw@nvidia.com \
    /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).