From: Christoph Hellwig <hch@infradead.org>
To: Changwei Ge <gechangwei@live.cn>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"ge.changwei@h3c.com" <ge.changwei@h3c.com>,
"liu.cong@h3c.com" <liu.cong@h3c.com>,
"changlimin@h3c.com" <changlimin@h3c.com>
Subject: Re: [RFC] Can DM pass SCSI command to path now?
Date: Fri, 17 Aug 2018 00:35:06 -0700 [thread overview]
Message-ID: <20180817073506.GA8653@infradead.org> (raw)
In-Reply-To: <HK0PR06MB25611BB82C50809642EFC4C5D53E0@HK0PR06MB2561.apcprd06.prod.outlook.com>
On Thu, Aug 16, 2018 at 11:56:48AM +0000, Changwei Ge wrote:
> Hi list,
>
> Recently, I found that block request can't take SCSI CDB any more.
>
> So, can we still pass SCSI command to DM device which will clone the
> request and transfer it real path?
You never could before, as the infrastructure was always missing.
prev parent reply other threads:[~2018-08-17 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 11:56 [RFC] Can DM pass SCSI command to path now? Changwei Ge
2018-08-17 7:35 ` Christoph Hellwig [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=20180817073506.GA8653@infradead.org \
--to=hch@infradead.org \
--cc=changlimin@h3c.com \
--cc=dm-devel@redhat.com \
--cc=ge.changwei@h3c.com \
--cc=gechangwei@live.cn \
--cc=linux-block@vger.kernel.org \
--cc=liu.cong@h3c.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;
as well as URLs for NNTP newsgroup(s).