From: sashiko-bot@kernel.org
To: "Changbin Du" <changbin.du@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v3] perf bench: Add atomic operations benchmark
Date: Thu, 08 Oct 2026 04:18:43 +0000 [thread overview]
Message-ID: <sashiko-outbox-163608@kernel.org> (raw)
In-Reply-To: <20261008041123.1970315-1-changbin.du@gmail.com>
> Add a new 'atomic' collection to perf bench for benchmarking
> atomic read-modify-write operations with multi-threaded
> contention testing. It provides two subcommands:
>
> - atomic cas: contended compare-and-swap operations
> (__atomic_compare_exchange_n)
> - atomic inc: contended fetch-add operations (__atomic_fetch_add)
>
> Both support configurable thread count and iteration count to
> measure atomic contention effects.
>
> Why this benchmark is needed:
> - Atomic read-modify-write operations are fundamental to lock-free
> algorithms and data structures. Understanding their performance
> characteristics under contention is critical for designing
> [ ... ]
> - Per-thread times: fastest/slowest/avg thread completion time
> - Per-thread throughput: per-thread ops/sec (shows scheduling imbalance)
>
> Assisted-by: opencode:DeepSeek-V4-Pro
> Signed-off-by: Changbin Du <changbin.du@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008041123.1970315-1-changbin.du@gmail.com?part=1
next prev parent reply other threads:[~2026-10-08 4:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 4:11 [PATCH v3] perf bench: Add atomic operations benchmark Changbin Du
2026-10-08 4:18 ` sashiko-bot [this message]
2026-10-12 19:31 ` Namhyung Kim
2026-10-13 7:48 ` Changbin Du
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=sashiko-outbox-163608@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=changbin.du@gmail.com \
--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 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.