linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Nitesh Shetty <nj.shetty@samsung.com>,
	Jens Axboe <axboe@kernel.dk>, Jonathan Corbet <corbet@lwn.net>,
	Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	dm-devel@redhat.com, Keith Busch <kbusch@kernel.org>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>
Cc: martin.petersen@oracle.com, linux-doc@vger.kernel.org,
	gost.dev@samsung.com, Anuj Gupta <anuj20.g@samsung.com>,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
	linux-block@vger.kernel.org, mcgrof@kernel.org,
	dlemoal@kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [dm-devel] [PATCH v14 02/11] Add infrastructure for copy offload in block and request layer.
Date: Fri, 11 Aug 2023 14:58:36 -0700	[thread overview]
Message-ID: <355bb623-9cd9-fe33-106e-1f091c09fb32@acm.org> (raw)
In-Reply-To: <20230811105300.15889-3-nj.shetty@samsung.com>

On 8/11/23 03:52, Nitesh Shetty wrote:
> We expect caller to take a plug and send bio with source information,
> followed by bio with destination information.
> Once the src bio arrives we form a request and wait for destination
> bio. Upon arrival of destination we merge these two bio's and send
> corresponding request down to device driver.

Is the above description up-to-date? In the cover letter there is a 
different description of how copy offloading works.

Thanks,

Bart.

  parent reply	other threads:[~2023-08-11 21:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230811105627epcas5p1aa1ef0e58bcd0fc05a072c8b40dcfb96@epcas5p1.samsung.com>
2023-08-11 10:52 ` [PATCH v14 00/11] Implement copy offload support Nitesh Shetty
     [not found]   ` <CGME20230811105638epcas5p4db95584b6a432ea4b8b93e060a95e5f1@epcas5p4.samsung.com>
2023-08-11 10:52     ` [PATCH v14 01/11] block: Introduce queue limits and sysfs for copy-offload support Nitesh Shetty
2023-08-11 21:56       ` [dm-devel] " Bart Van Assche
2023-08-14 10:35         ` Nitesh Shetty
     [not found]   ` <CGME20230811105648epcas5p3ae8b8f6ed341e2aa253e8b4de8920a4d@epcas5p3.samsung.com>
2023-08-11 10:52     ` [PATCH v14 02/11] Add infrastructure for copy offload in block and request layer Nitesh Shetty
2023-08-11 21:25       ` [dm-devel] " Bart Van Assche
2023-08-14 12:18         ` Nitesh Shetty
2023-08-14 14:26           ` Bart Van Assche
2023-08-15  7:50             ` Nitesh Shetty
2023-08-11 21:58       ` Bart Van Assche [this message]
2023-08-14 12:09         ` Nitesh Shetty
     [not found]   ` <CGME20230811105659epcas5p1982eeaeb580c4cb9b23a29270945be08@epcas5p1.samsung.com>
2023-08-11 10:52     ` [PATCH v14 03/11] block: add copy offload support Nitesh Shetty
2023-08-11 21:33       ` [dm-devel] " Bart Van Assche
2023-08-14 17:01         ` Nitesh Shetty
2023-08-11 22:06       ` Bart Van Assche
2023-08-14 10:30         ` Nitesh Shetty
     [not found]   ` <CGME20230811105713epcas5p3b5323a0c553006e60671dde6c72fc4c6@epcas5p3.samsung.com>
2023-08-11 10:52     ` [PATCH v14 04/11] block: add emulation for copy Nitesh Shetty
2023-08-11 22:11       ` [dm-devel] " Bart Van Assche
2023-08-14 16:58         ` Nitesh Shetty
     [not found]   ` <CGME20230811105723epcas5p468fa65dc9c5bea39d40359ce55bcd9aa@epcas5p4.samsung.com>
2023-08-11 10:52     ` [PATCH v14 05/11] fs/read_write: Enable copy_file_range for block device Nitesh Shetty
     [not found]   ` <CGME20230811105734epcas5p1b465394a301ba85f2c52ed7fde334f52@epcas5p1.samsung.com>
2023-08-11 10:52     ` [PATCH v14 06/11] fs, block: copy_file_range for def_blk_ops for direct " Nitesh Shetty
     [not found]   ` <CGME20230811105745epcas5p451c58384792038c13e9891fb2680050b@epcas5p4.samsung.com>
2023-08-11 10:52     ` [PATCH v14 07/11] nvme: add copy offload support Nitesh Shetty
2023-08-11 23:39       ` kernel test robot
     [not found]   ` <CGME20230811105756epcas5p46a7e3f00c33e912e76848c989fc8eac2@epcas5p4.samsung.com>
2023-08-11 10:52     ` [PATCH v14 08/11] nvmet: add copy command support for bdev and file ns Nitesh Shetty
     [not found]   ` <CGME20230811105808epcas5p4a9f9573d15f642a73bac46153bb935d2@epcas5p4.samsung.com>
2023-08-11 10:52     ` [PATCH v14 09/11] dm: Add support for copy offload Nitesh Shetty
     [not found]   ` <CGME20230811105819epcas5p40ddff0991c70b6d80d516dfe055bd673@epcas5p4.samsung.com>
2023-08-11 10:52     ` [PATCH v14 10/11] dm: Enable copy offload for dm-linear target Nitesh Shetty
     [not found]   ` <CGME20230811105830epcas5p37a477e5e7b006613549647bebdf4d028@epcas5p3.samsung.com>
2023-08-11 10:52     ` [PATCH v14 11/11] null_blk: add support for copy offload Nitesh Shetty
2023-08-11 17:16       ` kernel test robot
2023-08-11 21:15       ` kernel test robot
2023-08-11 21:50   ` [dm-devel] [PATCH v14 00/11] Implement copy offload support Bart Van Assche
2023-08-14 16:55     ` 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=355bb623-9cd9-fe33-106e-1f091c09fb32@acm.org \
    --to=bvanassche@acm.org \
    --cc=agk@redhat.com \
    --cc=anuj20.g@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dlemoal@kernel.org \
    --cc=dm-devel@redhat.com \
    --cc=gost.dev@samsung.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martin.petersen@oracle.com \
    --cc=mcgrof@kernel.org \
    --cc=nj.shetty@samsung.com \
    --cc=sagi@grimberg.me \
    --cc=snitzer@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).