[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87qzvz9f55.fsf@yellow.woof>
Date: Mon, 22 Sep 2025 08:26:30 +0200
From: Nam Cao <namcao@...utronix.de>
To: Mateusz Guzik <mjguzik@...il.com>, Khazhy Kumykov <khazhy@...omium.org>
Cc: Alexander Viro <viro@...iv.linux.org.uk>, Christian Brauner
<brauner@...nel.org>, Jan Kara <jack@...e.cz>, Shuah Khan
<shuah@...nel.org>, Davidlohr Bueso <dave@...olabs.net>, Soheil Hassas
Yeganeh <soheil@...gle.com>, Willem de Bruijn <willemb@...gle.com>, Eric
Dumazet <edumazet@...gle.com>, Jens Axboe <axboe@...nel.dk>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 2/2] eventpoll: Fix epoll_wait() report false negative
Mateusz Guzik <mjguzik@...il.com> writes:
> a sequence counter around shenanigans will sort it out, but I don't
> know if it is worth it and don't really want to investigate myself.
The original commit did mention "1% CPU/RPC reduction in RPC benchmarks".
I'm not sure what "RPC" stands for and which benchmark it is. But if it
is really important, we must have heard by now.
Nam
Powered by blists - more mailing lists