From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <longman@redhat.com>
Cc: "Hillf Danton" <hdanton@sina.com>, 马振华 <mazhenhua@xiaomi.com>,
mingo <mingo@redhat.com>, will <will@kernel.org>,
"boqun.feng" <boqun.feng@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG]locking/rwsem: only clean RWSEM_FLAG_HANDOFF when already set
Date: Thu, 11 Nov 2021 20:20:10 +0100 [thread overview]
Message-ID: <YY1s6v9b/tYtNnGv@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <61735528-141c-8d77-592d-b6b8fb75ebaa@redhat.com>
On Thu, Nov 11, 2021 at 02:14:48PM -0500, Waiman Long wrote:
> As for the PHASE_CHANGE name, we have to be consistent in both rwsem and
> mutex. Maybe a follow up patch if you think we should change the
> terminology.
Well, that's exactly the point, they do radically different things.
Having the same name for two different things is confusing.
Anyway, let me go read that patch you sent.
next prev parent reply other threads:[~2021-11-11 19:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4fafad133b074f279dbab1aa3642e23f@xiaomi.com>
2021-11-07 3:25 ` Waiman Long
2021-11-07 3:28 ` Waiman Long
[not found] ` <20211107090131.1535-1-hdanton@sina.com>
2021-11-07 15:24 ` Waiman Long
2021-11-07 19:52 ` Waiman Long
2021-11-10 21:38 ` Peter Zijlstra
2021-11-11 2:42 ` Maria Yu
2021-11-11 15:08 ` Peter Zijlstra
2021-11-11 19:14 ` Waiman Long
2021-11-11 19:20 ` Peter Zijlstra [this message]
2021-11-11 19:36 ` Waiman Long
2021-11-11 19:52 ` Waiman Long
2021-11-11 20:26 ` Peter Zijlstra
2021-11-11 21:01 ` Waiman Long
2021-11-11 21:25 ` Waiman Long
2021-11-11 21:53 ` Peter Zijlstra
2021-11-11 21:55 ` Waiman Long
2021-11-11 22:00 ` Waiman Long
2021-11-11 21:38 ` Peter Zijlstra
2021-11-11 21:46 ` Waiman Long
2021-11-11 20:35 ` Peter Zijlstra
2021-11-11 20:39 ` Peter Zijlstra
2021-11-11 20:45 ` Waiman Long
2021-11-11 21:27 ` Peter Zijlstra
2021-11-11 21:54 ` Waiman Long
2021-11-11 20:50 ` Peter Zijlstra
2021-11-11 21:09 ` Waiman Long
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=YY1s6v9b/tYtNnGv@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mazhenhua@xiaomi.com \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®