From: Steven Rostedt <rostedt@goodmis.org>
To: Yongliang Gao <leonylgao@gmail.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
bigeasy@linutronix.de, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, frankjpliu@tencent.com,
Yongliang Gao <leonylgao@tencent.com>,
Huang Cun <cunhuang@tencent.com>
Subject: Re: [PATCH v2] trace/pid_list: optimize pid_list->lock contention
Date: Wed, 12 Nov 2025 13:29:50 -0500 [thread overview]
Message-ID: <20251112132950.60a165f9@gandalf.local.home> (raw)
In-Reply-To: <20251112181456.473864-1-leonylgao@gmail.com>
On Thu, 13 Nov 2025 02:14:56 +0800
Yongliang Gao <leonylgao@gmail.com> wrote:
> @@ -271,7 +277,6 @@ int trace_pid_list_next(struct trace_pid_list *pid_list, unsigned int pid,
> {
> union upper_chunk *upper_chunk;
> union lower_chunk *lower_chunk;
> - unsigned long flags;
> unsigned int upper1;
> unsigned int upper2;
> unsigned int lower;
> @@ -282,27 +287,44 @@ int trace_pid_list_next(struct trace_pid_list *pid_list, unsigned int pid,
> if (pid_split(pid, &upper1, &upper2, &lower) < 0)
> return -EINVAL;
>
> - raw_spin_lock_irqsave(&pid_list->lock, flags);
> - for (; upper1 <= UPPER_MASK; upper1++, upper2 = 0) {
> - upper_chunk = pid_list->upper[upper1];
> + do {
> + unsigned int start_upper1 = upper1;
> + unsigned int start_upper2 = upper2;
> + unsigned int start_lower = lower;
> + unsigned int seq;
>
> - if (!upper_chunk)
> - continue;
> + seq = read_seqcount_begin(&pid_list->seqcount);
>
> - for (; upper2 <= UPPER_MASK; upper2++, lower = 0) {
> - lower_chunk = upper_chunk->data[upper2];
> - if (!lower_chunk)
> + for (; upper1 <= UPPER_MASK; upper1++, upper2 = 0) {
> + upper_chunk = pid_list->upper[upper1];
> +
> + if (!upper_chunk)
> continue;
>
> - lower = find_next_bit(lower_chunk->data, LOWER_MAX,
> - lower);
> - if (lower < LOWER_MAX)
> - goto found;
> + for (; upper2 <= UPPER_MASK; upper2++, lower = 0) {
> + lower_chunk = upper_chunk->data[upper2];
> + if (!lower_chunk)
> + continue;
> +
> + lower = find_next_bit(lower_chunk->data, LOWER_MAX,
> + lower);
> + if (lower < LOWER_MAX)
> + goto found;
> + }
> }
> - }
>
> + upper1 = UPPER_MASK + 1; /* Mark as not found */
> found:
> - raw_spin_unlock_irqrestore(&pid_list->lock, flags);
> + if (read_seqcount_retry(&pid_list->seqcount, seq)) {
> + /* Retry if write happened during read */
> + upper1 = start_upper1;
> + upper2 = start_upper2;
> + lower = start_lower;
> + continue;
> + }
> + break;
> + } while (1);
> +
> if (upper1 > UPPER_MASK)
> return -1;
Honestly, I wouldn't modify trace_pid_list_next(). It is simply used for
printing of the pids in /sys/kernel/tracing/set_*_pid files. It's not a
critical section, and it shouldn't affect scheduling like
trace_pid_list_is_set() does.
Just keep it taking the raw spin lock, as that will keep it from being
modified by the writers. It also keeps the code from becoming more complex.
-- Steve
prev parent reply other threads:[~2025-11-12 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 18:14 [PATCH v2] trace/pid_list: optimize pid_list->lock contention Yongliang Gao
2025-11-12 18:29 ` Steven Rostedt [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=20251112132950.60a165f9@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=cunhuang@tencent.com \
--cc=frankjpliu@tencent.com \
--cc=leonylgao@gmail.com \
--cc=leonylgao@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
/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