From: "Rafael Passos" <rafael@rcpassos.me>
To: "Alice Ryhl" <aliceryhl@google.com>,
"Greg KH" <gregkh@linuxfoundation.org>,
<rust-for-linux@vger.kernel.org>
Cc: "Rafael Passos" <rafael@rcpassos.me>, <arve@android.com>,
<tkjos@android.com>, "Christian Brauner" <brauner@kernel.org>,
<cmllamas@google.com>
Subject: Re: [PATCH] rust_binder: speed up get_node_debug_info using lower_bound iter
Date: Tue, 28 Jul 2026 17:59:45 -0300 [thread overview]
Message-ID: <DKAI8RPYX25S.ENUL6EQIROC9@rcpassos.me> (raw)
In-Reply-To: <CAH5fLgh6jyOOW=nHatA=wOc0fjwk7k5VUJgtk0HNz4zdUScN_g@mail.gmail.com>
Hi Greg and Alice,
On Tue, Jul 28, 2026 at 6:54 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Mon, Jul 27, 2026 at 10:03:21PM -0300, Rafael Passos wrote:
> > Finding the next node in the RBTree can be done more efficiently using
> > the cursor_lower_bound, as it reduces cost from O(n) to O(log n).
> >
> > Link: https://github.com/Rust-for-Linux/linux/issues/1249
> > Suggested-by: Alice Ryhl <aliceryhl@google.com>
> > Signed-off-by: Rafael Passos <rafael@rcpassos.me>
> > ---
>
> Does this actually speed anything up in the binder benchmark tools?
I want to run these benchmarks! I searched and this "Performance testing"
page [1] in android docs was the closest match. Am I correct?
I'm learning more about binder, watching the talks, reading posts etc.
It's really interesting. Any recommendations on how to run in VMs and in
Hardware ? Is the Cuttlefish emulator the recommended setup ?
On Tue Jul 28, 2026 at 2:47 AM -03, Alice Ryhl wrote:
> I don't think I got the email for this patch?
Sorry for the confusion. I had to send it twice because I missed the
list in the first email. The second send is in lore [2].
I will send a v2 with suggestions. This message might reach both
threads (if I manipulated the headers correctly ;P)
[1] Android Performance testing https://source.android.com/docs/core/tests/vts/performance
[2] patch resend https://lore.kernel.org/rust-for-linux/amhHBxSfuat8WZ8R@google.com/T/#t
Thanks,
Rafael Passos
next parent reply other threads:[~2026-07-28 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260728010717.3075755-1-rafael@rcpassos.me>
[not found] ` <2026072804-sedation-bogged-6f89@gregkh>
[not found] ` <CAH5fLgh6jyOOW=nHatA=wOc0fjwk7k5VUJgtk0HNz4zdUScN_g@mail.gmail.com>
2026-07-28 20:59 ` Rafael Passos [this message]
2026-07-28 1:22 [PATCH] rust_binder: speed up get_node_debug_info using lower_bound iter Rafael Passos
2026-07-28 5:48 ` Onur Özkan
2026-07-28 6:07 ` Alice Ryhl
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=DKAI8RPYX25S.ENUL6EQIROC9@rcpassos.me \
--to=rafael@rcpassos.me \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tkjos@android.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