From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Carol Wong <carolw@netacquire.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: 4.9.33-rt23 latency under high load
Date: Mon, 21 Aug 2017 15:25:22 +0200 [thread overview]
Message-ID: <20170821132522.nbtbdaj2ls5an6zw@linutronix.de> (raw)
In-Reply-To: <79e87984082046ca9cafa8baf74ee864@S1P7MBX1A.EXCHPROD.USA.NET>
On 2017-08-11 22:15:02 [+0000], Carol Wong wrote:
> Hi Sebastian,
Hi Carol,
> I can't say that this change is responsible, but I see a dramatic difference when this patch is removed. Perhaps this is a red herring. For sure in my test case, 4.9.30-rt21 reports small latency and 4.9.33-rt23 reports large latency.
>
> > This change should be a nop if you don't change the task's CPU-mask
> > while the task is in a migrate-disable section. Do I miss something?
> > Is part of your workload changing cpu-affinity mask?
> >
>
> The test program does not alter affinity masks.
interesting. Could you add a trace-printk to check if it gets into that
inner-loop if the mask changes and it needs to do the fixup? Other than
that I don't see anything that could make any difference.
> I performed the same test with 4.11.12-rt9 and observed large latencies under heavy cpu & net load.
>
> [localhost:~]# cyclictest -S -p98 --policy=rr
> # /dev/cpu_dma_latency set to 0us
> policy: rr: loadavg: 0.65 0.61 0.56 1/204 2206
>
> T: 0 ( 2131) P:98 I:1000 C:11132138 Min: 1 Act: 1 Avg: 1 Max: 375
> T: 1 ( 2132) P:98 I:1500 C:7421425 Min: 1 Act: 1 Avg: 1 Max: 105
> T: 2 ( 2133) P:98 I:2000 C:5566069 Min: 1 Act: 1 Avg: 1 Max: 68
> T: 3 ( 2134) P:98 I:2500 C:4452855 Min: 1 Act: 2 Avg: 1 Max: 64
>
>
> Cheers,
> Carol
Sebastian
prev parent reply other threads:[~2017-08-21 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 22:45 4.9.33-rt23 latency under high load Carol Wong
2017-08-07 13:46 ` Sebastian Andrzej Siewior
2017-08-11 22:15 ` Carol Wong
2017-08-21 13:25 ` Sebastian Andrzej Siewior [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=20170821132522.nbtbdaj2ls5an6zw@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=carolw@netacquire.com \
--cc=linux-rt-users@vger.kernel.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).