From: Bart Van Assche <bvanassche@acm.org>
To: Wang You <wangyoua@uniontech.com>
Cc: axboe@kernel.dk, fio@vger.kernel.org, hch@lst.de,
jaegeuk@kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.lei@redhat.com,
wangxiaohua@uniontech.com
Subject: Re: [PATCH v2 2/2] block/mq-deadline: Prioritize first request
Date: Sun, 24 Jul 2022 18:48:44 -0700 [thread overview]
Message-ID: <57accb2a-828d-c532-d964-130a63faebe5@acm.org> (raw)
In-Reply-To: <20220723105909.440050-1-wangyoua@uniontech.com>
On 7/23/22 03:59, Wang You wrote:
> Also, can I ask? If using fio or other tools, how should testing be done to get
> more accurate and convincing data? Such as the perfectly sequential and random I/O
> performance you mentioned above (fio's multi-threaded test does result in neither
> perfectly sequential nor perfectly random, but single thread dispatch is too slow,
> and cannot play the merge and sorting ability of elv).
I'm not sure that there is agreement about for which data patterns to
measure performance to conclude that certain code changes improve
performance of an I/O scheduler.
Thanks,
Bart.
prev parent reply other threads:[~2022-07-25 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 9:51 [PATCH v2 0/2] Improve mq-deadline performance in HDD Wang You
2022-07-22 9:51 ` [PATCH v2 1/2] block: Introduce nr_sched_batch sys interface Wang You
2022-07-22 17:35 ` Bart Van Assche
2022-07-23 10:04 ` Wang You
2022-07-22 9:51 ` [PATCH v2 2/2] block/mq-deadline: Prioritize first request Wang You
2022-07-22 17:47 ` Bart Van Assche
2022-07-23 10:59 ` Wang You
2022-07-25 1:48 ` Bart Van Assche [this message]
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=57accb2a-828d-c532-d964-130a63faebe5@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=wangxiaohua@uniontech.com \
--cc=wangyoua@uniontech.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).