Messages in this thread | | | Date | Wed, 27 Apr 2022 12:30:56 +0200 | Subject | Re: [PATCH v4 01/10] block: Introduce queue limits for copy-offload support | From | Hannes Reinecke <> |
| |
On 4/26/22 12:12, Nitesh Shetty wrote: > Add device limits as sysfs entries, > - copy_offload (RW) > - copy_max_bytes (RW) > - copy_max_hw_bytes (RO) > - copy_max_range_bytes (RW) > - copy_max_range_hw_bytes (RO) > - copy_max_nr_ranges (RW) > - copy_max_nr_ranges_hw (RO) > > Above limits help to split the copy payload in block layer. > copy_offload, used for setting copy offload(1) or emulation(0). > copy_max_bytes: maximum total length of copy in single payload. > copy_max_range_bytes: maximum length in a single entry. > copy_max_nr_ranges: maximum number of entries in a payload. > copy_max_*_hw_*: Reflects the device supported maximum limits. > > Signed-off-by: Nitesh Shetty <nj.shetty@samsung.com> > Signed-off-by: Kanchan Joshi <joshi.k@samsung.com> > Signed-off-by: Arnav Dawn <arnav.dawn@samsung.com> > --- > Documentation/ABI/stable/sysfs-block | 83 ++++++++++++++++ > block/blk-settings.c | 59 ++++++++++++ > block/blk-sysfs.c | 138 +++++++++++++++++++++++++++ > include/linux/blkdev.h | 13 +++ > 4 files changed, 293 insertions(+) >
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@suse.de +49 911 74053 688 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
| |