public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	"Alasdair G. Kergon" <agk@redhat.com>,
	Jonathan Brassow <jbrassow@redhat.com>,
	Edward Thornber <thornber@redhat.com>,
	Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@infradead.org>,
	dm-devel@redhat.com, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/15] SCSI XCOPY support for the kernel and device mapper
Date: Fri, 29 Aug 2014 06:29:02 -0400	[thread overview]
Message-ID: <yq1egvzfv2p.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20140828213719.GA3734@redhat.com> (Mike Snitzer's message of "Thu, 28 Aug 2014 17:37:19 -0400")

>>>>> "Mike" == Mike Snitzer <snitzer@redhat.com> writes:

Mike> It would be ideal for XCOPY support to make its way upstream for
Mike> 3.18.. but the window for staging this work in time is closing.

Mike> Any chance you might have some time to review Mikulas' revised
Mike> approach to your initial XCOPY support? 

It is at the top of my list.

-- 
Martin K. Petersen	Oracle Linux Engineering

      reply	other threads:[~2014-08-29 10:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 19:34 [PATCH 0/15] SCSI XCOPY support for the kernel and device mapper Mikulas Patocka
2014-07-15 19:34 ` [PATCH 1/15] block copy: initial XCOPY offload support Mikulas Patocka
2014-07-18 13:03   ` Tomas Henzl
2014-07-18 14:35     ` Mikulas Patocka
2014-08-04 14:09   ` Pavel Machek
2014-08-05 22:45     ` Mikulas Patocka
2014-07-15 19:35 ` [PATCH 2/15] block copy: use two bios Mikulas Patocka
2014-07-15 19:35 ` [PATCH 3/15] block copy: report the amount of copied data Mikulas Patocka
2014-07-15 19:36 ` [PATCH 4/15] block copy: use a timer to fix a theoretical deadlock Mikulas Patocka
2014-07-15 19:37 ` [PATCH 5/15] block copy: use merge_bvec_fn for copies Mikulas Patocka
2014-07-15 19:37 ` [PATCH 6/15] block copy: use asynchronous notification Mikulas Patocka
2014-07-15 19:39 ` [PATCH 7/15] dm: remove num_write_bios Mikulas Patocka
2014-07-15 19:39 ` [PATCH 8/15] dm: introduce dm_ask_for_duplicate_bios Mikulas Patocka
2014-07-15 19:40 ` [PATCH 9/15] dm: implement copy Mikulas Patocka
2014-07-15 19:40 ` [PATCH 10/15] dm linear: support copy Mikulas Patocka
2014-07-15 19:41 ` [PATCH 11/15] dm stripe: " Mikulas Patocka
2014-07-15 19:42 ` [PATCH 12/15] dm kcopyd: introduce the function submit_job Mikulas Patocka
2014-07-15 19:43 ` [PATCH 13/15] dm kcopyd: support copy offload Mikulas Patocka
2014-07-15 19:43 ` [PATCH 14/15] dm kcopyd: change mutex to spinlock Mikulas Patocka
2014-07-15 19:44 ` [PATCH 15/15] dm kcopyd: call copy offload with asynchronous callback Mikulas Patocka
2014-08-28 21:37 ` [PATCH 0/15] SCSI XCOPY support for the kernel and device mapper Mike Snitzer
2014-08-29 10:29   ` Martin K. Petersen [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=yq1egvzfv2p.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=agk@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=jbrassow@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@redhat.com \
    --cc=thornber@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