From: Waiman Long <longman@redhat.com>
To: Hillf Danton <hdanton@sina.com>, Peter Zijlstra <peterz@infradead.org>
Cc: "Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
linux-kernel@vger.kernel.org, john.p.donnelly@oracle.com,
"Mukesh Ojha" <quic_mojha@quicinc.com>,
"Ting11 Wang 王婷" <wangting11@xiaomi.com>
Subject: Re: [PATCH v3 2/5] locking/rwsem: Limit # of null owner retries for handoff writer
Date: Tue, 25 Oct 2022 15:00:29 -0400 [thread overview]
Message-ID: <7dc61070-4696-4668-eaef-efae8d7fa271@redhat.com> (raw)
In-Reply-To: <20221025145843.2953-1-hdanton@sina.com>
On 10/25/22 10:58, Hillf Danton wrote:
>> @@ -1179,15 +1171,12 @@ rwsem_down_write_slowpath(struct rw_semaphore *sem, int state)
>> if (waiter.handoff_set) {
>> enum owner_state owner_state;
>>
>> - preempt_disable();
>> owner_state = rwsem_spin_on_owner(sem);
>> - preempt_enable();
>> -
>> if (owner_state == OWNER_NULL)
>> goto trylock_again;
>> }
> __up_write()
> {
> rwsem_clear_owner(sem);
> /*
> If lockup can happen when a bound kworker gets preempted here by
> a FIFO acquirer for write, this is a case of preemption deeper
> than thought IMO
> */
> tmp = atomic_long_fetch_add_release(-RWSEM_WRITER_LOCKED, &sem->count);
> if (unlikely(tmp & RWSEM_FLAG_WAITERS))
> rwsem_wake(sem);
>
A preempt_disable()/preempt_enable() pair has been added by commit
48dfb5d2560 ("locking/rwsem: Disable preemption while trying for rwsem
lock") to __up_write(). So that should not be a problem. However, that
does make this change, if implemented, has dependency on the coexistence
of the previous mentioned commit to be functionally complete.
Cheers,
Longman
next prev parent reply other threads:[~2022-10-25 19:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 21:13 [PATCH v3 0/5] lockinig/rwsem: Fix rwsem bugs & enable true lock handoff Waiman Long
2022-10-17 21:13 ` [PATCH v3 1/5] locking/rwsem: Prevent non-first waiter from spinning in down_write() slowpath Waiman Long
2022-10-24 13:17 ` Peter Zijlstra
2022-10-24 13:50 ` Waiman Long
2022-10-17 21:13 ` [PATCH v3 2/5] locking/rwsem: Limit # of null owner retries for handoff writer Waiman Long
2022-10-24 13:31 ` Peter Zijlstra
2022-10-24 15:55 ` Waiman Long
2022-10-25 11:22 ` Peter Zijlstra
2022-10-25 11:48 ` Peter Zijlstra
2022-10-25 19:55 ` Waiman Long
2022-10-25 20:14 ` Peter Zijlstra
2022-10-26 1:44 ` Waiman Long
[not found] ` <20221025145843.2953-1-hdanton@sina.com>
2022-10-25 19:00 ` Waiman Long [this message]
2022-10-17 21:13 ` [PATCH v3 3/5] locking/rwsem: Change waiter->hanodff_set to a handoff_state enum Waiman Long
2022-10-17 21:13 ` [PATCH v3 4/5] locking/rwsem: Enable direct rwsem lock handoff Waiman Long
2022-10-17 21:13 ` [PATCH v3 5/5] locking/rwsem: Update handoff lock events tracking Waiman Long
[not found] ` <20221018111424.1007-1-hdanton@sina.com>
2022-10-18 14:13 ` [PATCH v3 4/5] locking/rwsem: Enable direct rwsem lock handoff Mukesh Ojha
2022-10-18 17:37 ` Waiman Long
[not found] ` <20221018235138.1088-1-hdanton@sina.com>
2022-10-19 0:39 ` Waiman Long
[not found] ` <20221019022934.1166-1-hdanton@sina.com>
2022-10-19 2:49 ` Waiman Long
[not found] ` <20221019070559.1220-1-hdanton@sina.com>
2022-10-19 15:02 ` Waiman Long
2022-10-24 16:18 ` 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=7dc61070-4696-4668-eaef-efae8d7fa271@redhat.com \
--to=longman@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=hdanton@sina.com \
--cc=john.p.donnelly@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quic_mojha@quicinc.com \
--cc=wangting11@xiaomi.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®