From: Peter Zijlstra <peterz@infradead.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Waiman Long <longman@redhat.com>,
Shakeel Butt <shakeelb@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Boqun Feng <boqun.feng@gmail.com>,
Will Deacon <will@kernel.org>, Roman Penyaev <rpenyaev@suse.de>
Subject: Re: [PATCH] locking/rwlocks: do not starve writers
Date: Fri, 17 Jun 2022 21:04:08 +0200 [thread overview]
Message-ID: <YqzQKER4JRoudTJE@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CANn89iLxX_bqD8PvAkZXGWzKBKYxB3qaqQjxxdmoG91PfmvRnA@mail.gmail.com>
On Fri, Jun 17, 2022 at 07:45:14PM +0200, Eric Dumazet wrote:
> Were rwlocks always unfair, and we have been lucky ?
Yes.
next prev parent reply other threads:[~2022-06-17 19:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 9:10 [PATCH] locking/rwlocks: do not starve writers Eric Dumazet
2022-06-17 12:07 ` Peter Zijlstra
2022-06-17 14:43 ` Waiman Long
2022-06-17 14:57 ` Shakeel Butt
2022-06-17 15:00 ` Waiman Long
2022-06-17 15:24 ` Eric Dumazet
2022-06-17 15:56 ` Peter Zijlstra
2022-06-17 17:41 ` Waiman Long
2022-06-17 17:45 ` Eric Dumazet
2022-06-17 18:57 ` Waiman Long
2022-06-17 19:04 ` Peter Zijlstra [this message]
2022-06-17 19:10 ` Eric Dumazet
2022-06-17 19:19 ` Linus Torvalds
2022-06-17 19:25 ` Eric Dumazet
2022-06-17 19:34 ` Linus Torvalds
2022-06-17 19:39 ` Eric Dumazet
2022-06-17 19:48 ` Linus Torvalds
2022-06-20 7:25 ` Peter Zijlstra
2022-06-21 16:55 ` Eric W. Biederman
2022-06-17 21:58 ` David Laight
2022-06-17 19:34 ` Shakeel Butt
2022-06-17 19:08 ` Linus Torvalds
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=YqzQKER4JRoudTJE@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=rpenyaev@suse.de \
--cc=shakeelb@google.com \
--cc=torvalds@linux-foundation.org \
--cc=will@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