Message ID | 20220920192616.808070-1-sth@linux.ibm.com (mailing list archive) |
---|---|
Headers | show |
Series | s390/dasd: add hardware copy relation | expand |
On 20.09.22 21:26, Stefan Haberland wrote: > Hi Jens, > > please apply the following patchset to for-next. > It adds basic support for a harwdare based copy relation to the DASD > device driver. Hi Stefan, How's the relation of this patchset to the current efforts of getting a common copy offload API (NVMe Simple Copy and SCSI XCOPY) into the block-layer? Thanks, Johannes
Am 21.09.22 um 09:07 schrieb Johannes Thumshirn: > On 20.09.22 21:26, Stefan Haberland wrote: >> Hi Jens, >> >> please apply the following patchset to for-next. >> It adds basic support for a harwdare based copy relation to the DASD >> device driver. > Hi Stefan, > > How's the relation of this patchset to the current efforts of getting a common > copy offload API (NVMe Simple Copy and SCSI XCOPY) into the block-layer? > > > Thanks, > Johannes Hi Johannes, there is no relation to this efforts. My patchset basically aims to add some support of IBMs Peer-to-Peer-Remote-Copy (PPRC) hardware feature to the DASD device driver. PPRC is a protocol that might be used without any OS interaction on a storage server level. This patchset allows the driver to recognize such devices correctly and allows an user to make a copy relation known to the driver. In this case Linux is only an observer/user of the copy relation which is set up by an external entity. regards, Stefan
On 21.09.22 10:23, Stefan Haberland wrote: > Am 21.09.22 um 09:07 schrieb Johannes Thumshirn: >> On 20.09.22 21:26, Stefan Haberland wrote: >>> Hi Jens, >>> >>> please apply the following patchset to for-next. >>> It adds basic support for a harwdare based copy relation to the DASD >>> device driver. >> Hi Stefan, >> >> How's the relation of this patchset to the current efforts of getting a common >> copy offload API (NVMe Simple Copy and SCSI XCOPY) into the block-layer? >> >> >> Thanks, >> Johannes > > Hi Johannes, > > there is no relation to this efforts. > My patchset basically aims to add some support of IBMs > Peer-to-Peer-Remote-Copy (PPRC) hardware feature to the DASD device driver. > PPRC is a protocol that might be used without any OS interaction on a > storage server level. > This patchset allows the driver to recognize such devices correctly and > allows an user to make a copy relation known to the driver. > In this case Linux is only an observer/user of the copy relation which > is set up by an external entity. Thanks for the clarification.
On Tue, 20 Sep 2022 21:26:09 +0200, Stefan Haberland wrote: > please apply the following patchset to for-next. > It adds basic support for a harwdare based copy relation to the DASD > device driver. > > regards, > Stefan > > [...] Applied, thanks! [1/7] s390/dasd: put block allocation in separate function commit: 2b43bf061b2e1b67561cbb1f6f305421f5fc86af [2/7] s390/dasd: add query PPRC function commit: 3f217cceb6846e7533511fc69bc774cdba37ff7d [3/7] s390/dasd: add copy pair setup commit: a91ff09d39f9b6545254839ac91f1ff7bd21d39e [4/7] s390/dasd: add copy pair swap capability commit: 413862caad6fe7fddec639219bccfdab60333551 [5/7] s390/dasd: add ioctl to perform a swap of the drivers copy pair commit: 112ff512fc654d7066936dcc06f77cc60471fdb4 [6/7] s390/dasd: suppress generic error messages for PPRC secondary devices commit: 1fca631a1185d1de9eab65ee963fec20efcc528a [7/7] s390/dasd: add device ping attribute commit: 32ff8ce08b47a5fe64ef9827443ba6cc49a659c8 Best regards,