All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: "Alasdair G. Kergon" <agk@redhat.com>,
	Mike Snitzer <msnitzer@redhat.com>,
	Jonathan Brassow <jbrassow@redhat.com>,
	Edward Thornber <thornber@redhat.com>,
	"Martin K. Petersen" <martin.petersen@oracle.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 1/15] block copy: initial XCOPY offload support
Date: Mon, 4 Aug 2014 16:09:25 +0200	[thread overview]
Message-ID: <20140804140925.GA24261@amd.pavel.ucw.cz> (raw)
In-Reply-To: <alpine.LRH.2.02.1407151534180.14632@file01.intranet.prod.int.rdu2.redhat.com>

On Tue 2014-07-15 15:34:47, Mikulas Patocka wrote:
> This is Martin Petersen's xcopy patch
> (https://git.kernel.org/cgit/linux/kernel/git/mkp/linux.git/commit/?h=xcopy&id=0bdeed274e16b3038a851552188512071974eea8)
> with some bug fixes, ported to the current kernel.
> 
> This patch makes it possible to use the SCSI XCOPY command.
> 
> We create a bio that has REQ_COPY flag in bi_rw and a bi_copy structure
> that defines the source device. The target device is defined in the
> bi_bdev and bi_iter.bi_sector.
> 
> There is a new BLKCOPY ioctl that makes it possible to use XCOPY from
> userspace. The ioctl argument is a pointer to an array of four uint64_t
> values.

But it is there only for block devices, right?

Is there plan to enable tools such as /bin/cp to use XCOPY?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2014-08-04 14:09 UTC|newest]

Thread overview: 24+ 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 [this message]
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
2015-12-10 17:29 [PATCH 0/15] copy offload patches Mikulas Patocka
2015-12-10 17:30 ` [PATCH 1/15] block copy: initial XCOPY offload support Mikulas Patocka
2015-12-10 17:30   ` Mikulas Patocka

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=20140804140925.GA24261@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --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=martin.petersen@oracle.com \
    --cc=mpatocka@redhat.com \
    --cc=msnitzer@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 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.