From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
chuck.lever@oracle.com, Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Doug Gilbert <dgilbert@interlog.com>
Subject: Re: status of block-integrity
Date: Thu, 09 Jan 2014 20:49:53 -0500 [thread overview]
Message-ID: <yq1vbxssj0e.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <52CE85C6.8000405@suse.de> (Hannes Reinecke's message of "Thu, 09 Jan 2014 12:19:34 +0100")
>>>>> "Hannes" == Hannes Reinecke <hare@suse.de> writes:
Hannes> With LID1/XCopy you have the ambiguity on where to actually send
Hannes> the command to; the spec is silent in this area.
Yeah, right now it's a coin toss.
However, thanks to VAAI most arrays support LID1. I'm trying to leverage
that. Doesn't in any way preclude LID4 being supported as well.
Hannes> As said, Doug and me are working on putting this into sg3_utils,
Hannes> then we'll have a better idea on the actual workings.
Cool! That'll save me some headaches when we start seeing LID4 devices.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-01-10 1:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 19:21 status of block-integrity Christoph Hellwig
2013-12-22 20:45 ` Nicholas A. Bellinger
2013-12-23 13:35 ` Martin K. Petersen
2013-12-23 13:48 ` Christoph Hellwig
2013-12-31 19:41 ` berthiaume, wayne
2014-01-07 8:28 ` Ric Wheeler
2014-01-07 13:33 ` Hannes Reinecke
2014-01-07 23:34 ` Matthew Wilcox
2014-01-08 0:05 ` James Bottomley
2014-01-08 15:43 ` Martin K. Petersen
2014-01-03 15:01 ` Hannes Reinecke
2014-01-03 20:03 ` Martin K. Petersen
2014-01-07 1:36 ` Darrick J. Wong
2014-01-07 7:17 ` Hannes Reinecke
2014-01-07 21:43 ` Martin K. Petersen
2014-01-08 7:14 ` Hannes Reinecke
2014-01-08 15:23 ` Martin K. Petersen
2014-01-09 11:19 ` Hannes Reinecke
2014-01-10 1:49 ` Martin K. Petersen [this message]
2014-01-07 15:06 ` Chuck Lever
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=yq1vbxssj0e.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=chuck.lever@oracle.com \
--cc=darrick.wong@oracle.com \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).