From: "Danilo Krummrich" <dakr@kernel.org>
To: "Shivam Kalra" <shivamkalra98@zohomail.in>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] rust: alloc: add Vec shrinking methods
Date: Wed, 11 Feb 2026 09:57:10 +0100 [thread overview]
Message-ID: <DGC0AJ9L0ZP1.20IV8O6FT1PTD@kernel.org> (raw)
In-Reply-To: <af90cbe5-dcfa-46da-83b3-e903134c7f93@zohomail.in>
On Wed Feb 11, 2026 at 9:41 AM CET, Shivam Kalra wrote:
> Thanks Alice. I'll go with the standalone helper function approach
> with separate impl blocks for Vec<T, Vmalloc> and Vec<T, KVmalloc>.
If it's only needed for KVmalloc, which apparently is the case, let's just add
it for KVVec only.
Also, please make sure to add a TODO comment mentioning why this workaround
exists and what it should be replaced with, i.e. a generic shrink_to() that
calls into A::realloc().
next prev parent reply other threads:[~2026-02-11 8:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 11:32 [PATCH v3 0/4] rust: alloc: add Vec shrinking methods Shivam Kalra
2026-02-07 11:32 ` Shivam Kalra via B4 Relay
2026-02-07 11:32 ` [PATCH v3 1/4] rust: alloc: introduce Shrinkable trait Shivam Kalra
2026-02-07 11:32 ` Shivam Kalra via B4 Relay
2026-02-07 11:32 ` [PATCH v3 2/4] rust: kvec: implement shrink_to and shrink_to_fit for Vec Shivam Kalra
2026-02-07 11:32 ` Shivam Kalra via B4 Relay
2026-02-07 17:23 ` Danilo Krummrich
2026-02-08 16:11 ` Shivam Kalra
2026-02-07 11:32 ` [PATCH v3 3/4] rust: alloc: add KUnit tests for Vec shrink operations Shivam Kalra
2026-02-07 11:32 ` Shivam Kalra via B4 Relay
2026-02-07 11:32 ` [PATCH v3 4/4] rust: binder: shrink all_procs when deregistering processes Shivam Kalra
2026-02-07 11:32 ` Shivam Kalra via B4 Relay
2026-02-09 13:54 ` Alice Ryhl
2026-02-10 11:47 ` Shivam Kalra
2026-02-10 13:38 ` [PATCH v3 0/4] rust: alloc: add Vec shrinking methods Shivam Kalra
2026-02-10 13:57 ` Alice Ryhl
2026-02-10 15:05 ` Danilo Krummrich
2026-02-10 17:42 ` Shivam Kalra
2026-02-10 20:05 ` Alice Ryhl
2026-02-10 20:43 ` Danilo Krummrich
2026-02-10 20:53 ` Danilo Krummrich
2026-02-10 20:56 ` Danilo Krummrich
2026-02-10 20:58 ` Alice Ryhl
2026-02-10 21:11 ` Danilo Krummrich
2026-02-11 1:08 ` Shivam Kalra
2026-02-11 6:51 ` Alice Ryhl
2026-02-11 8:41 ` Shivam Kalra
2026-02-11 8:57 ` Danilo Krummrich [this message]
2026-02-11 9:35 ` Shivam Kalra
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=DGC0AJ9L0ZP1.20IV8O6FT1PTD@kernel.org \
--to=dakr@kernel.org \
--cc=aliceryhl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=shivamkalra98@zohomail.in \
/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.