[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_FKugtgoN0l6JNm@casper.infradead.org>
Date: Sat, 5 Apr 2025 16:22:34 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Andrew Ballance <andrewjballance@...il.com>
Cc: Liam.Howlett@...cle.com, ojeda@...nel.org, alex.gaynor@...il.com,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
benno.lossin@...ton.me, a.hindborg@...nel.org, aliceryhl@...gle.com,
tmgross@...ch.edu, dakr@...nel.org, akpm@...ux-foundation.org,
gregkh@...uxfoundation.org, wedsonaf@...il.com, brauner@...nel.org,
dingxiangfei2009@...il.com, linux-kernel@...r.kernel.org,
maple-tree@...ts.infradead.org, linux-mm@...ck.org,
rust-for-linux@...r.kernel.org
Subject: Re: [RFC PATCH 1/2] maple_tree: add __mtree_insert_range function
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.
Powered by blists - more mailing lists