public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Nitesh Shetty <nj.shetty@samsung.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: axboe@kernel.dk, agk@redhat.com, snitzer@kernel.org,
	dm-devel@redhat.com, kbusch@kernel.org, hch@lst.de,
	sagi@grimberg.me, james.smart@broadcom.com, kch@nvidia.com,
	naohiro.aota@wdc.com, jth@kernel.org, viro@zeniv.linux.org.uk,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvme@lists.infradead.org, linux-fsdevel@vger.kernel.org,
	anuj20.g@samsung.com, joshi.k@samsung.com, p.raghav@samsung.com,
	nitheshshetty@gmail.com, gost.dev@samsung.com
Subject: Re: [PATCH v5 10/10] fs: add support for copy file range in zonefs
Date: Wed, 30 Nov 2022 09:47:28 +0530	[thread overview]
Message-ID: <20221130041728.GB17533@test-zns> (raw)
In-Reply-To: <b22652ee-9cca-a5b1-e9f1-862ed8f0354d@opensource.wdc.com>

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

On Wed, Nov 30, 2022 at 08:45:55AM +0900, Damien Le Moal wrote:
> On 11/29/22 21:22, Nitesh Shetty wrote:
> > Acked. I do see a gap in current zonefs cfr implementation. I will drop this
> 
> cfr ?
>

yes, will drop zonefs cfr for next version.

> > implementation for next version. Once we finalize on block copy offload
> > implementation, will re-pick this and send with above reviews fixed.
> > 
> > Thank you,
> > Nitesh
> 
> Please trim your replies.
> 

Noted

> 
> -- 
> Damien Le Moal
> Western Digital Research
> 
> 

Thanks,
Nitesh Shetty

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2022-11-30  4:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221123061010epcas5p21cef9d23e4362b01f2b19d1117e1cdf5@epcas5p2.samsung.com>
2022-11-23  5:58 ` [PATCH v5 00/10] Implement copy offload support Nitesh Shetty
2022-11-23  5:58   ` [PATCH v5 01/10] block: Introduce queue limits for copy-offload support Nitesh Shetty
2022-11-23  5:58   ` [PATCH v5 02/10] block: Add copy offload support infrastructure Nitesh Shetty
2022-11-23  8:04     ` Ming Lei
2022-11-23 10:07       ` Nitesh Shetty
2022-11-24  0:03         ` Ming Lei
2022-11-29 11:44           ` Nitesh Shetty
2022-12-07  5:54             ` Nitesh Shetty
2022-12-07 11:19               ` Ming Lei
2022-12-09  8:16                 ` Nitesh Shetty
2022-11-23  5:58   ` [PATCH v5 03/10] block: add emulation for copy Nitesh Shetty
2022-11-23  5:58   ` [PATCH v5 04/10] block: Introduce a new ioctl " Nitesh Shetty
2022-11-23  5:58   ` [PATCH v5 05/10] nvme: add copy offload support Nitesh Shetty
2022-11-23  5:58   ` [PATCH v5 06/10] nvmet: add copy command support for bdev and file ns Nitesh Shetty
     [not found]     ` <482586a3-f45d-a17b-7630-341fb0e1ee96@linux.alibaba.com>
2022-11-23  9:39       ` Nitesh Shetty
2022-12-06  9:22     ` kernel test robot
2022-11-23  5:58   ` [PATCH v5 07/10] dm: Add support for copy offload Nitesh Shetty
2022-11-23  5:58   ` [PATCH v5 08/10] dm: Enable copy offload for dm-linear target Nitesh Shetty
2022-11-23  5:58   ` [PATCH v5 09/10] dm kcopyd: use copy offload support Nitesh Shetty
2022-11-23  5:58   ` [PATCH v5 10/10] fs: add support for copy file range in zonefs Nitesh Shetty
2022-11-23  6:53     ` Amir Goldstein
2022-11-23 10:13       ` Nitesh Shetty
2022-11-24  1:32     ` Damien Le Moal
2022-11-24  1:47       ` Damien Le Moal
2022-11-25  4:18         ` Al Viro
2022-11-29 12:22         ` Nitesh Shetty
2022-11-29 23:45           ` Damien Le Moal
2022-11-30  4:17             ` Nitesh Shetty [this message]
2022-11-30  9:55               ` Damien Le Moal
2022-11-23 22:56   ` [PATCH v5 00/10] Implement copy offload support Chaitanya Kulkarni
2022-11-29 12:16     ` Nitesh Shetty
2022-11-30  0:05       ` Chaitanya Kulkarni
2022-11-30  4:14         ` 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=20221130041728.GB17533@test-zns \
    --to=nj.shetty@samsung.com \
    --cc=agk@redhat.com \
    --cc=anuj20.g@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dm-devel@redhat.com \
    --cc=gost.dev@samsung.com \
    --cc=hch@lst.de \
    --cc=james.smart@broadcom.com \
    --cc=joshi.k@samsung.com \
    --cc=jth@kernel.org \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=naohiro.aota@wdc.com \
    --cc=nitheshshetty@gmail.com \
    --cc=p.raghav@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