mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: preempt-rt, NUMA and strange latency traces
Date: Thu, 09 Feb 2006 12:24:35 +0100	[thread overview]
Message-ID: <1139484275.5706.19.camel@frecb000686> (raw)
In-Reply-To: <1139465045.30058.31.camel@mindpipe>

On Thu, 2006-02-09 at 01:04 -0500, Lee Revell wrote:
> On Wed, 2006-02-08 at 11:45 +0100, Sébastien Dugué wrote:
> > The more I think about it, the more I tend to believe it's hardware 
> > related. It seems as if the CPU just hangs for ~27 ms before
> > resuming processing. 
> 
> That would be an exceptionally long latency - you would probably notice
> it if the mouse froze, VOIP dropped out, ping stops, etc for 30ms.
> 

  It's a test machine and I use it remotely with console redirected so
no mouse, no RT applications aside from my silly nanosleep() loop. But 
I do notice that that test sometimes takes more time (ie when I get 
those weird latencies). 


  Sébastien.


  reply	other threads:[~2006-02-09 11:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 11:28 Sébastien Dugué
2006-02-08  9:41 ` Steven Rostedt
2006-02-08 10:25   ` Ingo Molnar
2006-02-08 10:47     ` Sébastien Dugué
2006-02-08 10:45   ` Sébastien Dugué
2006-02-08 16:49     ` john stultz
2006-02-09 11:11       ` Sébastien Dugué
2006-02-09 11:26         ` Sébastien Dugué
2006-02-09 18:54         ` john stultz
2006-02-10 13:07           ` Sébastien Dugué
2006-02-10 19:07             ` Lee Revell
2006-02-09  6:04     ` Lee Revell
2006-02-09 11:24       ` Sébastien Dugué [this message]
2006-02-09 20:02         ` Lee Revell
2006-02-10 13:18           ` Sébastien Dugué

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=1139484275.5706.19.camel@frecb000686 \
    --to=sebastien.dugue@bull.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rlrevell@joe-job.com \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®