From: Matthew Wilcox <willy@infradead.org>
To: Andrew Ballance <andrewjballance@gmail.com>
Cc: Liam.Howlett@oracle.com, 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, dakr@kernel.org,
akpm@linux-foundation.org, gregkh@linuxfoundation.org,
wedsonaf@gmail.com, brauner@kernel.org,
dingxiangfei2009@gmail.com, linux-kernel@vger.kernel.org,
maple-tree@lists.infradead.org, linux-mm@kvack.org,
rust-for-linux@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] maple_tree: add __mtree_insert_range function
Date: Sat, 5 Apr 2025 16:22:34 +0100 [thread overview]
Message-ID: <Z_FKugtgoN0l6JNm@casper.infradead.org> (raw)
In-Reply-To: <20250405060154.1550858-2-andrewjballance@gmail.com>
On Sat, Apr 05, 2025 at 01:01:53AM -0500, Andrew Ballance wrote:
> adds the __mtree_insert_range which is identical to mtree_insert_range
> but does not aquire ma_lock.
> This function is needed for the rust bindings for maple trees because
> the locking is handled on the rust side.
No.
The support for external locking is a TEMPORARY HACK. I've talked
before about why this is and don't feel like explaining it again.
next prev parent reply other threads:[~2025-04-05 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 6:01 [RFC PATCH 0/2] rust: add support for maple trees Andrew Ballance
2025-04-05 6:01 ` [RFC PATCH 1/2] maple_tree: add __mtree_insert_range function Andrew Ballance
2025-04-05 15:22 ` Matthew Wilcox [this message]
2025-04-05 18:38 ` Boqun Feng
2025-04-06 9:30 ` Andrew Ballance
2025-04-05 6:01 ` [RFC PATCH 2/2] rust: add maple tree abstractions Andrew Ballance
2025-04-05 15:23 ` Miguel Ojeda
2025-04-07 13:59 ` Liam R. Howlett
2025-04-07 20:02 ` Andrew Ballance
2025-04-08 1:36 ` Liam R. Howlett
2025-04-14 18:27 ` 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=Z_FKugtgoN0l6JNm@casper.infradead.org \
--to=willy@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--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=brauner@kernel.org \
--cc=dakr@kernel.org \
--cc=dingxiangfei2009@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wedsonaf@gmail.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