Re: [PATCH v4 0/9] null_blk fixes, improvements and cleanup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/19/20 6:55 PM, Damien Le Moal wrote:
> Jens,
> 
> This series provides fixes and improvements for null_blk.
> 
> The first two patches are bug fixes which likely should go into 5.10.
> The first patch fixes a problem with zone initialization when the
> device capacity is not a multiple of the zone size and the second
> patch fixes zone append handling.
> 
> The following patches are improvements and cleanups:
> * Patch 3 makes sure that the device max_sectors limit is aligned to the
>   block size.
> * Patch 4 improves zone locking overall, and especially the memory
>   backing disabled case by introducing a spinlock array to implement a
>   per zone lock in place of a global lock. With this patch, write
>   performance remains mostly unchanged, but read performance with a
>   multi-queue setup more than double from 1.3 MIOPS to 3.3 MIOPS (4K
>   random reads to zones with fio zonemode=zbd).
> * Patch 5 improves implicit zone close
> * Patch 6 and 7 cleanup discard handling code and use that code to free
>   the memory backing a zone that is being reset.
> * Patch 8 adds the max_sectors configuration option to allow changing
>   the max_sectors/max_hw_sectors of the device.
> * Finally, patch 9 moves nullblk into its own directory under
>   drivers/block/null_blk/

Applied, thanks.

-- 
Jens Axboe




[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux