All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "trieu2.huynh" <trieu2.huynh@lge.corp-partner.google.com>
Cc: arve@android.com, tkjos@android.com, brauner@kernel.org,
	cmllamas@google.com, aliceryhl@google.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drivers: android: binder: implement CTABS heuristic
Date: Wed, 15 Jul 2026 07:55:17 +0200	[thread overview]
Message-ID: <2026071500-smooth-cross-fd3a@gregkh> (raw)
In-Reply-To: <20260714183553.39773-2-trieu2.huynh@lge.corp-partner.google.com>

On Wed, Jul 15, 2026 at 03:35:51AM +0900, trieu2.huynh wrote:
> Introduce Cluster/Topology-Aware Binder Selection (CTABS) to optimize
> IPC transaction dispatching.
> 
> On asymmetric multi-cluster ARM64 architectures (e.g., big.LITTLE), the
> default binder thread selection algorithm is topology-blind. This leads
> to frequent cross-cluster thread wakeups, resulting in severe CPU cache
> misses, interconnect bottlenecks, and unnecessary cache ping-pongs.
> 
> To mitigate this latency penalty, CTABS evaluates idle waiting threads
> based on their last-executed CPU ID and prioritizing them as follows:
> 
> (*) Immediate Selection: Favors threads whose last-executed CPU matches
>     the caller's CPU exactly, exiting the selection loop early to ensure
>     optimal L1/L2 cache locality.
> (*) Cluster Match: Selects threads that ran on the same CPU cluster as
>     the caller, maximizing local cache reuse.
> (*) Cross-Cluster: Falls back to any available thread across different
>     clusters if no local affinity is found.
> 
> This topology prioritization maximizes CPU cache reuse, minimizes inter-
> cluster snooping overhead, and significantly reduces overall transaction
> turnaround latency on modern multi-cluster SoCs.
> 
> Signed-off-by: trieu2.huynh <trieu2.huynh@lge.corp-partner.google.com>

We need a real name here, and a real email address, not a
partner.google.com one.

thanks,

greg k-h

  reply	other threads:[~2026-07-15  5:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 18:35 [PATCH 0/2] drivers: android: binder: Introduce Cluster Aware Thread Selection trieu2.huynh
2026-07-14 18:35 ` [PATCH 1/2] drivers: android: binder: implement CTABS heuristic trieu2.huynh
2026-07-15  5:55   ` Greg KH [this message]
2026-07-15 15:01     ` Trieu Huynh
2026-07-14 18:35 ` [PATCH 2/2] drivers: android: binder: add preferred CPU wake-up nudge for waiting threads trieu2.huynh
2026-07-15  9:17 ` [PATCH 0/2] drivers: android: binder: Introduce Cluster Aware Thread Selection Alice Ryhl
2026-07-15 15:38   ` Trieu Huynh

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=2026071500-smooth-cross-fd3a@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=cmllamas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tkjos@android.com \
    --cc=trieu2.huynh@lge.corp-partner.google.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 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.