From: "M. Koehrer" <mathias_koehrer@arcor.de>
To: linux-rt-users@vger.kernel.org
Subject: Disabling lapic timer for a certain core
Date: Thu, 4 Mar 2010 13:29:53 +0100 (CET) [thread overview]
Message-ID: <14900780.1267705793289.JavaMail.ngmail@webmail16.arcor-online.net> (raw)
Hi all!
I am running the RT_PREEMPT kernel 2.6.31.2-rt13 on a Intel Quad Core CPU.
I start my kernel with isolcpus=1-7 option to force all processes to run on CPU core 0 only.
Now we have the need for a very fast loop. Within this loop some accesses from/to a PCIe I/O board
(mapped in user space) and some additional computation has to be done.
For this, I use a real time thread, run this on CPU core 3 and let it run in an endless polling loop.
So far everything works fine.
This thread is the only running user mode thread on CPU core 3.
However, we measure some run time jitters when accessing the I/O board in the range of up to
15 microseconds which are not tolerable by the application.
I see that on all cores the "Local Timer Interrupt" occurs 100 times a second (of course this is the timer frequency
select in the kernel configuration).
My question is now:
Is it possible to disable the "Local Timer Interrupt" for core 3 as it is actually not required here?
I want to use the full 100% CPU core time for this single loop.
Any help or ideas are welcome!
Thanks a lot.
Regards
Mathias
--
Mathias Koehrer
mathias_koehrer@arcor.de
Tolle Dekolletés oder scharfe Tatoos? Vote jetzt ... oder mach selbst mit und zeige Deine Schokoladenseite
bei Topp oder Hopp von Arcor: http://www.arcor.de/rd/footer.toh
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-03-04 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 12:29 M. Koehrer [this message]
2010-03-04 14:04 ` Disabling lapic timer for a certain core Luis Claudio R. Goncalves
2010-03-05 9:59 ` Mark Hounschell
2010-03-05 10:31 ` Jan Kiszka
2010-03-06 9:10 ` Thomas Gleixner
2010-03-06 13:12 ` Mark Hounschell
-- strict thread matches above, loose matches on Subject: below --
2010-03-04 21:03 M. Koehrer
2010-03-05 7:05 ` Thomas Gleixner
2011-05-23 21:40 Joe Howard
2011-05-23 23:49 ` Frank Rowand
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=14900780.1267705793289.JavaMail.ngmail@webmail16.arcor-online.net \
--to=mathias_koehrer@arcor.de \
--cc=linux-rt-users@vger.kernel.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.