On Fri, May 22, 2020 at 09:36:18AM -0400, Martin K. Petersen wrote:
>
> >>> + if (t->io_opt & (t->physical_block_size - 1))
> >>> + t->io_opt = lcm(t->io_opt, t->physical_block_size);
> >
> >> Any comment on this patch ? Note: the patch the patch "nvme: Fix
> >> io_opt limit setting" is
>>> + if (t->io_opt & (t->physical_block_size - 1))
>>> + t->io_opt = lcm(t->io_opt, t->physical_block_size);
>
>> Any comment on this patch ? Note: the patch the patch "nvme: Fix
>> io_opt limit setting" is already queued for 5.8.
>
> Setting io_opt to the physical block size is
Damien,
>> +if (t->io_opt & (t->physical_block_size - 1))
>> +t->io_opt = lcm(t->io_opt, t->physical_block_size);
> Any comment on this patch ? Note: the patch the patch "nvme: Fix
> io_opt limit setting" is already queued for 5.8.
Setting io_opt to the physical block size is
On 2020/05/14 15:58, Damien Le Moal wrote:
> When devices with different physical sector sizes are stacked, the
> largest value is used as the stacked device physical sector size. For
> the optimal IO size, the lowest common multiple (lcm) of the underlying
> devices is used for the stacked
When devices with different physical sector sizes are stacked, the
largest value is used as the stacked device physical sector size. For
the optimal IO size, the lowest common multiple (lcm) of the underlying
devices is used for the stacked device. In this scenario, if only one of
the underlying
