[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7233p553-861o-9772-n4nr-rr5424prq1r@vanv.qr>
Date: Thu, 11 May 2023 14:14:08 +0200 (CEST)
From: Jan Engelhardt <jengelh@...i.de>
To: Kent Overstreet <kent.overstreet@...ux.dev>
cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-bcachefs@...r.kernel.org,
Kent Overstreet <kent.overstreet@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
Waiman Long <longman@...hat.com>,
Boqun Feng <boqun.feng@...il.com>
Subject: Re: [PATCH 04/32] locking: SIX locks (shared/intent/exclusive)
On Tuesday 2023-05-09 18:56, Kent Overstreet wrote:
>--- /dev/null
>+++ b/include/linux/six.h
>@@ -0,0 +1,210 @@
>+ * There are also operations that take the lock type as a parameter, where the
>+ * type is one of SIX_LOCK_read, SIX_LOCK_intent, or SIX_LOCK_write:
>+ *
>+ * six_lock_type(lock, type)
>+ * six_unlock_type(lock, type)
>+ * six_relock(lock, type, seq)
>+ * six_trylock_type(lock, type)
>+ * six_trylock_convert(lock, from, to)
>+ *
>+ * A lock may be held multiple types by the same thread (for read or intent,
"multiple times"
>+// SPDX-License-Identifier: GPL-2.0
The currently SPDX list only knows "GPL-2.0-only" or "GPL-2.0-or-later",
please edit.
Powered by blists - more mailing lists