From: Oliver Nittka <oly@nittka.com>
To: RT <linux-rt-users@vger.kernel.org>
Cc: Staffan Tjernstrom <stjernstrom@eagleseven.com>,
tstone@krieglstein.org, tglx@linutronix.de
Subject: Re: Beginner's questions on userspace latency
Date: Sun, 24 Mar 2013 21:09:47 +0100 [thread overview]
Message-ID: <514F5D8B.7070706@nittka.com> (raw)
In-Reply-To: <514CB285.4050100@nittka.com>
Thank you all very much for your insights!
I was experimenting some more on the weekend, and before I could
investigate everything I learned from you, CPU isolation did the trick
for me (using cset just like shown in the wiki).
I originally thought sched_setaffinity() would suffice, but giving the
application its own CPU helped a lot. Didn't get anything over 1.735 ms
for two days now.
FYI: this is running on a Kontron pITX-SP
http://de.kontron.com/products/boards+and+mezzanines/embedded+sbc/pitx+25+sbc/pitxsp.html.
Thanks again!
-- o
prev parent reply other threads:[~2013-03-24 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 19:35 Beginner's questions on userspace latency Oliver Nittka
2013-03-22 20:06 ` Staffan Tjernstrom
2013-03-22 20:21 ` Tim Sander
2013-03-22 20:23 ` Thomas Gleixner
2013-03-24 20:09 ` Oliver Nittka [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=514F5D8B.7070706@nittka.com \
--to=oly@nittka.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=stjernstrom@eagleseven.com \
--cc=tglx@linutronix.de \
--cc=tstone@krieglstein.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox