From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
device-mapper development <dm-devel@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [dm-devel] [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
Date: Wed, 07 Jan 2015 18:39:41 -0500 [thread overview]
Message-ID: <yq1vbki40ua.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <54ACEF13.7000508@suse.de> (Hannes Reinecke's message of "Wed, 07 Jan 2015 09:32:19 +0100")
>>>>> "Hannes" == Hannes Reinecke <hare@suse.de> writes:
Hannes> Not quite. XCOPY is optional, and the system works well without
Hannes> it. So the exception handling would need to copy things by hand
Hannes> to avoid regressions.
Or defer to user space.
But it's really no different from how we do WRITE SAME which may or may
not work. If it fails we fall back to writing zeroes.
Hannes> Plus XCOPY requires some elaborate setup, and even if those
Hannes> succeeded the array might still fail the command. _And_ there
Hannes> is no guarantee that that the XCOPY command is actually faster
Hannes> than the manual procedure.
It saves the data a roundtrip on the fabric. That itself may be more
valuable than a direct bandwidth win if there is concurrent I/O on the
wire.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2015-01-07 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 17:16 [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY Mike Snitzer
2015-01-05 13:25 ` [dm-devel] " Hannes Reinecke
2015-01-06 23:55 ` Martin K. Petersen
2015-01-07 8:32 ` Hannes Reinecke
2015-01-07 23:39 ` Martin K. Petersen [this message]
2015-01-08 6:31 ` Hannes Reinecke
2015-01-08 14:39 ` Martin K. Petersen
2015-01-06 23:52 ` Martin K. Petersen
2015-01-07 17:00 ` Nicholas A. Bellinger
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=yq1vbki40ua.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=hch@infradead.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 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.