From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <Bart.VanAssche@wdc.com>, "hch@lst.de" <hch@lst.de>
Cc: "tj@kernel.org" <tj@kernel.org>,
"israelr@mellanox.com" <israelr@mellanox.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"maxg@mellanox.com" <maxg@mellanox.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>
Subject: Re: [PATCH] blk-mq: Fix recently introduced races in the timeout handling code
Date: Mon, 9 Apr 2018 09:03:05 -0600 [thread overview]
Message-ID: <548aa0f5-2e7d-e659-4b25-a7dc69352025@kernel.dk> (raw)
In-Reply-To: <a7972bb84efa3313b87ecbaf37112b360346bdfe.camel@wdc.com>
On 4/9/18 8:58 AM, Bart Van Assche wrote:
> On Mon, 2018-04-09 at 11:37 +0200, Christoph Hellwig wrote:
>> This looks sensible, but I'm worried about taking a whole spinlock
>> for every request completion, including irq disabling. However it seems
>> like your new updated pattern would fit use of cmpxchg() very nicely.
>
> Hello Christoph,
>
> Thanks for the review. I had a look at the spin lock implementation on
> x86 and apparently on x86 spin locks are implemented as qspinlocks
> (include/asm-generic/qspinlock.h). queued_spin_lock() already uses
> atomic_cmpxchg_acquire(). Are you sure that replacing the spin lock
> by cmpxchg() will yield a performance improvement?
It's definitely worth a shot, especially since this looks like a clear
cut case for cmpxchg(). Additionally, it also kills the local irq
disable.
Conversion should be trivial and we can do some perf testing around
that.
Neither solution really makes me happy though, the prospect of
either kind of synchronization cost isn't appealing at all. I'll
have to ponder this a lot more, but it would be ideal if we could
shift that cost to the extremely unlikely case of a timeout
triggering rather than add the cost upfront to EVERY request.
--
Jens Axboe
next prev parent reply other threads:[~2018-04-09 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 5:20 [PATCH] blk-mq: Fix recently introduced races in the timeout handling code Bart Van Assche
2018-04-09 8:37 ` Sagi Grimberg
2018-04-09 14:37 ` Bart Van Assche
2018-04-09 15:42 ` Israel Rukshin
2018-04-09 16:49 ` Tejun Heo
2018-04-09 9:37 ` Christoph Hellwig
2018-04-09 14:58 ` Bart Van Assche
2018-04-09 15:03 ` Jens Axboe [this message]
2018-04-09 16:47 ` Tejun Heo
2018-04-09 17:03 ` Bart Van Assche
2018-04-09 18:56 ` tj
2018-04-09 21:30 ` Bart Van Assche
2018-04-09 21:40 ` tj
-- strict thread matches above, loose matches on Subject: below --
2018-04-10 15:37 Alex G.
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=548aa0f5-2e7d-e659-4b25-a7dc69352025@kernel.dk \
--to=axboe@kernel.dk \
--cc=Bart.VanAssche@wdc.com \
--cc=hch@lst.de \
--cc=israelr@mellanox.com \
--cc=linux-block@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
--cc=tj@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).