All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurijn Buys <Kurijn.Buys@open.ac.uk>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "Xenomai@xenomai.org" <Xenomai@xenomai.org>
Subject: Re: [Xenomai] latency spikes under load
Date: Thu, 5 Dec 2013 10:28:40 +0000	[thread overview]
Message-ID: <BBB3C87A-FD9C-47B4-BE9F-BFE18DD0D6F3@open.ac.uk> (raw)
In-Reply-To: <CE87D5F4-FE47-4310-A74F-7F8E4CCEC92B@open.ac.uk>


Op 5-dec.-2013, om 00:44 heeft Kurijn Buys het volgende geschreven:

>
> Op 4-dec.-2013, om 17:43 heeft Philippe Gerum het volgende geschreven:
>
>> On 12/04/2013 05:03 PM, Gilles Chanteperdrix wrote:
>>> On 12/04/2013 02:19 PM, Philippe Gerum wrote:
>>>> On 12/04/2013 01:00 PM, Gilles Chanteperdrix wrote:
>>>>> Ok, could you push the branch somewhere so that I can try it?
>>>>>
>>>>
>>>> testing/ipipe-3.8-i915-fix
>>>
>>> I could test it, I no longer get high latencies while moving a large
>>> opengl window. So, it looks good.
>
> I've it running as well (with the priority coupling option disabled this time). The latency test results in a worst value of 52us (no idea if this is normal, the lat max globally stays between 10 and 30us), but I have no higher pikes under load in each case...
> The other test I mentioned before still has a few measurements that occur at 10us in stead of 1000us... maybe it's an issue with this test...
>
> I have the same oddity as the other time I installed a 3.8 kernel on Ubuntu 10.04:
> -the /proc/ipipe files don't look how they should I guess. The Linux file is full of lines with "__ipipe_do_IRQ" and near the end a line with "__ipipe_do_critical_sync"...
> -the version file only states "1"
> -the xenomai file mainly has lines with "..." and also this critical sync line near the end.
>
> Also, I tried to enable the ipipe tracer but without the "tracing on boot" option, but I can't get it to work now. When I do "echo < 1 /proc/ipipe/trace/enable" (as root), the flag stays on 0. and the frozen file remains empty.

For some unknown reason, now the tracer works (I didn't even do a reboot en the mean time), and now I have difficulties setting trace/enable to 0.

Another latency test had a pike of 62us (but pikes are very rare now, and not dependent on load anymore), which seems related to the ipipe frozen line:
-56!    44.220  __ipipe_spin_lock_irqsave+0x5 (mask_and_ack_8259A+0x22)

>
>>>
>>>
>>
>> Same here.
>>
>> --
>> Philippe.
>

-- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302).


  reply	other threads:[~2013-12-05 10:28 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 11:38 [Xenomai] latency spikes under load Kurijn Buys
2013-12-03 11:54 ` Gilles Chanteperdrix
2013-12-03 12:31 ` Gilles Chanteperdrix
2013-12-03 13:07   ` Kurijn Buys
2013-12-03 13:23     ` Gilles Chanteperdrix
2013-12-03 15:31       ` Kurijn Buys
2013-12-03 15:54         ` Gilles Chanteperdrix
2013-12-03 16:49           ` Kurijn Buys
2013-12-03 18:50             ` Gilles Chanteperdrix
2013-12-04  8:44               ` Philippe Gerum
2013-12-04  8:51                 ` Gilles Chanteperdrix
2013-12-04  9:27                   ` Philippe Gerum
2013-12-04  9:31                     ` Gilles Chanteperdrix
2013-12-04  9:40                       ` Philippe Gerum
2013-12-04  9:51                         ` Gilles Chanteperdrix
2013-12-04 10:29                           ` Philippe Gerum
2013-12-04 10:33                             ` Philippe Gerum
2013-12-04 11:04                               ` Philippe Gerum
2013-12-04 11:10                                 ` Gilles Chanteperdrix
2013-12-04 11:36                                   ` Philippe Gerum
2013-12-04 11:59                                     ` Philippe Gerum
2013-12-04 12:00                                       ` Gilles Chanteperdrix
2013-12-04 13:19                                         ` Philippe Gerum
2013-12-04 16:03                                           ` Gilles Chanteperdrix
2013-12-04 17:43                                             ` Philippe Gerum
2013-12-05  0:44                                               ` Kurijn Buys
2013-12-05 10:28                                                 ` Kurijn Buys [this message]
2013-12-05 11:05                                                   ` Philippe Gerum
2013-12-05 11:09                                                 ` Gilles Chanteperdrix
2013-12-09 15:19                                                   ` Kurijn Buys
2013-12-09 15:27                                                     ` Gilles Chanteperdrix
2013-12-11 14:23                                                       ` Kurijn Buys
2013-12-11 14:51                                                         ` Lennart Sorensen
2013-12-11 16:04                                                           ` Tobias Luksch
2013-12-11 17:21                                                             ` Gilles Chanteperdrix
2013-12-11 16:44                                                       ` [Xenomai] Analogy NI 6052E Kurijn Buys
2014-03-21 14:33                                                         ` Erhart Robert (CC-DA/ESR3)
2014-03-22 16:58                                                           ` Gilles Chanteperdrix

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=BBB3C87A-FD9C-47B4-BE9F-BFE18DD0D6F3@open.ac.uk \
    --to=kurijn.buys@open.ac.uk \
    --cc=Xenomai@xenomai.org \
    --cc=rpm@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.