From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: paolo.valente@linaro.org
Cc: linux-block@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>
Subject: Re: blk-mq 5-8 times slower for bmap-tools
Date: Fri, 17 Aug 2018 19:52:41 +0200 [thread overview]
Message-ID: <CAPybu_20-bSH5aw5L0mrmLRTD3Q02Sj0yez5LxJ1YHcDAZeoBg@mail.gmail.com> (raw)
In-Reply-To: <82A59CD0-9B59-4F5B-BE9B-BCDD3FDCA177@linaro.org>
Hi Paolo
On Fri, Aug 17, 2018 at 7:42 PM Paolo Valente <paolo.valente@linaro.org> wrote:
>
> Try bfq too, as it is probably the one containing also the most old
> way heuristics. If bfq fails too, we will at least know that the issue
> is out of the schedulers. Or in every scheduler! :)
I believe that for this specific setup: A disk reader with a cfast via
USB3, the best approach might be to have a single queue and respect
the tool sequence. But definitely the io layer is out of my expertise
;)
Monday morning will performe the tests.
Thanks again and best regards!
--
Ricardo Ribalda
next prev parent reply other threads:[~2018-08-17 20:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 17:31 blk-mq 5-8 times slower for bmap-tools Ricardo Ribalda Delgado
2018-08-17 17:35 ` Paolo Valente
2018-08-17 17:39 ` Ricardo Ribalda Delgado
2018-08-17 17:41 ` Jens Axboe
2018-08-17 17:49 ` Ricardo Ribalda Delgado
2018-08-17 21:23 ` Jens Axboe
2018-08-17 17:42 ` Paolo Valente
2018-08-17 17:52 ` Ricardo Ribalda Delgado [this message]
2018-08-17 23:43 ` Ming Lei
[not found] ` <CAPybu_2ke4usj9Qwr9iSKTymAk1510pzZnZAgLemRB+cK4Se1A@mail.gmail.com>
2018-08-20 8:30 ` Ming Lei
2018-08-20 9:04 ` Ricardo Ribalda Delgado
2018-08-20 9:55 ` Ming Lei
2018-08-20 9:56 ` Ricardo Ribalda Delgado
2018-08-20 10:15 ` Ming Lei
2018-08-20 11:42 ` Ming Lei
2018-08-20 11:45 ` Ming Lei
2018-08-22 19:22 ` Ben Hutchings
2018-08-22 22:02 ` Ming Lei
2018-08-23 0:51 ` Ben Hutchings
2018-08-23 2:17 ` Ming Lei
2018-08-23 6:29 ` Ricardo Ribalda Delgado
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPybu_20-bSH5aw5L0mrmLRTD3Q02Sj0yez5LxJ1YHcDAZeoBg@mail.gmail.com \
--to=ricardo.ribalda@gmail.com \
--cc=ben@decadent.org.uk \
--cc=linux-block@vger.kernel.org \
--cc=paolo.valente@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.