All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "Deniz Uğur" <deniz343@gmail.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [I-PIPE][ARM64] Experimenting on Jetson Xavier
Date: Mon, 22 Feb 2021 09:39:16 +0100	[thread overview]
Message-ID: <87y2fg339n.fsf@xenomai.org> (raw)
In-Reply-To: <652D6B1D-CE11-4C5B-93E5-0D02B07ABC35@gmail.com>


Deniz Uğur <deniz343@gmail.com> writes:

> Hi again,
>
> So I’ve installed the evl/v5.10 on Jetson Xavier and after setting the scaling_governor to performance I got somewhat good results.
>
> I’ve set the isolcpus=0 command line argument but latmus reports that CPU0 is not isolated. I’m not sure if that’s a bug or I’ve missed something.
>

You cannot isolate CPU0, this is a reserved one Linux-wise.

> Other than that I’m getting latencies between +-10us and worst latency
> is 73us.

You may want to run "evl check" for a quick verification of the running
kernel configuration wrt real-time. This reads /proc/config.gz on the
current system by default unless you pass it a .config file, so
CONFIG_IKCONFIG_PROC should be enabled if you want to check a running
kernel.

> Even though I’ve ran latmus -t I’m still getting negative latencies. Isn’t that supposed to fix that?
>

Yep, it should. This can happen with high performance platforms as the
tuner is fairly conservative when determining the typical jitter. What
is the smallest negative value you get?

> evl test reports OK for everything except for scheduler-quota-accuracy and sched-tp-accuracy (no kernel support)
>

You will need CONFIG_EVL_SCHED_QUOTA and CONFIG_EVL_SCHED_TP enabled in
your Kconfig to run these tests.

The exhaustive list of the core options can be found at
https://evlproject.org/core/build-steps/#core-kconfig.

> Are these latencies best I can get or are there anything else I can do to lower/stabilize the latencies?
>

Isolating the test CPU will certainly help. Next, a closer look to the
impact of CPU idling may help, such as measuring the latency with and
without idle=poll on the kernel boot line. As I hinted at earlier, evl
check would detect the kernel options which are known to increase the
latency figures. There might be more SoC-specific tweaks, I don't know
the Jetson enough to figure this out at the moment though.

-- 
Philippe.


  parent reply	other threads:[~2021-02-22  8:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 18:49 [I-PIPE][ARM64] Experimenting on Jetson Xavier Deniz Uğur
2021-02-21 16:29 ` Philippe Gerum
2021-02-21 17:35   ` Deniz Uğur
2021-02-21 18:14     ` Philippe Gerum
2021-02-21 21:44       ` Deniz Uğur
2021-02-22  7:01         ` Deniz Uğur
2021-02-22  8:39         ` Philippe Gerum [this message]
2021-02-22  9:01           ` Deniz Uğur

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=87y2fg339n.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=deniz343@gmail.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.