From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: lsf-pc@lists.linux-foundation.org,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
Jej B <James.Bottomley@hansenpartnership.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
Date: Tue, 06 Jan 2015 18:52:45 -0500 [thread overview]
Message-ID: <yq1bnmb8o1e.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CAMM=eLdGQ4wQDHy0ACzDsYOs0AYC+KAcx7Mx7FmpBTV293d41Q@mail.gmail.com> (Mike Snitzer's message of "Sun, 4 Jan 2015 12:16:57 -0500")
>>>>> "Mike" == Mike Snitzer <snitzer@redhat.com> writes:
Mike> Another topic we need to come to terms with is the state of XCOPY
Mike> (whether the initial approach needs further work, etc) -- Mikulas
Mike> Patocka reworked aspects of Martin's initial approach but it
Mike> hasn't progressed upstream:
Yeah, I'd like to get that sorted out too. It got stuck on running out
of request flags and that requires some block layer surgery. I'll try to
get that piece done right away for 3.20 so we can get xcopy into 3.21.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2015-01-06 23:52 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
2015-01-08 6:31 ` Hannes Reinecke
2015-01-08 14:39 ` Martin K. Petersen
2015-01-06 23:52 ` Martin K. Petersen [this message]
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=yq1bnmb8o1e.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=snitzer@redhat.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