Re: [PATCH 2/4] scatterlist: add sgl_copy_sgl() function

2020-10-16 Thread Douglas Gilbert
On 2020-10-16 7:17 a.m., Bodo Stroesser wrote: Hi Douglas, AFAICS this patch - and also patch 3 - are not correct. When started with SG_MITER_ATOMIC, sg_miter_next and sg_miter_stop use the k(un)map_atomic calls. But these have to be used strictly nested according to docu and code. The below cod

Re: [PATCH 2/4] scatterlist: add sgl_copy_sgl() function

2020-10-16 Thread Bodo Stroesser
Hi Douglas, AFAICS this patch - and also patch 3 - are not correct. When started with SG_MITER_ATOMIC, sg_miter_next and sg_miter_stop use the k(un)map_atomic calls. But these have to be used strictly nested according to docu and code. The below code uses the atomic mappings in overlapping mode.

[PATCH 2/4] scatterlist: add sgl_copy_sgl() function

2020-10-15 Thread Douglas Gilbert
Both the SCSI and NVMe subsystems receive user data from the block layer in scatterlist_s (aka scatter gather lists (sgl) which are often arrays). If drivers in those subsystems represent storage (e.g. a ramdisk) or cache "hot" user data then they may also choose to use scatterlist_s. Currently the