[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87cy5v3w5m.fsf@linux.intel.com>
Date: Thu, 06 Nov 2025 09:31:33 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Ian Rogers <irogers@...gle.com>
Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>, Namhyung Kim
<namhyung@...nel.org>, Alexander Shishkin
<alexander.shishkin@...ux.intel.com>, Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>, "Dr. David Alan Gilbert"
<linux@...blig.org>, Yang Li <yang.lee@...ux.alibaba.com>, James Clark
<james.clark@...aro.org>, Thomas Falcon <thomas.falcon@...el.com>,
Thomas Richter <tmricht@...ux.ibm.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org, Dapeng
Mi <dapeng1.mi@...ux.intel.com>
Subject: Re: [PATCH v3 9/9] perf stat: Add no-affinity flag
Ian Rogers <irogers@...gle.com> writes:
> Add flag that disables affinity behavior. Using sched_setaffinity to
> place a perf thread on a CPU can avoid certain interprocessor
> interrupts but may introduce a delay due to the scheduling,
> particularly on loaded machines. Add a command line option to disable
> the behavior. This behavior is less present in other tools like `perf
> record`, as it uses a ring buffer and doesn't make repeated system
> calls.
I would rather use a real time scheduling policy instead if you see starvation.
That would still get the batching efficiency.
If it's done it would be better in .perfconfig instead of adding ever
more obscure command line options.
-Andi
Powered by blists - more mailing lists