From: "Ahmed S. Darwish" <a.darwish@linutronix.de>
To: Jonathan Schwender <schwenderjonathan@gmail.com>
Cc: jkacur@redhat.com, williams@redhat.com, linux-rt-users@vger.kernel.org
Subject: Re: rt-tests: cyclictest: Add option to specify main pid affinity
Date: Wed, 24 Mar 2021 10:32:39 +0100 [thread overview]
Message-ID: <YFsHN/w+2mDHr1W8@lx-t490> (raw)
In-Reply-To: <dd40b81d-7099-7740-c2ad-64b49e582234@gmail.com>
Hi Jonathan,
On Mar 21, 2021, Jonathan Schwender wrote:
>
> On 2/22/21 5:20 PM, Ahmed S. Darwish wrote:
> >
> > Do you also have any numbers showing different results
> > with/without "--mainaffinity"?
>
> Sorry for the delay. I do have some numbers now, and there is a
> benefit to using this option if CPU isolation + CAT are
> used. Otherwise it's not really visible.
>
Thanks a lot for the results.
Since I'm doing some CAT-related stuff on RT tasks vs. GPU workloads,
I'm curious, how much was the benefit of CAT ON/OFF?
In your benchmarks you show that the combination of --mainaffinity, CPU
isolation, and CAT, improves worst case latency by 2 micro seconds. If
you keep everything as-is, but disable only CAT, how much change happens
in the results?
Also, how many classes of service (CLOS) your CPU has? How was the cache
bitmask divided vis-a-vis the available CLOSes? And did you assign
isolated CPUs to one CLOS, and non-isolated CPUs to a different CLOS? Or
was the division more granular?
Kind regards,
--
Ahmed S. Darwish
Linutronix GmbH
next prev parent reply other threads:[~2021-03-24 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 15:28 rt-tests: cyclictest: Add option to specify main pid affinity Jonathan Schwender
2021-02-22 15:28 ` [PATCH 0/2] " Jonathan Schwender
2021-02-22 15:28 ` [PATCH 1/2] cyclictest: Move main pid setaffinity handling into a function Jonathan Schwender
2021-02-23 5:12 ` John Kacur
2021-02-22 15:28 ` [PATCH 2/2] cyclictest: Add --mainaffinity=[CPUSET] option Jonathan Schwender
2021-02-22 16:20 ` rt-tests: cyclictest: Add option to specify main pid affinity Ahmed S. Darwish
2021-02-22 17:05 ` Jonathan Schwender
2021-03-21 17:11 ` Jonathan Schwender
2021-03-23 16:51 ` John Kacur
2021-03-24 9:32 ` Ahmed S. Darwish [this message]
2021-03-29 14:37 ` Jonathan Schwender
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=YFsHN/w+2mDHr1W8@lx-t490 \
--to=a.darwish@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=schwenderjonathan@gmail.com \
--cc=williams@redhat.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).