linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Waiman Long <llong@redhat.com>
To: alexjlzheng@gmail.com, peterz@infradead.org, will@kernel.org,
	boqun.feng@gmail.com
Cc: linux-kernel@vger.kernel.org, Jinliang Zheng <alexjlzheng@tencent.com>
Subject: Re: [PATCH] locking/rwsem: use OWNER_NONSPINNABLE directly instead of OWNER_SPINNABLE
Date: Fri, 13 Jun 2025 01:52:43 -0400	[thread overview]
Message-ID: <7a006014-bf6e-4480-bd61-b0333c74e3a4@redhat.com> (raw)
In-Reply-To: <20250610130158.4876-1-alexjlzheng@tencent.com>


On 6/10/25 9:01 AM, alexjlzheng@gmail.com wrote:
> From: Jinliang Zheng <alexjlzheng@tencent.com>
>
> After commit 7d43f1ce9dd0 ("locking/rwsem: Enable time-based spinning on
> reader-owned rwsem"), OWNER_SPINNABLE contains all possible values except
> OWNER_NONSPINNABLE, namely OWNER_NULL | OWNER_WRITER | OWNER_READER.
>
> Therefore, it is better to use OWNER_NONSPINNABLE directly to determine
> whether to exit optimistic spin.
>
> And, remove useless OWNER_SPINNABLE to simplify the code.
>
> Signed-off-by: Jinliang Zheng <alexjlzheng@tencent.com>
> ---
>   kernel/locking/rwsem.c | 4 +---
>   1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/kernel/locking/rwsem.c b/kernel/locking/rwsem.c
> index 2ddb827e3bea..8572dba95af4 100644
> --- a/kernel/locking/rwsem.c
> +++ b/kernel/locking/rwsem.c
> @@ -727,8 +727,6 @@ static inline bool rwsem_can_spin_on_owner(struct rw_semaphore *sem)
>   	return ret;
>   }
>   
> -#define OWNER_SPINNABLE		(OWNER_NULL | OWNER_WRITER | OWNER_READER)
> -
>   static inline enum owner_state
>   rwsem_owner_state(struct task_struct *owner, unsigned long flags)
>   {
> @@ -835,7 +833,7 @@ static bool rwsem_optimistic_spin(struct rw_semaphore *sem)
>   		enum owner_state owner_state;
>   
>   		owner_state = rwsem_spin_on_owner(sem);
> -		if (!(owner_state & OWNER_SPINNABLE))
> +		if (owner_state == OWNER_NONSPINNABLE)
>   			break;
>   
>   		/*

Right, OWNER_SPINNABLE is no longer needed after commit 7d43f1ce9dd0.

Acked-by: Waiman Long <longman@redhat.com>


  reply	other threads:[~2025-06-13  5:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 13:01 [PATCH] locking/rwsem: use OWNER_NONSPINNABLE directly instead of OWNER_SPINNABLE alexjlzheng
2025-06-13  5:52 ` Waiman Long [this message]
2025-06-17 17:13   ` Boqun Feng
2025-07-19 17:40 ` [tip: locking/core] locking/rwsem: Use " tip-bot2 for Jinliang Zheng

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=7a006014-bf6e-4480-bd61-b0333c74e3a4@redhat.com \
    --to=llong@redhat.com \
    --cc=alexjlzheng@gmail.com \
    --cc=alexjlzheng@tencent.com \
    --cc=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).