From: SelvaKumar S <selvakuma.s1@samsung.com> To: linux-nvme@lists.infradead.org Cc: kbusch@kernel.org, axboe@kernel.dk, damien.lemoal@wdc.com, hch@lst.de, sagi@grimberg.me, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, selvajove@gmail.com, nj.shetty@samsung.com, joshi.k@samsung.com, javier.gonz@samsung.com, SelvaKumar S <selvakuma.s1@samsung.com> Subject: [RFC PATCH 0/2] add simple copy support Date: Tue, 1 Dec 2020 11:09:47 +0530 [thread overview] Message-ID: <20201201053949.143175-1-selvakuma.s1@samsung.com> (raw) In-Reply-To: CGME20201201054049epcas5p2e0118abda14aaf8d8bdcfb543bc330fc@epcas5p2.samsung.com This patchset tries to add support for TP4065a ("Simple Copy Command"), v2020.05.04 ("Ratified") The Specification can be found in following link. https://nvmexpress.org/wp-content/uploads/NVM-Express-1.4-Ratified-TPs-1.zip This is an RFC. Looking forward for any feedbacks or other alternate designs for plumbing simple copy to IO stack. Simple copy command is a copy offloading operation and is used to copy multiple contiguous ranges (source_ranges) of LBA's to a single destination LBA within the device reducing traffic between host and device. This implementation accepts destination, no of sources and arrays of source ranges from application and attach it as payload to the bio and submits to the device. Following limits are added to queue limits and are exposed in sysfs to userspace - *max_copy_sectors* limits the sum of all source_range length - *max_copy_nr_ranges* limits the number of source ranges - *max_copy_range_sectors* limit the maximum number of sectors that can constitute a single source range. SelvaKumar S (2): block: add simple copy support nvme: add simple copy support block/blk-core.c | 104 +++++++++++++++++++++++++++++++--- block/blk-lib.c | 116 ++++++++++++++++++++++++++++++++++++++ block/blk-merge.c | 2 + block/blk-settings.c | 11 ++++ block/blk-sysfs.c | 23 ++++++++ block/blk-zoned.c | 1 + block/bounce.c | 1 + block/ioctl.c | 43 ++++++++++++++ drivers/nvme/host/core.c | 91 ++++++++++++++++++++++++++++++ drivers/nvme/host/nvme.h | 4 ++ include/linux/bio.h | 1 + include/linux/blk_types.h | 7 +++ include/linux/blkdev.h | 15 +++++ include/linux/nvme.h | 45 +++++++++++++-- include/uapi/linux/fs.h | 21 +++++++ 15 files changed, 473 insertions(+), 12 deletions(-) -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: SelvaKumar S <selvakuma.s1@samsung.com> To: linux-nvme@lists.infradead.org Cc: axboe@kernel.dk, damien.lemoal@wdc.com, SelvaKumar S <selvakuma.s1@samsung.com>, sagi@grimberg.me, joshi.k@samsung.com, selvajove@gmail.com, linux-kernel@vger.kernel.org, nj.shetty@samsung.com, linux-block@vger.kernel.org, kbusch@kernel.org, javier.gonz@samsung.com, hch@lst.de Subject: [RFC PATCH 0/2] add simple copy support Date: Tue, 1 Dec 2020 11:09:47 +0530 [thread overview] Message-ID: <20201201053949.143175-1-selvakuma.s1@samsung.com> (raw) In-Reply-To: CGME20201201054049epcas5p2e0118abda14aaf8d8bdcfb543bc330fc@epcas5p2.samsung.com This patchset tries to add support for TP4065a ("Simple Copy Command"), v2020.05.04 ("Ratified") The Specification can be found in following link. https://nvmexpress.org/wp-content/uploads/NVM-Express-1.4-Ratified-TPs-1.zip This is an RFC. Looking forward for any feedbacks or other alternate designs for plumbing simple copy to IO stack. Simple copy command is a copy offloading operation and is used to copy multiple contiguous ranges (source_ranges) of LBA's to a single destination LBA within the device reducing traffic between host and device. This implementation accepts destination, no of sources and arrays of source ranges from application and attach it as payload to the bio and submits to the device. Following limits are added to queue limits and are exposed in sysfs to userspace - *max_copy_sectors* limits the sum of all source_range length - *max_copy_nr_ranges* limits the number of source ranges - *max_copy_range_sectors* limit the maximum number of sectors that can constitute a single source range. SelvaKumar S (2): block: add simple copy support nvme: add simple copy support block/blk-core.c | 104 +++++++++++++++++++++++++++++++--- block/blk-lib.c | 116 ++++++++++++++++++++++++++++++++++++++ block/blk-merge.c | 2 + block/blk-settings.c | 11 ++++ block/blk-sysfs.c | 23 ++++++++ block/blk-zoned.c | 1 + block/bounce.c | 1 + block/ioctl.c | 43 ++++++++++++++ drivers/nvme/host/core.c | 91 ++++++++++++++++++++++++++++++ drivers/nvme/host/nvme.h | 4 ++ include/linux/bio.h | 1 + include/linux/blk_types.h | 7 +++ include/linux/blkdev.h | 15 +++++ include/linux/nvme.h | 45 +++++++++++++-- include/uapi/linux/fs.h | 21 +++++++ 15 files changed, 473 insertions(+), 12 deletions(-) -- 2.25.1 _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next parent reply other threads:[~2020-12-01 7:12 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20201201054049epcas5p2e0118abda14aaf8d8bdcfb543bc330fc@epcas5p2.samsung.com> 2020-12-01 5:39 ` SelvaKumar S [this message] 2020-12-01 5:39 ` [RFC PATCH 0/2] add simple copy support SelvaKumar S [not found] ` <CGME20201201054057epcas5p1d5bd2813146d2cb57eb66b7cedce1f63@epcas5p1.samsung.com> 2020-12-01 5:39 ` [RFC PATCH 1/2] block: " SelvaKumar S 2020-12-01 5:39 ` SelvaKumar S 2020-12-01 9:37 ` kernel test robot 2020-12-01 9:57 ` Johannes Thumshirn 2020-12-01 9:57 ` Johannes Thumshirn 2020-12-01 10:28 ` Aleksei Marov 2020-12-01 10:28 ` Aleksei Marov 2020-12-01 13:22 ` Selva Jove 2020-12-01 13:22 ` Selva Jove [not found] ` <CGME20201201054106epcas5p486fa3f85f6ba5568f6df85c2660b2e3e@epcas5p4.samsung.com> 2020-12-01 5:39 ` [RFC PATCH 2/2] nvme: " SelvaKumar S 2020-12-01 5:39 ` SelvaKumar S 2020-12-01 15:16 ` Keith Busch 2020-12-01 15:16 ` Keith Busch 2020-12-02 8:29 ` Selva Jove 2020-12-02 8:29 ` Selva Jove 2020-12-01 11:22 ` [RFC PATCH 0/2] " Damien Le Moal 2020-12-01 11:22 ` [dm-devel] " Damien Le Moal 2020-12-01 11:22 ` Damien Le Moal 2020-12-01 12:20 ` javier.gonz@samsung.com 2020-12-01 12:20 ` [dm-devel] " javier.gonz@samsung.com 2020-12-01 12:20 ` javier.gonz@samsung.com
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=20201201053949.143175-1-selvakuma.s1@samsung.com \ --to=selvakuma.s1@samsung.com \ --cc=axboe@kernel.dk \ --cc=damien.lemoal@wdc.com \ --cc=hch@lst.de \ --cc=javier.gonz@samsung.com \ --cc=joshi.k@samsung.com \ --cc=kbusch@kernel.org \ --cc=linux-block@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=nj.shetty@samsung.com \ --cc=sagi@grimberg.me \ --cc=selvajove@gmail.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: linkBe 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.