From: Jan Kiszka <jan.kiszka@domain.hid>
To: Peter Pastor <peter.pastor@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] latency spike when starting opengl windows
Date: Sat, 09 Oct 2010 10:26:28 +0200 [thread overview]
Message-ID: <4CB02734.3060900@domain.hid> (raw)
In-Reply-To: <AANLkTi=6tAnApCNw9hzQUEYR7BcsgDSU3YA5N+xn-uN2@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
Am 08.10.2010 03:44, Peter Pastor wrote:
> Hey there,
>
> I noticed a spike in the latency over around 600-800microseconds when
> starting an opengl window.
>
> I have the SMI workaround enabled and also included my device id in the
>
> /usr/src/xenomai/ksrc/arch/x86/smi.c
>
> file
>
> lspci -vvv -nn shows a
>
> Intel Corporation 82801JIR (ICH10R) LPC Interface Controller [8086:3a16]
>
> so I added
>
> {PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH10_1)},
>
> After recompiling the kernel I finally saw
>
> [ 2.443949] Xenomai: SMI-enabled chipset found
>
> ( I did not see that line before )
> but unfortunately I also saw
>
> [ 2.443957] Xenomai: SMI workaround failed!
>
> Well, the latency test still showed spikes of about 600-800microsends when
> for example starting or closing glxgears. I am using a nvidia FxQuadro FX
> 4800 and I am using the latest nvidia driver which I downloaded from the
> nvidia homepage (256.53).
The nice nvdidia driver is known to cause latency peaks during DMA
memory allocation/mapping (wbinvd...). You will have to leave it in a
stable state (no X restarts, no 3D or CUDA setup/tear-down, not sure
about mode switches ATM) as long as the RT load is running.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
prev parent reply other threads:[~2010-10-09 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 1:44 [Xenomai-help] latency spike when starting opengl windows Peter Pastor
2010-10-08 22:20 ` Gilles Chanteperdrix
2010-10-09 8:26 ` 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=4CB02734.3060900@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=peter.pastor@domain.hid \
--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.