From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Fernando Lopez-Lezcano <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 22:20:45 +0100 [thread overview]
Message-ID: <1165526445.27217.59.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061207205819.GA21953@elte.hu>
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.
well C-states do cause latencies... as advertized in
the /proc/acpi/processor/CPU0/power file.
You can prevent linux from going into c-states that just take too long,
by setting the latency you can tolerate via the
set_acceptable_latency(). You can see the active maximum latency via the
same power file...
(right now audio playback is the main user of this api; of other parts
should use it too lets talk about it)
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-12-07 21:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 17:11 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
2006-12-07 21:20 ` Arjan van de Ven [this message]
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=1165526445.27217.59.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--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=nando@ccrma.Stanford.EDU \
--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
all inboxes | Powered by JetHome®