From: Danilo Krummrich <dakr@kernel.org>
To: Andrew Ballance <andrewjballance@gmail.com>
Cc: airlied@gmail.com, simona@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, corbet@lwn.net, ojeda@kernel.org,
alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, benno.lossin@proton.me,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
acourbot@nvidia.com, nouveau@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2 1/3] rust: alloc: add Vec::truncate method
Date: Sun, 16 Mar 2025 20:19:54 +0100 [thread overview]
Message-ID: <Z9ckWiW7X0hX5Wvt@pollux> (raw)
In-Reply-To: <20250316111644.154602-2-andrewjballance@gmail.com>
On Sun, Mar 16, 2025 at 06:16:42AM -0500, Andrew Ballance wrote:
> implement the equivalent to the std's Vec::truncate
> on the kernel's Vec type.
>
> Signed-off-by: Andrew Ballance <andrewjballance@gmail.com>
> ---
> rust/kernel/alloc/kvec.rs | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/rust/kernel/alloc/kvec.rs b/rust/kernel/alloc/kvec.rs
> index ae9d072741ce..18bcc59f0b38 100644
> --- a/rust/kernel/alloc/kvec.rs
> +++ b/rust/kernel/alloc/kvec.rs
> @@ -452,6 +452,42 @@ pub fn reserve(&mut self, additional: usize, flags: Flags) -> Result<(), AllocEr
>
> Ok(())
> }
> +
> + /// Shortens the vector, setting the length to `len` and drops the removed values.
> + /// If `len` is greater than or equal to the current length, this does nothing.
> + ///
> + /// This has no effect on the capacity and will not allocate.
> + /// # Examples
> + ///
> + /// ```
> + /// let mut v = kernel::kvec![1, 2, 3]?;
> + /// v.truncate(1);
> + /// assert_eq!(v.len(), 1);
> + /// assert_eq!(&v, &[1]);
> + ///
> + /// # Ok::<(), Error>(())
> + /// ```
> + pub fn truncate(&mut self, len: usize) {
> + if len >= self.len() {
> + return;
> + }
> +
> + let drop_range = len..self.len();
> +
> + // SAFETY: `drop_range` is a subrange of `[0, len)` by the bounds check above.
> + let ptr: *mut [T] = unsafe { self.get_unchecked_mut(drop_range) };
> +
> + // SAFETY:
> + // - this will always shrink the vector because of the above bounds check
> + // - [`new_len`, `self.len`) will be dropped through the call to `drop_in_place` below
We've just figured out that this part is not needed after all, sorry for the
inconvenience. No need to resend for this though, I can remove this line when
applying the patch.
> + unsafe { self.set_len(len) };
> +
> + // SAFETY:
> + // - the dropped values are valid `T`s by the type invariant
> + // - we are allowed to invalidate [`new_len`, `old_len`) because we just changed the
> + // len, therefore we have exclusive access to [`new_len`, `old_len`)
> + unsafe { ptr::drop_in_place(ptr) };
> + }
> }
>
> impl<T: Clone, A: Allocator> Vec<T, A> {
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-03-16 19:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 11:16 [PATCH v2 0/3] rust: alloc: add Vec::resize and Vec::truncate Andrew Ballance
2025-03-16 11:16 ` [PATCH v2 1/3] rust: alloc: add Vec::truncate method Andrew Ballance
2025-03-16 19:19 ` Danilo Krummrich [this message]
2025-03-16 11:16 ` [PATCH v2 2/3] rust: alloc: add Vec::resize method Andrew Ballance
2025-03-16 18:01 ` Benno Lossin
2025-03-18 20:12 ` Tamir Duberstein
2025-03-19 0:50 ` Benno Lossin
2025-03-19 13:42 ` Tamir Duberstein
2025-03-19 14:34 ` Benno Lossin
2025-03-19 15:58 ` Tamir Duberstein
2025-03-19 16:06 ` Miguel Ojeda
2025-03-19 16:13 ` Tamir Duberstein
2025-03-19 16:43 ` Miguel Ojeda
2025-03-19 17:22 ` Tamir Duberstein
2025-03-16 11:16 ` [PATCH v2 3/3] gpu: nova-core: remove completed Vec extentions from task list Andrew Ballance
2025-04-07 13:07 ` [PATCH v2 0/3] rust: alloc: add Vec::resize and Vec::truncate 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=Z9ckWiW7X0hX5Wvt@pollux \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=andrewjballance@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=tzimmermann@suse.de \
/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.