All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Zheng, Qi" <qi.zheng@intel.com>,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] How to locate the max latency
Date: Thu, 5 Jul 2018 08:59:57 +0200	[thread overview]
Message-ID: <c5555274-a2a8-84dd-3841-1f94e969741f@siemens.com> (raw)
In-Reply-To: <0DD381DBF8F68D419C32ACFCEB28EB2553AEE721@SHSMSX101.ccr.corp.intel.com>

On 2018-07-05 08:55, Zheng, Qi wrote:
> 1. I run the test one hour for a round, totally tested for 12 rounds.
>      The data were consistent, on console mode, max latency were between 10us to 19us, on GUI mode, they were between 28us to 42us.
> 2. I tried the PREEMPT-RT kernel, yes, there was similar increase.
> 

Then you should probably discuss this with your colleagues from the
hardware design, if there are ways for software to avoid that increase
at all. If there are, we can look for how they can be activated on Linux
(but we likely need some hints from them).

Jan

> 
> Best Regards
> 
> SSG->OTC->One Linux Platform Engineering Team (Shanghai)
> 
> 
> -----Original Message-----
> From: Jan Kiszka [mailto:jan.kiszka@siemens.com] 
> Sent: Thursday, July 5, 2018 2:02 PM
> To: Zheng, Qi <qi.zheng@intel.com>; xenomai@xenomai.org
> Subject: Re: How to locate the max latency
> 
> On 2018-07-03 10:59, Zheng, Qi wrote:
>> I am using xenomai 3.0.5 (https://xenomai.org/downloads/xenomai/stable/xenomai-3.0.5.tar.bz2) on the Intel SKL platform.
>> On console mode or accessed by vnc viewer (no i915 graphics interrupt), the max latency values are usually below 20us no matter low or high loading (by stress-ng).
>> But the max latency can reach up to 40us on GUI (gnome)  mode (dozens of i915 interrupt counts per second).
>> I tried enabling the ipipe trace function, but couldn't find valuable information.
>> Is there any other good ways to locate the max latency?
>> Or does anybody have experience on reducing the latency caused by graphics (such as i915) ?
>> Many thanks.
>>
> First of all, how long did you run the tests? Maybe enabling graphics just increases the probability to hit the peak, and the same is conceptually possible without it.
> 
> It may also be the case that this is hardware-induced (GPU). Do you see a similar increase in the latency (even if from a different ground
> level) when using the PREEMPT-RT kernel?
> 
> Jan
> 
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
> 

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


      reply	other threads:[~2018-07-05  6:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03  8:59 [Xenomai] How to locate the max latency Zheng, Qi
2018-07-04  7:27 ` Zheng, Qi
2018-07-04 11:10   ` Greg Gallagher
2018-07-05  0:29     ` Zheng, Qi
2018-07-05  6:02 ` Jan Kiszka
2018-07-05  6:55   ` Zheng, Qi
2018-07-05  6:59     ` Jan Kiszka [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=c5555274-a2a8-84dd-3841-1f94e969741f@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=qi.zheng@intel.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.