linux-kernel - ANNOUNCE: SCSI XCOPY support for the kernel and device mapper

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.02.1407151359430.5499@file01.intranet.prod.int.rdu2.redhat.com>
Date:	Tue, 15 Jul 2014 14:33:13 -0400 (EDT)
From:	Mikulas Patocka <mpatocka@...hat.com>
To:	"Alasdair G. Kergon" <agk@...hat.com>,
	Mike Snitzer <msnitzer@...hat.com>,
	Jonathan Brassow <jbrassow@...hat.com>,
	Edward Thornber <thornber@...hat.com>,
	"Martin K. Petersen" <martin.petersen@...cle.com>,
	Jens Axboe <axboe@...nel.dk>
cc:	dm-devel@...hat.com, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org
Subject: ANNOUNCE: SCSI XCOPY support for the kernel and device mapper

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.

It is based on Martin Petersen's work 
https://git.kernel.org/cgit/linux/kernel/git/mkp/linux.git/commit/?h=xcopy&id=0bdeed274e16b3038a851552188512071974eea8, 
but it is changed significantly so that it is possible to propagate XCOPY 
bios through the device mapper stack.

The basic architecture is this: in the function blkdev_issue_copy we 
create two bios, one for read and one for write (with bi_rw READ|REQ_COPY 
and WRITE|REQ_COPY). Both bios have a pointer to the same bio_copy 
structure. These two bios travel independently through the device mapper 
stack - each bio can go through different device mapper devices. When both 
the bios reach the physical block device (in the function blk_queue_bio) 
the bio pair is collected and a XCOPY request is allocated and sent to the 
scsi disk driver.

Note that because device mapper mapping can dynamically change, there no 
guarantee that the XCOPY command succeeds. If it ends with an error, the 
caller is supposed to perform the copying manually.

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.

There is a new ioctl BLKCOPY that makes it possible to use copy offload 
from userspace.

Mikulas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/