From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"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: Mon, 05 Jan 2015 14:25:05 +0100 [thread overview]
Message-ID: <54AA90B1.1030201@suse.de> (raw)
In-Reply-To: <CAMM=eLdGQ4wQDHy0ACzDsYOs0AYC+KAcx7Mx7FmpBTV293d41Q@mail.gmail.com>
On 01/04/2015 06:16 PM, Mike Snitzer wrote:
> Hi,
>
> I'd like to attend LSF (and the first day of Vault).
>
> As a DM maintainer I'm open to discussing anything DM related. In
> particular I'd like to at least have hallway track discussions with
> key people interested in DM multipath support for blk-mq devices.
> Keith Busch and I have gone ahead and implemented the bulk of this
> request-based DM support for blk-mq devices, see:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-for-3.20-blk-mq
>
> But Bart says he is seeing inconsistent performance now that the code
> appears relatively stable. I'll continue analyzing this aspect of
> things and by the time LSF rolls around I hope the code to be sorted.
>
I'd be interested in having a discussion here, too.
hch and me have discussed an alternative approach for multipathing
(send the request directly and only clone request if the original
submission failed) which I'd like to discuss with a broader audience.
And I'd be interested in getting multipath to work with blk-mq, naturally.
> Another topic we need to come to terms with is the state of XCOPY
> (whether the initial approach needs further work, etc) -- Mikulas
> Patocka reworked aspects of Martin's initial approach but it hasn't
> progressed upstream:
> https://www.redhat.com/archives/dm-devel/2014-October/msg00167.html
>
Yep. That definitely needs to be discussed.
Especially we'd need to discuss how to handle exceptions, seeing that
XCOPY might fail basically at any time.
And there are some corner-cases (bandwidth starvation on the target)
which needs to be discussed, too.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-05 13:25 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 ` Hannes Reinecke [this message]
2015-01-06 23:55 ` [dm-devel] " Martin K. Petersen
2015-01-07 8:32 ` Hannes Reinecke
2015-01-07 23:39 ` Martin K. Petersen
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=54AA90B1.1030201@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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.