From: sashiko-bot@kernel.org
To: "Arnaldo Carvalho de Melo" <acme@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v9 9/9] perf test: Add false_sharing workload exhibiting cross-CPU false sharing
Date: Sun, 04 Oct 2026 06:11:35 +0000 [thread overview]
Message-ID: <20261004061137.81A9D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261004060457.3353-10-acme@kernel.org>
> From: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Add a 'perf test -w false_sharing' workload that hammers one shared
> struct from several CPUs, shaped as a TCP connection: a read-mostly
> identity (five-tuple) shares a cacheline with per-packet rx counters
> (the false-sharing line), a second line has packet-path private tx and
> congestion control counters, and a third the connection config.
>
> The packet path runs in the main thread and up to four lookup threads
> sum the five-tuple and pull the config, reading one volatile shared
> instance directly so the accesses are PC-relative and resolvable by the
> data type profiler.
>
> Data type profiling of the workload with cacheline info:
>
> [ ... ]
> 0.00% 0.01% struct folio +0x34 (_refcount.counter)
> 0.00% 0.00% struct folio +0x18 (mapping)
>
> Assisted-by: LLM
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261004060457.3353-1-acme@kernel.org?part=9
prev parent reply other threads:[~2026-10-04 6:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 6:04 [PATCH v9 0/9] perf tools: Add progress diagnostics and a false-sharing workload Arnaldo Carvalho de Melo
2026-10-04 6:04 ` [PATCH v9 1/9] perf config: Move perf_config__set_variable() to util/config.c Arnaldo Carvalho de Melo
2026-10-04 6:16 ` sashiko-bot
2026-10-04 6:04 ` [PATCH v9 2/9] perf config: Make perf_etc_perfconfig() never return NULL Arnaldo Carvalho de Melo
2026-10-04 6:11 ` sashiko-bot
2026-10-04 6:04 ` [PATCH v9 3/9] perf mutex: Add DEFINE_MUTEX() static initializer Arnaldo Carvalho de Melo
2026-10-04 6:10 ` sashiko-bot
2026-10-04 6:04 ` [PATCH v9 4/9] perf mutex: Add DO_ONCE() for one-time initialization Arnaldo Carvalho de Melo
2026-10-04 6:10 ` sashiko-bot
2026-10-04 6:04 ` [PATCH v9 5/9] perf config: Serialize config file access with a mutex Arnaldo Carvalho de Melo
2026-10-04 6:14 ` sashiko-bot
2026-10-04 6:04 ` [PATCH v9 6/9] perf report: Add --progress option Arnaldo Carvalho de Melo
2026-10-04 6:12 ` sashiko-bot
2026-10-04 6:04 ` [PATCH v9 7/9] perf report: Add --no-progress option Arnaldo Carvalho de Melo
2026-10-04 6:11 ` sashiko-bot
2026-10-04 6:04 ` [PATCH v9 8/9] perf scripts: Add perf-stuck, to tell where a running perf is stuck Arnaldo Carvalho de Melo
2026-10-04 6:17 ` sashiko-bot
2026-10-04 6:04 ` [PATCH v9 9/9] perf test: Add false_sharing workload exhibiting cross-CPU false sharing Arnaldo Carvalho de Melo
2026-10-04 6:11 ` sashiko-bot [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=20261004061137.81A9D1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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