From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"linux-block\@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-nvme\@lists.infradead.org"
<linux-nvme@lists.infradead.org>,
"dm-devel\@redhat.com" <dm-devel@redhat.com>,
"lsf-pc\@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"axboe\@kernel.dk" <axboe@kernel.dk>,
"hare\@suse.de" <hare@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
Stephen Bates <sbates@raithlin.com>,
"msnitzer\@redhat.com" <msnitzer@redhat.com>,
"mpatocka\@redhat.com" <mpatocka@redhat.com>,
"zach.brown\@ni.com" <zach.brown@ni.com>,
"roland\@purestorage.com" <roland@purestorage.com>,
"rwheeler\@redhat.com" <rwheeler@redhat.com>,
"frederick.knight\@netapp.com" <frederick.knight@netapp.com>,
Matias Bjorling <Matias.Bjorling@wdc.com>
Subject: Re: [LSF/MM/BFP ATTEND] [LSF/MM/BFP TOPIC] Storage: Copy Offload
Date: Fri, 10 Jan 2020 00:33:27 -0500 [thread overview]
Message-ID: <yq1pnfrx4d4.fsf@oracle.com> (raw)
In-Reply-To: <fda88fd3-2d75-085e-ca15-a29f89c1e781@acm.org> (Bart Van Assche's message of "Wed, 8 Jan 2020 19:18:54 -0800")
Bart,
> * Copying must be supported not only within a single storage device but
> also between storage devices.
Identifying which devices to permit copies between has been challenging.
That has since been addressed in T10.
> * VMware, which uses XCOPY (with a one-byte length ID, aka LID1).
I don't think LID1 vs LID4 is particularly interesting for the Linux use
case. It's just an additional command tag since the copy manager is a
third party.
> * Microsoft, which uses ODX (aka LID4 because it has a four-byte length
> ID).
Microsoft uses the token commands.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"roland@purestorage.com" <roland@purestorage.com>,
"msnitzer@redhat.com" <msnitzer@redhat.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Matias Bjorling <Matias.Bjorling@wdc.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Stephen Bates <sbates@raithlin.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"mpatocka@redhat.com" <mpatocka@redhat.com>,
"hare@suse.de" <hare@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Keith Busch <kbusch@kernel.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"rwheeler@redhat.com" <rwheeler@redhat.com>,
Christoph Hellwig <hch@lst.de>,
"frederick.knight@netapp.com" <frederick.knight@netapp.com>,
"zach.brown@ni.com" <zach.brown@ni.com>
Subject: Re: [LSF/MM/BFP ATTEND] [LSF/MM/BFP TOPIC] Storage: Copy Offload
Date: Fri, 10 Jan 2020 00:33:27 -0500 [thread overview]
Message-ID: <yq1pnfrx4d4.fsf@oracle.com> (raw)
In-Reply-To: <fda88fd3-2d75-085e-ca15-a29f89c1e781@acm.org> (Bart Van Assche's message of "Wed, 8 Jan 2020 19:18:54 -0800")
Bart,
> * Copying must be supported not only within a single storage device but
> also between storage devices.
Identifying which devices to permit copies between has been challenging.
That has since been addressed in T10.
> * VMware, which uses XCOPY (with a one-byte length ID, aka LID1).
I don't think LID1 vs LID4 is particularly interesting for the Linux use
case. It's just an additional command tag since the copy manager is a
third party.
> * Microsoft, which uses ODX (aka LID4 because it has a four-byte length
> ID).
Microsoft uses the token commands.
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"roland@purestorage.com" <roland@purestorage.com>,
"msnitzer@redhat.com" <msnitzer@redhat.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Matias Bjorling <Matias.Bjorling@wdc.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Stephen Bates <sbates@raithlin.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"mpatocka@redhat.com" <mpatocka@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Keith Busch <kbusch@kernel.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"rwheeler@redhat.com" <rwheeler@redhat.com>,
Christoph Hellwig <hch@lst.de>,
"frederick.knight@netapp.com" <frederick.knight@netapp.com>,
"zach.brown@ni.com" <zach.brown@ni.com>
Subject: Re: [LSF/MM/BFP ATTEND] [LSF/MM/BFP TOPIC] Storage: Copy Offload
Date: Fri, 10 Jan 2020 00:33:27 -0500 [thread overview]
Message-ID: <yq1pnfrx4d4.fsf@oracle.com> (raw)
In-Reply-To: <fda88fd3-2d75-085e-ca15-a29f89c1e781@acm.org> (Bart Van Assche's message of "Wed, 8 Jan 2020 19:18:54 -0800")
Bart,
> * Copying must be supported not only within a single storage device but
> also between storage devices.
Identifying which devices to permit copies between has been challenging.
That has since been addressed in T10.
> * VMware, which uses XCOPY (with a one-byte length ID, aka LID1).
I don't think LID1 vs LID4 is particularly interesting for the Linux use
case. It's just an additional command tag since the copy manager is a
third party.
> * Microsoft, which uses ODX (aka LID4 because it has a four-byte length
> ID).
Microsoft uses the token commands.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-01-10 5:34 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200107181551epcas5p4f47eeafd807c28a26b4024245c4e00ab@epcas5p4.samsung.com>
2020-01-07 18:14 ` [LSF/MM/BFP ATTEND] [LSF/MM/BFP TOPIC] Storage: Copy Offload Chaitanya Kulkarni
2020-01-07 18:14 ` Chaitanya Kulkarni
2020-01-07 18:14 ` Chaitanya Kulkarni
2020-01-08 10:17 ` Javier González
2020-01-08 10:17 ` Javier González
2020-01-08 10:17 ` Javier González
2020-01-09 0:51 ` Logan Gunthorpe
2020-01-09 0:51 ` Logan Gunthorpe
2020-01-09 0:51 ` Logan Gunthorpe
2020-01-09 3:18 ` Bart Van Assche
2020-01-09 3:18 ` Bart Van Assche
2020-01-09 3:18 ` Bart Van Assche
2020-01-09 4:01 ` Chaitanya Kulkarni
2020-01-09 4:01 ` Chaitanya Kulkarni
2020-01-09 4:01 ` Chaitanya Kulkarni
2020-01-09 5:56 ` Damien Le Moal
2020-01-09 5:56 ` Damien Le Moal
2020-01-09 5:56 ` Damien Le Moal
2020-01-10 5:33 ` Martin K. Petersen [this message]
2020-01-10 5:33 ` Martin K. Petersen
2020-01-10 5:33 ` Martin K. Petersen
2020-01-24 14:23 ` Nikos Tsironis
2020-01-24 14:23 ` Nikos Tsironis
2020-01-24 14:23 ` Nikos Tsironis
2020-02-13 5:11 ` joshi.k
2020-02-13 5:11 ` joshi.k
2020-02-13 5:11 ` joshi.k
2020-02-13 13:09 ` Knight, Frederick
2020-02-13 13:09 ` Knight, Frederick
2020-02-13 13:09 ` Knight, Frederick
2021-05-11 0:15 Chaitanya Kulkarni
2021-05-11 0:15 ` Chaitanya Kulkarni
2021-05-11 21:15 ` Knight, Frederick
2021-05-11 21:15 ` Knight, Frederick
2021-05-12 2:21 ` Bart Van Assche
2021-05-12 2:21 ` Bart Van Assche
[not found] ` <CGME20210512071321eucas1p2ca2253e90449108b9f3e4689bf8e0512@eucas1p2.samsung.com>
2021-05-12 7:13 ` Javier González
2021-05-12 7:13 ` Javier González
2021-05-12 7:30 ` Johannes Thumshirn
2021-05-12 7:30 ` Johannes Thumshirn
[not found] ` <CGME20210928191342eucas1p23448dcd51b23495fa67cdc017e77435c@eucas1p2.samsung.com>
2021-09-28 19:13 ` Javier González
2021-09-28 19:13 ` Javier González
2021-09-29 6:44 ` Johannes Thumshirn
2021-09-29 6:44 ` Johannes Thumshirn
2021-09-30 9:43 ` Chaitanya Kulkarni
2021-09-30 9:43 ` Chaitanya Kulkarni
2021-09-30 9:53 ` Javier González
2021-09-30 9:53 ` Javier González
2021-10-06 10:01 ` Javier González
2021-10-06 10:01 ` Javier González
2021-10-13 8:35 ` Javier González
2021-10-13 8:35 ` Javier González
2021-09-30 16:20 ` Bart Van Assche
2021-09-30 16:20 ` Bart Van Assche
2021-10-06 10:05 ` Javier González
2021-10-06 10:05 ` Javier González
2021-10-06 17:33 ` Bart Van Assche
2021-10-06 17:33 ` Bart Van Assche
2021-10-08 6:49 ` Javier González
2021-10-08 6:49 ` Javier González
2021-10-29 0:21 ` Chaitanya Kulkarni
2021-10-29 5:51 ` Hannes Reinecke
2021-10-29 8:16 ` Javier González
2021-10-29 16:15 ` Bart Van Assche
2021-11-01 17:54 ` Keith Busch
2021-10-29 8:14 ` Javier González
2021-11-03 19:27 ` Javier González
2021-11-16 13:43 ` Javier González
2021-11-16 17:59 ` Bart Van Assche
2021-11-17 12:53 ` Javier González
2021-11-17 15:52 ` Bart Van Assche
2021-11-19 7:38 ` Javier González
2021-11-19 10:47 ` Kanchan Joshi
2021-11-19 15:51 ` Keith Busch
2021-11-19 16:21 ` Bart Van Assche
2021-11-22 7:39 ` Kanchan Joshi
2021-05-12 15:23 ` Hannes Reinecke
2021-05-12 15:23 ` Hannes Reinecke
2021-05-12 15:45 ` Himanshu Madhani
2021-05-12 15:45 ` Himanshu Madhani
2021-05-17 16:39 ` Kanchan Joshi
2021-05-17 16:39 ` Kanchan Joshi
2021-05-18 0:15 ` Bart Van Assche
2021-05-18 0:15 ` Bart Van Assche
2021-06-11 6:03 ` Chaitanya Kulkarni
2021-06-11 6:03 ` Chaitanya Kulkarni
2021-06-11 15:35 ` Nikos Tsironis
2021-06-11 15:35 ` Nikos Tsironis
[not found] <CGME20220127071544uscas1p2f70f4d2509f3ebd574b7ed746d3fa551@uscas1p2.samsung.com>
2022-01-27 7:14 ` Chaitanya Kulkarni
2022-01-28 19:59 ` Adam Manzanares
2022-01-31 11:49 ` Johannes Thumshirn
2022-01-31 19:03 ` Bart Van Assche
2022-02-01 1:54 ` Luis Chamberlain
2022-02-01 10:21 ` Javier González
2022-02-07 9:57 ` Nitesh Shetty
2022-02-02 5:57 ` Kanchan Joshi
2022-02-07 10:45 ` David Disseldorp
2022-03-01 17:34 ` Nikos Tsironis
2022-03-01 21:32 ` Chaitanya Kulkarni
2022-03-03 18:36 ` Nikos Tsironis
2022-03-08 20:48 ` Nikos Tsironis
2022-03-09 8:51 ` Mikulas Patocka
2022-03-09 15:49 ` Nikos Tsironis
[not found] <CGME20230113094723epcas5p2f6f81ca1ad85f4b26829b87f8ec301ce@epcas5p2.samsung.com>
2023-01-13 9:46 ` Nitesh Shetty
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=yq1pnfrx4d4.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=frederick.knight@netapp.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mpatocka@redhat.com \
--cc=msnitzer@redhat.com \
--cc=roland@purestorage.com \
--cc=rwheeler@redhat.com \
--cc=sbates@raithlin.com \
--cc=zach.brown@ni.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.