[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170421105654.GC31499@infradead.org>
Date: Fri, 21 Apr 2017 03:56:54 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Eric Biggers <ebiggers3@...il.com>
Cc: "Reshetova, Elena" <elena.reshetova@...el.com>,
Christoph Hellwig <hch@...radead.org>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"james.bottomley@...senpartnership.com"
<james.bottomley@...senpartnership.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"fujita.tomonori@....ntt.co.jp" <fujita.tomonori@....ntt.co.jp>,
"mingo@...hat.com" <mingo@...hat.com>, "clm@...com" <clm@...com>,
"jbacik@...com" <jbacik@...com>,
"dsterba@...e.com" <dsterba@...e.com>
Subject: Re: [PATCH 0/5] v2: block subsystem refcounter conversions
On Thu, Apr 20, 2017 at 11:33:19AM -0700, Eric Biggers wrote:
> Like I suggested months ago, how about doing an efficient implementation of
> refcount_t which doesn't use the bloated cmpxchg loop? Then there would be no
> need for endless performance arguments. In fact, in PaX there are already
> example implementations for several architectures. It's unfortunate that
> they're still being ignored for some reason.
Yes. I will also NAK other conversions until this is done, which is a
bit sad as the recount_t API itself is very useful.
Powered by blists - more mailing lists