public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Mike Galbraith <efault@gmx.de>
Cc: "Sébastien Dugué" <sebastien.dugue@bull.net>,
	"Ingo Molnar" <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, "John Stultz" <johnstul@us.ibm.com>,
	"Deepak Saxena" <dsaxena@plexity.net>
Subject: Re: 2.6.17-rc6-rt1
Date: Fri, 09 Jun 2006 16:31:36 +0200	[thread overview]
Message-ID: <1149863497.5257.148.camel@localhost.localdomain> (raw)
In-Reply-To: <1149860558.7423.9.camel@Homer.TheSimpsons.net>

On Fri, 2006-06-09 at 15:42 +0200, Mike Galbraith wrote:
> On Fri, 2006-06-09 at 15:11 +0200, Thomas Gleixner wrote:
> > On Fri, 2006-06-09 at 14:57 +0200, Sébastien Dugué wrote:
> > > All the round trips under strace are in the 2ms range.
> > > 
> > >   How on earth can it be that stracing the ping gives better
> > > performance???
> > 
> > Was busy fixing a scheduling while atomic bug. I just verified that I
> > have the same weird behaviour. I'm looking into it.
> 
> I downloaded and patched a ping.c to do a user triggered latency trace
> around recvfrom() of a ping -c 1 127.0.0.1 running SCHED_RR.  We
> schedule away at 25us, do aaaall kinds of interesting stuff, and come
> back at 42234us.  If you want the trace, holler.  It's 51k bzipped.

Yes, please send it offlist to me.

Thanks, 

	tglx



  reply	other threads:[~2006-06-09 14:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 21:14 2.6.17-rc6-rt1 Ingo Molnar
2006-06-08  2:09 ` 2.6.17-rc6-rt1 Daniel Walker
2006-06-08  3:49 ` 2.6.17-rc6-rt1 Mark Knecht
2006-06-08 20:12   ` 2.6.17-rc6-rt1 Mark Knecht
2006-06-08  6:42 ` [PATCH -rt] Trivial compiler warning fix Jan Altenberg
2006-06-08  8:51 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-08 19:52   ` 2.6.17-rc6-rt1 john stultz
2006-06-08 20:01     ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-08 10:28 ` 2.6.17-rc6-rt1 Michal Piotrowski
2006-06-08 12:23   ` 2.6.17-rc6-rt1 Michal Piotrowski
2006-06-08 11:28 ` 2.6.17-rc6-rt1 Michal Piotrowski
2006-06-08 18:27 ` 2.6.17-rc6-rt1 Kevin Hilman
2006-06-08 19:03   ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-08 23:57 ` 2.6.17-rc6-rt1 john stultz
2006-06-09  7:28   ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-09  8:42 ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 10:12   ` 2.6.17-rc6-rt1 Sébastien Dugué
2006-06-09 11:35     ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 11:44       ` 2.6.17-rc6-rt1 Sébastien Dugué
2006-06-09 12:20         ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 12:57           ` 2.6.17-rc6-rt1 Sébastien Dugué
2006-06-09 13:11             ` 2.6.17-rc6-rt1 Thomas Gleixner
2006-06-09 13:42               ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 14:31                 ` Thomas Gleixner [this message]
2006-06-09 15:55                 ` 2.6.17-rc6-rt1 Daniel Walker
2006-06-09 18:41                   ` 2.6.17-rc6-rt1 Mike Galbraith
2006-06-09 19:09                     ` 2.6.17-rc6-rt1 Thomas Gleixner

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=1149863497.5257.148.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=dsaxena@plexity.net \
    --cc=efault@gmx.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sebastien.dugue@bull.net \
    /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