mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Mikulas Patocka <mpatocka@redhat.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "James E.J. Bottomley" <JBottomley@odin.com>,
	Jens Axboe <axboe@kernel.dk>, Mike Snitzer <msnitzer@redhat.com>,
	Jonathan Brassow <jbrassow@redhat.com>,
	dm-devel@redhat.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [PATCH 0/15] copy offload patches
Date: Mon, 14 Dec 2015 22:43:04 -0500	[thread overview]
Message-ID: <566F8C48.6060903@interlog.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1512142018030.8189@file01.intranet.prod.int.rdu2.redhat.com>

On 15-12-14 08:22 PM, Mikulas Patocka wrote:
>
>
> On Thu, 10 Dec 2015, Martin K. Petersen wrote:
>
>>>>>>> "Mikulas" == Mikulas Patocka <mpatocka@redhat.com> writes:
>>
>> Mikulas,
>>
>> Mikulas> This patch series adds copy offload (the XCOPY command) to the
>> Mikulas> block layer, SCSI subsystems and device mapper.
>>
>> Now that the VFS stuff appears to stabilize I agree it's a good time to
>> revisit all this. I just merged the required VPD patches from Hannes so
>> those will be in 4.5.
>>
>> I have a bunch of changes to the SCSI code that I worked on over the
>> spring/summer based on a feedback from the array vendors after
>> discussions we started at LSF/MM. Generally speaking, their comments
>> didn't make things easier, nor prettier :( But your two bio approach is
>> a requirement to accommodate those needs (token-based copy) so I'll work
>> on consolidating your changes with mine.
>
> Let me know when you make some progress with that.
>
> Is there some software iSCSI implementation that supports token-based
> copy? So that I could try to make support for it.

FreeNAS. See:
    http://www.freenas.org/

It has the best ODX implementation (thanks to Alexander Motin) that
I have come across for testing my ddpt based ODX client. It also
supports large parts of the more general xcopy LID1 and LID4.


BTW In SPC-5 xcopy LID1 has been dropped and "xcopy" now means
xcopy LID4 (as found in SPC-4).

Doug Gilbert

>> That said, we still need Mike Christie's patches to go in first.
>>
>> Mike: What's your status? I'm afraid I didn't get a chance to dig very
>> deep in your series since it coincided with me scrambling to sort out
>> SCSI for 4.4. Do you think there's a chance we could get your patches in
>> shape for 4.5? Is there an up-to-date tree I can look at?
>>
>> --
>> Martin K. Petersen	Oracle Linux Engineering



  reply	other threads:[~2015-12-15  3:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 17:29 Mikulas Patocka
2015-12-10 17:30 ` [PATCH 1/15] block copy: initial XCOPY offload support Mikulas Patocka
2015-12-10 17:30 ` [PATCH 2/15] block copy: use two bios Mikulas Patocka
2015-12-10 17:30 ` [PATCH 3/15] block copy: report the amount of copied data Mikulas Patocka
2015-12-10 17:30 ` [PATCH 4/15] block copy: use a timer to fix a theoretical deadlock Mikulas Patocka
2015-12-10 17:30 ` [PATCH 5/15] block copy: use asynchronous notification Mikulas Patocka
2015-12-10 17:30 ` [PATCH 6/15] scsi xcopy: suppress error messages Mikulas Patocka
2015-12-10 17:30 ` [PATCH 7/15] scsi xcopy: keep cache of failures Mikulas Patocka
2015-12-10 17:30 ` [PATCH 8/15] block copy: introduce "copy_boundary" limits Mikulas Patocka
2015-12-10 17:30 ` [PATCH 9/15] dm: implement copy Mikulas Patocka
2015-12-10 17:30 ` [PATCH 10/15] dm linear: support copy Mikulas Patocka
2015-12-10 17:31 ` [PATCH 11/15] dm stripe: " Mikulas Patocka
2015-12-10 17:31 ` [PATCH 12/15] dm kcopyd: introduce the function submit_job Mikulas Patocka
2015-12-10 17:31 ` [PATCH 13/15] dm kcopyd: support copy offload Mikulas Patocka
2015-12-10 17:31 ` [PATCH 14/15] dm kcopyd: change mutex to spinlock Mikulas Patocka
2015-12-10 17:31 ` [PATCH 15/15] dm kcopyd: call copy offload with asynchronous callback Mikulas Patocka
2015-12-10 22:33 ` [PATCH 0/15] copy offload patches Martin K. Petersen
2015-12-11  1:46   ` [dm-devel] " Mike Christie
2015-12-11  5:06   ` Mike Christie
2015-12-11 19:55     ` Christoph Hellwig
2015-12-15  1:22   ` Mikulas Patocka
2015-12-15  3:43     ` Douglas Gilbert [this message]
2015-12-16  3:05     ` Martin K. Petersen

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=566F8C48.6060903@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=JBottomley@odin.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=jbrassow@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michaelc@cs.wisc.edu \
    --cc=mpatocka@redhat.com \
    --cc=msnitzer@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

Powered by JetHome