From: Christoph Hellwig <hch@infradead.org>
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>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: ANNOUNCE: SCSI XCOPY support for the kernel and device mapper
Date: Tue, 15 Jul 2014 11:55:13 -0700 [thread overview]
Message-ID: <20140715185513.GA5331@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1407151359430.5499@file01.intranet.prod.int.rdu2.redhat.com>
On Tue, Jul 15, 2014 at 02:33:13PM -0400, Mikulas Patocka wrote:
> Hi
>
> I annouce that I released the first version of a patch set that makes it
> possible to use SCSI XCOPY offload for the block layer and device mapper.
>
> The patchset is at
> http://people.redhat.com/~mpatocka/patches/kernel/xcopy/series.html It
> requires kernel version at least 3.16-rc4. It was tested on target-core
> iSCSI implementation.
Can you send the series to the mainling list(s)? That makes it a lot
easier to do a quick review.
> The dm-kcopyd subsystem is modified to use the XCOPY command, so device
> mapper targets that use it (mirror, snapshot, thin, cache) take advantage
> of copy offload automatically.
That sounds good, do you have any benchmarking data that shows the
advantage of using XCOPY?
next prev parent reply other threads:[~2014-07-15 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 18:33 ANNOUNCE: SCSI XCOPY support for the kernel and device mapper Mikulas Patocka
2014-07-15 18:55 ` Christoph Hellwig [this message]
2014-07-15 19:26 ` 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=20140715185513.GA5331@infradead.org \
--to=hch@infradead.org \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox