From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: EH method APIs
Date: Fri, 4 Apr 2014 00:24:00 -0700 [thread overview]
Message-ID: <20140404072400.GA23630@infradead.org> (raw)
In-Reply-To: <533E5C81.60409@suse.de>
On Fri, Apr 04, 2014 at 09:17:21AM +0200, Hannes Reinecke wrote:
> Plus we don't meddle with block request allocation intrinsics
> anymore; the SCSI EH command is allocate within the SCSI midlayer,
> and requests originating from the block layer won't be messed with.
Any chance we could also switch to a new scsi_tmf structure instead
of reusing struct scsi_cmnd for that? It should be a lot smaller
without all the baggage, and make it clear we're not dealing with a
command. That would also solve the scsi_reset_provide issue.
next prev parent reply other threads:[~2014-04-04 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 7:04 EH method APIs Christoph Hellwig
2014-04-04 7:17 ` Hannes Reinecke
2014-04-04 7:24 ` Christoph Hellwig [this message]
2014-04-04 7:36 ` Hannes Reinecke
2014-04-04 7:42 ` 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=20140404072400.GA23630@infradead.org \
--to=hch@infradead.org \
--cc=hare@suse.de \
--cc=linux-scsi@vger.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).