From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] NVMe: fix retry/error logic in nvme_queue_rq()
Date: Thu, 11 Dec 2014 13:58:10 -0700 [thread overview]
Message-ID: <548A0562.6070902@fb.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1412112040520.4026@localhost.lm.intel.com>
On 12/11/2014 01:54 PM, Keith Busch wrote:
> The real reason for reusing the nvme_iod was we needed some structure
> to exist for the life of the command to track total time so we don't
> retry indefinitely. Keeping the dma mapping was just a bonus.
Before blk-mq, you could have cases where ->make_request_fn() was
entered and you'd have to defer due to being out of commands, for
instance. That's no longer the case. Right now it should only happen if
we run into resource constraints, on the IOMMU or memory side. Now we
are definitely better off freeing everything. Besides, we didn't retain
the full state, so the retry was buggy.
> Total time is tracked with "req->start_time" now, so nothing wrong with
> removing the iod reuse.
>
> Acked-by: Keith Busch <keith.busch at intel.com>
Thanks!
--
Jens Axboe
prev parent reply other threads:[~2014-12-11 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 20:33 [PATCH] NVMe: fix retry/error logic in nvme_queue_rq() Jens Axboe
2014-12-11 20:54 ` Keith Busch
2014-12-11 20:58 ` Jens Axboe [this message]
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=548A0562.6070902@fb.com \
--to=axboe@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.