From: keith.busch@intel.com (Keith Busch)
Subject: RFC: what to do about abort?
Date: Thu, 5 May 2016 17:56:33 -0400 [thread overview]
Message-ID: <20160505215633.GF8503@localhost.localdomain> (raw)
In-Reply-To: <20160505141118.GA5260@infradead.org>
On Thu, May 05, 2016@07:11:18AM -0700, Christoph Hellwig wrote:
> You're the maintainer, so it's up to you - it just doesn't seem very
> useful to me from both the host and device perspectice.
If you don't find a deterministic event on failure to be useful for the
device side, you must have better visibility into your internal device
state than most others do. :)
The spec so badly defines abort, though, I have to agree you're right
to remove it. Since having a dependable event greatly helps debugging
field issues when device makers desperately want to blame the driver
for command timeouts, does it sound okay to have a module param toggle
its use, defaulting to off?
next prev parent reply other threads:[~2016-05-05 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 10:03 RFC: what to do about abort? Christoph Hellwig
2016-05-04 10:19 ` Hannes Reinecke
2016-05-04 10:58 ` Christoph Hellwig
2016-05-04 14:59 ` Busch, Keith
2016-05-05 14:11 ` Christoph Hellwig
2016-05-05 21:56 ` Keith Busch [this message]
2016-05-08 9:04 ` Christoph Hellwig
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=20160505215633.GF8503@localhost.localdomain \
--to=keith.busch@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox