From mboxrd@z Thu Jan 1 00:00:00 1970 From: axboe@fb.com (Jens Axboe) Date: Tue, 23 Dec 2014 14:24:43 -0700 Subject: [PATCH 0/4] nvme-blkmq fixes In-Reply-To: References: <1419036856-16275-1-git-send-email-keith.busch@intel.com> <5495B2BF.8070602@fb.com> <5495CDFE.3060404@fb.com> <54984B10.6060907@fb.com> <549860A9.7060106@fb.com> <54987A43.9000807@fb.com> <5499AB17.6060805@fb.com> <5499AC69.2010706@fb.com> Message-ID: <5499DD9B.4020508@fb.com> On 12/23/2014 02:23 PM, Keith Busch wrote: > On Tue, 23 Dec 2014, Keith Busch wrote: >> @@ -432,7 +432,8 @@ static void req_completion(struct nvme_queue >> *nvmeq, void *ctx, >> if (!(status & NVME_SC_DNR || blk_noretry_request(req)) >> && (jiffies - req->start_time) < req->timeout) { >> blk_mq_requeue_request(req); >> - blk_mq_kick_requeue_list(req->q); >> + if (!blk_queue_stopped(req->q)) >> + blk_mq_kick_requeue_list(req->q); >> return; >> } > > Oops, experimenting with different things, took the wrong snapshot of > the patch. Should be: > > + if (nvmeq->cq_vector != -1) > > rather than: > > + if (!blk_queue_stopped(req->q)) > > Anyway, I'm going to keep messing with this until I can either hit the > other failures I mentioned or convince myself it's safe before sending > something for official consideration. I was puzzled by the signed change for cq_vector by itself. I'll wait on more results from you before doing anything. -- Jens Axboe