[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201111043304.GS17076@casper.infradead.org>
Date: Wed, 11 Nov 2020 04:33:04 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Shuah Khan <skhan@...uxfoundation.org>
Cc: corbet@....net, keescook@...omium.org, gregkh@...uxfoundation.org,
peterz@...radead.org, rafael@...nel.org, lenb@...nel.org,
james.morse@....com, tony.luck@...el.com, bp@...en8.de,
minyard@....org, arnd@...db.de, mchehab@...nel.org,
rric@...nel.org, valentina.manea.m@...il.com, shuah@...nel.org,
zohar@...ux.ibm.com, dmitry.kasatkin@...il.com, jmorris@...ei.org,
serge@...lyn.com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-acpi@...r.kernel.org,
openipmi-developer@...ts.sourceforge.net,
linux-edac@...r.kernel.org, linux-usb@...r.kernel.org,
linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH 00/13] Introduce seqnum_ops
On Tue, Nov 10, 2020 at 12:53:26PM -0700, Shuah Khan wrote:
> There are a number of atomic_t usages in the kernel where atomic_t api
> is used strictly for counting sequence numbers and other statistical
> counters and not for managing object lifetime.
We already have something in Linux called a sequence counter, and it's
different from this. ID counter? instance number? monotonic_t? stat_t?
Powered by blists - more mailing lists