From: Thomas Gleixner <tglx@kernel.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: Dmitry Ilvokhin <d@ilvokhin.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun@kernel.org>, Dmitry Vyukov <dvyukov@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH] rseq: defer time slice extension yield for sys_futex_wakey
Date: Mon, 07 Sep 2026 18:09:11 +0200 [thread overview]
Message-ID: <87fqzl2gd4.ffs@fw13> (raw)
In-Reply-To: <ap66R7QTdVyMqcG9@google.com>
On Mon, Sep 07 2026 at 13:21, Alice Ryhl wrote:
> On Sat, Sep 05, 2026 at 10:01:59PM +0200, Thomas Gleixner wrote:
>> What is the actual problem you are trying to solve?
>
> Basically in Tokio we have a bunch of critical regions that look like
> this:
>
> mutex_lock();
> list_add_tail(&my_list, new_item);
> mutex_unlock();
>
> and this:
>
> mutex_lock();
> next_job = list_first_entry(&my_list);
> list_del(&next_job);
> mutex_unlock();
>
> except in Rust.
>
> People are reporting bugs to me saying that this particular list in
> Tokio is causing significant contention for real-world workloads in
> production. The context here is backend/web servers.
>
> Thus, I am looking at various solutions to improving contention here.
Have you looked at lockless lists or queues? The above use case looks
more like a queue than a list. I'm sure there is some Rust
implementation by now.
Thanks,
tglx
prev parent reply other threads:[~2026-09-07 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 12:57 [PATCH] rseq: defer time slice extension yield for sys_futex_wake Alice Ryhl
2026-08-31 13:45 ` Mathieu Desnoyers
2026-08-31 14:12 ` Alice Ryhl
2026-09-01 11:49 ` Dmitry Ilvokhin
2026-09-01 20:27 ` Alice Ryhl
2026-09-04 5:21 ` Thomas Gleixner
2026-09-04 13:53 ` [PATCH] rseq: defer time slice extension yield for sys_futex_wakey Dmitry Ilvokhin
2026-09-05 20:01 ` Thomas Gleixner
2026-09-07 13:21 ` Alice Ryhl
2026-09-07 16:09 ` Thomas Gleixner [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=87fqzl2gd4.ffs@fw13 \
--to=tglx@kernel.org \
--cc=aliceryhl@google.com \
--cc=boqun@kernel.org \
--cc=corbet@lwn.net \
--cc=d@ilvokhin.com \
--cc=dvyukov@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®