From: Selva Jove <selvajove@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: SelvaKumar S <selvakuma.s1@samsung.com>,
linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
axboe@kernel.dk, Damien Le Moal <damien.lemoal@wdc.com>,
hch@lst.de, sagi@grimberg.me, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, dm-devel@redhat.com,
snitzer@redhat.com, joshiiitr@gmail.com, nj.shetty@samsung.com,
joshi.k@samsung.com, javier.gonz@samsung.com, kch@kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH v5 0/4] add simple copy support
Date: Tue, 23 Feb 2021 14:44:08 +0530 [thread overview]
Message-ID: <CAHqX9vbG-cB0h25y4OhcdOEegn-_E=HwHJtkPFGaurEF9-KXPw@mail.gmail.com> (raw)
In-Reply-To: <20210221235248.GZ4626@dread.disaster.area>
Dave,
copy_file_range() is work under progress. FALLOC_FL_UNSHARE of fallocate()
use case sounds interesting. I will try to address both of them in the
next series.
Adding SCSI_XCOPY() support is not in the scope of this patchset. However
blkdev_issue_copy() interface is made generic so that it is possible to extend
to cross device XCOPY in future.
Thanks,
Selva
WARNING: multiple messages have this Message-ID (diff)
From: Selva Jove <selvajove@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: axboe@kernel.dk, Damien Le Moal <damien.lemoal@wdc.com>,
kch@kernel.org, SelvaKumar S <selvakuma.s1@samsung.com>,
sagi@grimberg.me, snitzer@redhat.com,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
nj.shetty@samsung.com, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, dm-devel@redhat.com,
joshi.k@samsung.com, javier.gonz@samsung.com,
Keith Busch <kbusch@kernel.org>,
joshiiitr@gmail.com, hch@lst.de
Subject: Re: [RFC PATCH v5 0/4] add simple copy support
Date: Tue, 23 Feb 2021 14:44:08 +0530 [thread overview]
Message-ID: <CAHqX9vbG-cB0h25y4OhcdOEegn-_E=HwHJtkPFGaurEF9-KXPw@mail.gmail.com> (raw)
In-Reply-To: <20210221235248.GZ4626@dread.disaster.area>
Dave,
copy_file_range() is work under progress. FALLOC_FL_UNSHARE of fallocate()
use case sounds interesting. I will try to address both of them in the
next series.
Adding SCSI_XCOPY() support is not in the scope of this patchset. However
blkdev_issue_copy() interface is made generic so that it is possible to extend
to cross device XCOPY in future.
Thanks,
Selva
_______________________________________________
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: Selva Jove <selvajove@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: axboe@kernel.dk, Damien Le Moal <damien.lemoal@wdc.com>,
kch@kernel.org, SelvaKumar S <selvakuma.s1@samsung.com>,
sagi@grimberg.me, snitzer@redhat.com,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
nj.shetty@samsung.com, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, dm-devel@redhat.com,
joshi.k@samsung.com, javier.gonz@samsung.com,
Keith Busch <kbusch@kernel.org>,
joshiiitr@gmail.com, hch@lst.de
Subject: Re: [dm-devel] [RFC PATCH v5 0/4] add simple copy support
Date: Tue, 23 Feb 2021 14:44:08 +0530 [thread overview]
Message-ID: <CAHqX9vbG-cB0h25y4OhcdOEegn-_E=HwHJtkPFGaurEF9-KXPw@mail.gmail.com> (raw)
In-Reply-To: <20210221235248.GZ4626@dread.disaster.area>
Dave,
copy_file_range() is work under progress. FALLOC_FL_UNSHARE of fallocate()
use case sounds interesting. I will try to address both of them in the
next series.
Adding SCSI_XCOPY() support is not in the scope of this patchset. However
blkdev_issue_copy() interface is made generic so that it is possible to extend
to cross device XCOPY in future.
Thanks,
Selva
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-02-23 9:15 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210219124555epcas5p1334e7c4d64ada5dc4a2ca0feb48c1d44@epcas5p1.samsung.com>
2021-02-19 12:45 ` [RFC PATCH v5 0/4] add simple copy support SelvaKumar S
2021-02-19 12:45 ` [dm-devel] " SelvaKumar S
2021-02-19 12:45 ` SelvaKumar S
[not found] ` <CGME20210219124559epcas5p41da46f1c248e334953d407a154697903@epcas5p4.samsung.com>
2021-02-19 12:45 ` [RFC PATCH v5 1/4] block: make bio_map_kern() non static SelvaKumar S
2021-02-19 12:45 ` [dm-devel] " SelvaKumar S
2021-02-19 12:45 ` SelvaKumar S
[not found] ` <CGME20210219124603epcas5p33add0f2c1781b2a4d71bf30c9e1ac647@epcas5p3.samsung.com>
2021-02-19 12:45 ` [RFC PATCH v5 2/4] block: add simple copy support SelvaKumar S
2021-02-19 12:45 ` [dm-devel] " SelvaKumar S
2021-02-19 12:45 ` SelvaKumar S
2021-02-20 4:59 ` Damien Le Moal
2021-02-20 4:59 ` [dm-devel] " Damien Le Moal
2021-02-20 4:59 ` Damien Le Moal
2021-04-07 11:32 ` Selva Jove
2021-04-07 11:32 ` [dm-devel] " Selva Jove
2021-04-07 11:32 ` Selva Jove
2021-04-12 0:24 ` Damien Le Moal
2021-04-12 0:24 ` [dm-devel] " Damien Le Moal
2021-04-12 0:24 ` Damien Le Moal
2021-04-12 14:34 ` Selva Jove
2021-04-12 14:34 ` [dm-devel] " Selva Jove
2021-04-12 14:34 ` Selva Jove
2021-04-13 0:32 ` Damien Le Moal
2021-04-13 0:32 ` [dm-devel] " Damien Le Moal
2021-04-13 0:32 ` Damien Le Moal
2021-04-14 6:58 ` Selva Jove
2021-04-14 6:58 ` [dm-devel] " Selva Jove
2021-04-14 6:58 ` Selva Jove
2021-02-20 5:24 ` kernel test robot
[not found] ` <CGME20210219124608epcas5p2a673f9e00c3e7b5352f115497b0e2d98@epcas5p2.samsung.com>
2021-02-19 12:45 ` [RFC PATCH v5 3/4] nvme: " SelvaKumar S
2021-02-19 12:45 ` [dm-devel] " SelvaKumar S
2021-02-19 12:45 ` SelvaKumar S
2021-02-20 3:36 ` Matthew Wilcox
2021-02-20 3:36 ` [dm-devel] " Matthew Wilcox
2021-02-20 3:36 ` Matthew Wilcox
2021-02-22 15:57 ` Selva Jove
2021-02-22 15:57 ` [dm-devel] " Selva Jove
2021-02-22 15:57 ` Selva Jove
[not found] ` <CGME20210219124611epcas5p1c775b63b537e75da161556e375fcf05e@epcas5p1.samsung.com>
2021-02-19 12:45 ` [RFC PATCH v5 4/4] dm kcopyd: add simple copy offload support SelvaKumar S
2021-02-19 12:45 ` [dm-devel] " SelvaKumar S
2021-02-19 12:45 ` SelvaKumar S
2021-02-22 5:28 ` Dan Carpenter
2021-02-22 5:28 ` Dan Carpenter
2021-02-20 18:01 ` [RFC PATCH v5 0/4] add simple copy support David Laight
2021-02-20 18:01 ` [dm-devel] " David Laight
2021-02-20 18:01 ` David Laight
2021-02-20 19:08 ` Matthew Wilcox
2021-02-20 19:08 ` [dm-devel] " Matthew Wilcox
2021-02-20 19:08 ` Matthew Wilcox
2021-02-20 19:19 ` Keith Busch
2021-02-20 19:19 ` [dm-devel] " Keith Busch
2021-02-20 19:19 ` Keith Busch
2021-02-21 23:52 ` Dave Chinner
2021-02-21 23:52 ` [dm-devel] " Dave Chinner
2021-02-21 23:52 ` Dave Chinner
2021-02-23 9:14 ` Selva Jove [this message]
2021-02-23 9:14 ` [dm-devel] " Selva Jove
2021-02-23 9:14 ` Selva Jove
2021-02-22 1:31 ` Ming Lei
2021-02-22 1:31 ` [dm-devel] " Ming Lei
2021-02-22 1:31 ` Ming Lei
2021-02-22 6:52 ` Su Yue
2021-02-22 6:52 ` [dm-devel] " Su Yue
2021-02-22 6:52 ` Su Yue
2021-02-23 9:00 ` Selva Jove
2021-02-23 9:00 ` [dm-devel] " Selva Jove
2021-02-23 9:00 ` Selva Jove
2021-04-10 0:21 ` Max Gurtovoy
2021-04-10 0:21 ` [dm-devel] " Max Gurtovoy
2021-04-10 0:21 ` Max Gurtovoy
2021-04-10 0:29 ` Chaitanya Kulkarni
2021-04-10 0:29 ` [dm-devel] " Chaitanya Kulkarni
2021-04-10 0:29 ` Chaitanya Kulkarni
2021-04-10 6:32 ` Javier González
2021-04-10 6:32 ` [dm-devel] " Javier González
2021-04-10 6:32 ` Javier González
2021-04-11 9:10 ` Max Gurtovoy
2021-04-11 9:10 ` [dm-devel] " Max Gurtovoy
2021-04-11 9:10 ` Max Gurtovoy
2021-04-11 19:26 ` Javier González
2021-04-11 19:26 ` [dm-devel] " Javier González
2021-04-11 19:26 ` Javier González
2021-04-13 15:38 ` Max Gurtovoy
2021-04-13 15:38 ` [dm-devel] " Max Gurtovoy
2021-04-13 15:38 ` Max Gurtovoy
2021-04-13 18:25 ` Javier González
2021-04-13 18:25 ` [dm-devel] " Javier González
2021-04-13 18:25 ` Javier González
2021-04-13 18:36 ` Chaitanya Kulkarni
2021-04-13 18:36 ` [dm-devel] " Chaitanya Kulkarni
2021-04-13 18:36 ` Chaitanya Kulkarni
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='CAHqX9vbG-cB0h25y4OhcdOEegn-_E=HwHJtkPFGaurEF9-KXPw@mail.gmail.com' \
--to=selvajove@gmail.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=david@fromorbit.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=joshi.k@samsung.com \
--cc=joshiiitr@gmail.com \
--cc=kbusch@kernel.org \
--cc=kch@kernel.org \
--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=nj.shetty@samsung.com \
--cc=sagi@grimberg.me \
--cc=selvakuma.s1@samsung.com \
--cc=snitzer@redhat.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.