All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frank.rowand@am.sony.com>
To: Joe Howard <howardj@esi.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: Disabling lapic timer for a certain core
Date: Mon, 23 May 2011 16:49:29 -0700	[thread overview]
Message-ID: <4DDAF289.8090002@am.sony.com> (raw)
In-Reply-To: <5A76E600A0235B469F3CC8AD2A6AC17340CCEDDC76@pdxex02.esi.com>

On 05/23/11 14:40, Joe Howard wrote:
> Apologies if this is improper etiquette top-posting and bumping a
> thread that is over 1 year old, but I am curious if any progress has
> been made toward the desire to shield one or more cores from other
> interrupts and processes?  Particularly the lapic timer interrupt.
> 
> It seems the combination of cpusets and irq smp_affinity get 95% of
> the way there, but the "Local timer interrupts" cannot be disabled
> for a given core.  My application runs a polling loop that consumes
> 100% cpu time on a "shielded" core.  The code in the loop takes about
> 500ns to execute and runs once every 5000ns (using "rdtsc"
> instruction to throttle).  I'm seeing an increase of 3000ns duration
> in one cycle out of every 200 (corresponding to the default
> HZ=1000).
> 
> Thanks, -Joe H


At ELC 2011, Thomas Gleixner gave a presentation titled "Status of
Preempt-RT and why there is no roadmap".  The slides are at:

   http://elinux.org/images/c/ca/Elc2011_gleixner.pdf

On slide 12, one of the "Future features" listed is "Full CPU isolation".
So the good news is that the feature is on the radar screen.  The bad
news is that the future is not here yet.

-Frank





  reply	other threads:[~2011-05-23 23:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 21:40 Disabling lapic timer for a certain core Joe Howard
2011-05-23 23:49 ` Frank Rowand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-04 21:03 M. Koehrer
2010-03-05  7:05 ` Thomas Gleixner
2010-03-04 12:29 M. Koehrer
2010-03-04 14:04 ` 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

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=4DDAF289.8090002@am.sony.com \
    --to=frank.rowand@am.sony.com \
    --cc=howardj@esi.com \
    --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.