LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Ingo Molnar <mingo@elte.hu>
Cc: nando@ccrma.Stanford.EDU, linux-kernel@vger.kernel.org,
	linux-rt-users@vger.kernel.org, Mike Galbraith <efault@gmx.de>,
	Clark Williams <williams@redhat.com>,
	Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Giandomenico De Tullio <ghisha@email.it>
Subject: Re: v2.6.19-rt6, yum/rpm
Date: Thu, 07 Dec 2006 13:42:03 -0800	[thread overview]
Message-ID: <1165527723.9244.45.camel@cmn3.stanford.edu> (raw)
In-Reply-To: <1165525665.9244.39.camel@cmn3.stanford.edu>

On Thu, 2006-12-07 at 13:07 -0800, Fernando Lopez-Lezcano wrote:
> On Thu, 2006-12-07 at 21:58 +0100, Ingo Molnar wrote:
> > * Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:
> > 
> > > Much better performance in terms of xruns with Jackd. Hardly any at 
> > > all as it should be. I'm starting to test -rt8 right now.
> > > 
> > > Now, I still don't have an smp machine to test so the improvement 
> > > could be because I'm just running 64 bit up instead of smp. Or it 
> > > could have been the hardware on that other machine that had some 
> > > problem (either because it was starting to fail or because the kernel 
> > > drivers for that hardware were somehow triggering the xruns).
> > 
> > i think it's the UP vs. SMP difference. We are chasing some SMP 
> > latencies right now that trigger on boxes that have deeper C sleep 
> > states. idle=poll seems to work around those problems.
> 
> Oh well, it looked too good, anyway, it is winter here so the extra
> heating should be fine :-)

Hmmm, when I was testing on smp I was running with the speed set to the
top speed of the processors (through the small gnome cpuspeed applet). I
imagine that the C states would not have been the problem...

-- Fernando



  reply	other threads:[~2006-12-07 21:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 17:11 v2.6.19-rt6, yum/rpm Ingo Molnar
2006-12-07 11:33 ` K.R. Foley
2006-12-07 12:13   ` Ingo Molnar
2006-12-07 15:54     ` K.R. Foley
2006-12-07 16:57       ` Ingo Molnar
2006-12-07 19:40         ` K.R. Foley
2006-12-07 20:04           ` Ingo Molnar
2006-12-07 20:45 ` Fernando Lopez-Lezcano
2006-12-07 20:58   ` Ingo Molnar
2006-12-07 21:07     ` Fernando Lopez-Lezcano
2006-12-07 21:42       ` Fernando Lopez-Lezcano [this message]
2006-12-07 21:20     ` Arjan van de Ven
2006-12-07 21:44       ` Ingo Molnar
2006-12-15 16:18 ` Sergei Shtylyov
2006-12-15 16:19   ` Ingo Molnar
2007-02-01 15:52     ` Sergei Shtylyov
2007-02-01 17:38       ` Ingo Molnar
2007-02-01 17:49         ` Ingo Molnar
2007-02-01 18:01           ` Sergei Shtylyov
2007-03-07 14:55             ` Sergei Shtylyov

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=1165527723.9244.45.camel@cmn3.stanford.edu \
    --to=nando@ccrma.stanford.edu \
    --cc=efault@gmx.de \
    --cc=ghisha@email.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sshtylyov@ru.mvista.com \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).