[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250407161557.bYYnmJSr@linutronix.de>
Date: Mon, 7 Apr 2025 18:15:57 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Shrikanth Hegde <sshegde@...ux.ibm.com>
Cc: André Almeida <andrealmeid@...lia.com>,
Darren Hart <dvhart@...radead.org>,
Davidlohr Bueso <dave@...olabs.net>, Ingo Molnar <mingo@...hat.com>,
Juri Lelli <juri.lelli@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Valentin Schneider <vschneid@...hat.com>,
Waiman Long <longman@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v10 00/21] futex: Add support task local hash maps,
FUTEX2_NUMA and FUTEX2_MPOL
On 2025-03-18 18:54:22 [+0530], Shrikanth Hegde wrote:
> I ran "perf bench futex all" as is. No change has been made to perf.
…
I just posted v11
https://lore.kernel.org/all/20250407155742.968816-1-bigeasy@linutronix.de/
this series extends "perf bench futex" with
- -b switch to specify number of buckets to use. Default is auto-scale,
0 is global hash, everything is the number of buckets.
- The used buckets are displayed after the run
- -I switches freezes the used buckets so the get/ put can be avoided.
This brings the invocations/sec back to where it was.
If you use the "all" instead of "hash" then the arguments are skipped.
I did not wire up the MPOL part. IMHO in order to make sense, the memory
allocation should based on the NUMA node and then the OP itself could be
based on the NUMA node.
Sebastian
Powered by blists - more mailing lists