All of lore.kernel.org
 help / color / mirror / Atom feed
From: 박재호 <jaeho@seoultech.ac.kr>
To: xenomai@xenomai.org
Subject: [Xenomai] kernelshark to check the CPU usage of the xenomai task.
Date: Wed, 19 Sep 2018 17:02:20 +0900 (KST)	[thread overview]
Message-ID: <653076205.1537344140916.JavaMail.root@webmail> (raw)

Hi, all



I'm using kernelshark to check the CPU usage of the xenomai task.



To check the cpu share of the xenomai task according to the cpu load given by Linux.

Using the stress-ng tool on Linux .

"# stress-ng -c0 -l100" 

gives 100% load to cpu, and xenomai has a run time of 750us for 1ms cycle.



Checking /proc/xenomai/stat we were able to verify the use of 75% CPU. 

However, I checked the cpu quota of xenomai and linux(stress-ng) using tracd-cmd and kernelshark 

I expected xenomai to use more cpu because its priority was higher than normal Linux, but the result was not so. 

The task that is "ecat-embedded" in the picture is the xenomai task. Why are these results coming out?



thank you for your advice.


             reply	other threads:[~2018-09-19  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  8:02 박재호 [this message]
2018-09-24 13:16 ` [Xenomai] kernelshark to check the CPU usage of the xenomai task Jan Kiszka

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=653076205.1537344140916.JavaMail.root@webmail \
    --to=jaeho@seoultech.ac.kr \
    --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.