From: "WEI-HONG, YE" <1234567weewee457@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Waiman Long <longman@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Cheng-Han Wu <hank20010209@gmail.com>,
"WEI-HONG, YE" <1234567weewee457@gmail.com>
Subject: [PATCH] locking/qspinlock: Clarify pending field layout
Date: Mon, 25 May 2026 13:04:50 +0000 [thread overview]
Message-ID: <20260525130450.723937-1-1234567weewee457@gmail.com> (raw)
For CONFIG_NR_CPUS < 16K, _Q_PENDING_BITS is 8 and the pending
field occupies bits 8-15 of the lock word. The current comment
documents bit 8 as pending and bits 9-15 as unused, which describes
the pending flag value rather than the field layout.
Describe bits 8-15 as the pending byte so the layout description
is consistent with the lock byte.
Signed-off-by: WEI-HONG, YE <1234567weewee457@gmail.com>
---
include/asm-generic/qspinlock_types.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/asm-generic/qspinlock_types.h b/include/asm-generic/qspinlock_types.h
index 2fd1fb89ec36..7d17b9bb069c 100644
--- a/include/asm-generic/qspinlock_types.h
+++ b/include/asm-generic/qspinlock_types.h
@@ -53,8 +53,7 @@ typedef struct qspinlock {
*
* When NR_CPUS < 16K
* 0- 7: locked byte
- * 8: pending
- * 9-15: not used
+ * 8-15: pending byte
* 16-17: tail index
* 18-31: tail cpu (+1)
*
--
2.48.1
next reply other threads:[~2026-05-25 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 13:04 WEI-HONG, YE [this message]
2026-05-27 0:52 ` Waiman Long
2026-06-03 14:25 ` [tip: locking/core] " tip-bot2 for WEI-HONG, YE
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=20260525130450.723937-1-1234567weewee457@gmail.com \
--to=1234567weewee457@gmail.com \
--cc=arnd@arndb.de \
--cc=hank20010209@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=peterz@infradead.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®