All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Emde <C.Emde@osadl.org>
To: "mr. sindar" <npc.sindar@gmail.com>, linux-rt-users@vger.kernel.org
Subject: Re: Variscite VAR-SOM-AM33 with patch-3.12.10-rt15
Date: Thu, 29 Oct 2015 19:45:06 +0100	[thread overview]
Message-ID: <56326932.3090206@osadl.org> (raw)
In-Reply-To: <5631DAE8.3000200@gmail.com>

Sergey,

> [..]
> But when i enable load with codesyscontrol-system(about 80% CPU load), i
> have following results:
> System without RT-patch:
> T: 0 ( 1412) P:80 I:10000 C:  10000 Min:      8 Act:   16 Avg:   13 Max:
>      572
> System with RT-patch:
> T: 0 ( 1549) P:80 I:10000 C:  10000 Min:     11 Act:   14 Avg:   17 Max:
>     2492
> Is it normal that max jitter in system with RT-patch more(almost 5x
> time) than in system without RT-patch, in this case?  [..]
Is the codesyscontrol system running at priority above 80 or below? If 
above, then at least the second result makes sense, since on a 
single-core system only the one task that runs at highest priority is 
the real-time task that enjoys the worst-case latency of the system. All 
other tasks do not. If, however, priority 80 of the cyclictest task is 
the highest priority of all tasks, then you may have detected a problem 
that needs to be fixed.

Note that cyclictest is intended as a placeholder of a real-time task 
for people who do not have their own user-space real-time project, for 
example kernel developers and board manufacturers. Once you have your 
own real-time application, you better equip it with internal real-time 
checks in a similar way as cyclictest does it, but you should not run 
cyclictest in parallel.

Thanks,
	-Carsten.

  reply	other threads:[~2015-10-29 18:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  8:38 Variscite VAR-SOM-AM33 with patch-3.12.10-rt15 mr. sindar
2015-10-29 18:45 ` Carsten Emde [this message]
2015-10-30  8:08   ` mr. sindar

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=56326932.3090206@osadl.org \
    --to=c.emde@osadl.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=npc.sindar@gmail.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 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.