Hi Linus,
This pull is based on an earlier subset of changes that you already
pulled in for 6.5 via the block tree.
The following changes since commit 245165658e1c9f95c0fecfe02b9b1ebd30a1198a:
blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none
(2023-06-16 10:12:25 -0600)
Hi Nitesh,
On Wed, Jun 28, 2023 at 12:06:17AM +0530, Nitesh Shetty wrote:
> For the devices which does not support copy, copy emulation is added.
> It is required for in-kernel users like fabrics, where file descriptor is
I can understand copy command does help for FS GC and fabrics storages,
On 23/06/28 03:45PM, Damien Le Moal wrote:
On 6/28/23 03:36, Nitesh Shetty wrote:
Introduce blkdev_copy_offload which takes similar arguments as
copy_file_range and performs copy offload between two bdevs.
I am confused... I thought it was discussed to only allow copy offload only
within a
On 23/06/28 03:50PM, Damien Le Moal wrote:
On 6/28/23 03:36, Nitesh Shetty wrote:
For the devices which does not support copy, copy emulation is added.
It is required for in-kernel users like fabrics, where file descriptor is
not available and hence they can't use copy_file_range.
On 23/06/28 03:51PM, Damien Le Moal wrote:
On 6/28/23 03:36, Nitesh Shetty wrote:
For direct block device opened with O_DIRECT, use copy_file_range to
issue device copy offload, and fallback to generic_copy_file_range incase
device copy offload capability is absent.
...if the device does not
On 23/06/28 03:40PM, Damien Le Moal wrote:
On 6/28/23 03:36, Nitesh Shetty wrote:
Add device limits as sysfs entries,
- copy_offload (RW)
- copy_max_bytes (RW)
- copy_max_bytes_hw (RO)
Above limits help to split the copy payload in block layer.
copy_offload: used for
