Re: [PATCH v10 06/41] btrfs: introduce max_zone_append_size

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

 



On Thu, Nov 19, 2020 at 05:23:20PM +0800, Anand Jain wrote:
> On 10/11/20 7:26 pm, Naohiro Aota wrote:
> > The zone append write command has a maximum IO size restriction it
> > accepts. This is because a zone append write command cannot be split, as
> > we ask the device to place the data into a specific target zone and the
> > device responds with the actual written location of the data.
> > 
> > Introduce max_zone_append_size to zone_info and fs_info to track the
> > value, so we can limit all I/O to a zoned block device that we want to
> > write using the zone append command to the device's limits.
> > 
> > Reviewed-by: Josef Bacik <josef@xxxxxxxxxxxxxx>
> > Signed-off-by: Naohiro Aota <naohiro.aota@xxxxxxx>
> > ---
> 
> Looks good except for - what happens when we replace or add a new zone
> device with a different queue_max_zone_append_sectors(queue) value. ?

The max zone seems to be a constraint for all devices so yeah it should
be recalculated.



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux