lkml.org 
[lkml]   [2022]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH v15 00/13] support zoned block devices with non-power-of-2 zone sizes
From
On 10/1/22 04:38, Bart Van Assche wrote:
> On 9/30/22 08:13, Jens Axboe wrote:
>> On 9/29/22 12:31 AM, Pankaj Raghav wrote:
>>>> Hi Jens,
>>>> Please consider this patch series for the 6.1 release.
>>>>
>>>
>>> Hi Jens, Christoph, and Keith,
>>> All the patches have a Reviewed-by tag at this point. Can we queue this up
>>> for 6.1?
>>
>> It's getting pretty late for 6.1 and I'd really like to have both Christoph
>> and Martin sign off on these changes.
>
> Hi Jens,
>
> Agreed that it's getting late for 6.1.
>
> Since this has not been mentioned in the cover letter, I want to add
> that in the near future we will need these patches for Android devices.
> JEDEC is working on supporting zoned storage for UFS devices, the
> storage devices used in all modern Android phones. Although it would be
> possible to make the offset between zone starts a power of two by
> inserting gap zones between data zones, UFS vendors asked not to do this
> and hence need support for zone sizes that are not a power of two. An
> advantage of not having to deal with gap zones is better filesystem
> performance since filesystem extents cannot span gap zones. Having to
> split filesystem extents because of gap zones reduces filesystem
> performance.

As mentioned many times, my opinion is that a good implementation should
*not* have any extent span zone boundaries. So personally, I do not
consider such argument as a valid justification for the non-power-of-2
zone size support.

>
> Thanks,
>
> Bart.
>
>

--
Damien Le Moal
Western Digital Research

\
 
 \ /
  Last update: 2022-10-01 02:46    [W:0.311 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site