Eric,
> While some drivers set queue_limits.io_opt (e.g., md raid5), there are
> currently no SCSI/RAID controller drivers that do.
That's not true. Lots of SCSI RAID devices report a stripe width.
--
Martin K. Petersen Oracle Linux Engineering
From: Eric Wheeler
While some drivers set queue_limits.io_opt (e.g., md raid5), there are
currently no SCSI/RAID controller drivers that do. Previously stripe_size
and partial_stripes_expensive were read-only values and could not be
tuned by users (eg, for hardware RAID5/6).
This patch enables
By mistake, there is a '&' instead of a '==' in the definition of the
macro BFQQ_TOTALLY_SEEKY. This commit replaces the wrong operator with
the correct one.
Fixes: commit 7074f076ff15 ("block, bfq: do not tag totally seeky queues as
soft rt")
Signed-off-by: Paolo Valente
---
block/bfq-iosched.
Sorry, I forgot to mention the fixed commit. Making a V2 ...
> Il giorno 22 giu 2019, alle ore 21:38, Paolo Valente
> ha scritto:
>
> By mistake, there is a '&' instead of a '==' in the definition of the
> macro BFQQ_TOTALLY_SEEKY. This commit replaces the wrong operator with
> the correct one.
Hi Jens,
any chance this trivial, but rather critical fix makes it into 5.2?
Thanks,
Paolo
Paolo Valente (1):
block, bfq: fix operator in BFQQ_TOTALLY_SEEKY
block/bfq-iosched.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.20.1
By mistake, there is a '&' instead of a '==' in the definition of the
macro BFQQ_TOTALLY_SEEKY. This commit replaces the wrong operator with
the correct one.
Signed-off-by: Paolo Valente
---
block/bfq-iosched.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/bfq-iosched
On 6/21/19 6:06 AM, Stephen Bates wrote:
> Hi
>
>> I hit the following BUG when testing fio's t/io_uring test on a null
>> block device
>
> I confirmed the same BUG occurs on 5.2-rc5. I also managed to hit a
> similar bug if I use the io_uring engine in fio but only when the
> hipri engine optio
