mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.10-rc2-rt4
Date: Wed, 4 Nov 2020 13:47:46 +0100	[thread overview]
Message-ID: <20201104124746.74jdsig3dffomv3k@beryllium.lan> (raw)
In-Reply-To: <20201104111948.vpykh3ptmysqhmve@beryllium.lan>

On Wed, Nov 04, 2020 at 12:19:48PM +0100, Daniel Wagner wrote:
> Yes, Just fired up signaltest 5 times for arm64 and x86_64 with the
> latest release. Keep you posted.

arm64
  1184  0_signaltest         t0-max-latency      : fail     386.00
  1185  0_signaltest         t0-max-latency      : fail     417.00
  1186  0_signaltest         t0-max-latency      : fail     350.00
  1187  0_signaltest         t0-max-latency      : fail     360.00
  1188  0_signaltest         t0-max-latency      : fail     339.00

I noticed that also the last view 5.9-rt releases have higher values.
For example, version 5.9.0-rc8-rt12 has only 217us.

x86_64
  1189  0_signaltest         t0-max-latency      : fail      50.00
  1190  0_signaltest         t0-max-latency      : pass      46.00
  1191  0_signaltest         t0-max-latency      : pass      45.00
  1192  0_signaltest         t0-max-latency      : pass      47.00
  1193  0_signaltest         t0-max-latency      : fail      52.00

Same thing for version 5.9.0-rc8-rt12, the max value was 40us.

I'll work on getting these reports more useful, the performance trend
seems to be an interesting metric.

  reply	other threads:[~2020-11-04 12:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 19:57 Sebastian Andrzej Siewior
2020-11-04 10:38 ` Daniel Wagner
2020-11-04 10:46   ` Sebastian Andrzej Siewior
2020-11-04 11:19     ` Daniel Wagner
2020-11-04 12:47       ` Daniel Wagner [this message]
2020-11-04 13:09         ` Sebastian Andrzej Siewior
2020-11-04 16:06           ` Daniel Wagner
2020-11-06 10:54             ` Sebastian Andrzej Siewior
2020-11-06 16:14               ` Daniel Wagner
2020-11-09 12:47                 ` Sebastian Andrzej Siewior
2020-11-09 14:37                   ` Daniel Wagner
2020-11-09 16:31                     ` Sebastian Andrzej Siewior
2020-11-11 18:39                       ` Daniel Wagner
2020-11-10 18:05                     ` Sebastian Andrzej Siewior
2020-11-12 12:39                       ` Daniel Wagner
2020-11-12 13:54                         ` Sebastian Andrzej Siewior

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=20201104124746.74jdsig3dffomv3k@beryllium.lan \
    --to=wagi@monom.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®