From: Alice Ryhl <aliceryhl@google.com>
To: nenkov2004@gmail.com
Cc: rust-for-linux@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Miguel Ojeda <ojeda@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: binder: Use lower bound for node debug lookup
Date: Mon, 31 Aug 2026 12:30:09 +0000 [thread overview]
Message-ID: <apVz0SFGOLbhUc2O@google.com> (raw)
In-Reply-To: <20260831052635.42417-1-nenkov2004@gmail.com>
On Mon, Aug 31, 2026 at 07:26:35AM +0200, nenkov2004@gmail.com wrote:
> From: ChrisX101010 <nenkov2004@gmail.com>
>
> The Binder node debug lookup currently walks the process node RBTree
> from the beginning until it finds the first node pointer greater than
> the requested pointer.
>
> Use RBTree::cursor_lower_bound() to start the lookup at the relevant
> tree position instead. When the lower-bound key is equal to the
> requested pointer, inspect the next node to preserve the existing
> strictly-greater-than semantics.
>
> This changes the tree lookup from a linear scan to an O(log n) search
> without changing the returned node semantics.
>
> Suggested-by: Alice Ryhl <aliceryhl@google.com>
> Link: https://github.com/Rust-for-Linux/linux/issues/1249
> Signed-off-by: ChrisX101010 <nenkov2004@gmail.com>
This is a duplicate:
https://lore.kernel.org/all/20260814215145.2050599-1-rafael@rcpassos.me/
prev parent reply other threads:[~2026-08-31 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 5:26 [PATCH] rust: binder: Use lower bound for node debug lookup nenkov2004
2026-08-31 5:39 ` Greg Kroah-Hartman
2026-08-31 5:49 ` [PATCH v2] " nenkov2004
2026-08-31 12:30 ` Alice Ryhl [this message]
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=apVz0SFGOLbhUc2O@google.com \
--to=aliceryhl@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nenkov2004@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
/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.