From: Jan Kara <jack@suse.cz>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Jan Kara <jack@suse.cz>, linux-block@vger.kernel.org
Subject: Re: False waker detection in BFQ
Date: Mon, 23 Aug 2021 18:06:18 +0200 [thread overview]
Message-ID: <20210823160618.GI21467@quack2.suse.cz> (raw)
In-Reply-To: <A72B321A-3952-4C00-B7DB-67954B05B99A@linaro.org>
On Mon 23-08-21 15:58:25, Paolo Valente wrote:
> > Currently I'm running wider set of benchmarks for the patches to see
> > whether I didn't regress anything else. If not, I'll post the patches to
> > the list.
>
> Any news?
It took a while for all those benchmarks to run. Overall results look sane,
I'm just verifying by hand now whether some of the localized regressions
(usually specific to a particular fs+machine config) are due to a measurement
noise or real regressions...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2021-08-23 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 16:20 False waker detection in BFQ Jan Kara
2021-05-20 15:05 ` Paolo Valente
2021-05-21 13:10 ` Jan Kara
2021-08-13 14:01 ` Jan Kara
2021-08-23 13:58 ` Paolo Valente
2021-08-23 16:06 ` Jan Kara [this message]
2021-08-25 16:43 ` Jan Kara
2021-08-26 9:45 ` Paolo Valente
2021-08-26 17:51 ` Jan Kara
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=20210823160618.GI21467@quack2.suse.cz \
--to=jack@suse.cz \
--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 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).