public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: Lee Revell <rlrevell@joe-job.com>,
	linux-kernel@vger.kernel.org, kernel@kolivas.org,
	rncbc@rncbc.org, paul@linuxaudiosystems.com
Subject: Re: Latency results with 2.6.10 - looks good
Date: Tue, 4 Jan 2005 10:51:47 +0100	[thread overview]
Message-ID: <20050104095147.GA14787@elte.hu> (raw)
In-Reply-To: <20050101012252.7b4645b7.akpm@osdl.org>


* Andrew Morton <akpm@osdl.org> wrote:

> Lee Revell <rlrevell@joe-job.com> wrote:
> >
> > Followup: other audio users have confirmed that 2.6.10 is the best
> >  release yet latency-wise.  It works most of the time at 64 frames
> >  (~1.33ms latency).
> > 
> >  Now, the bad news: there are still enough xruns to make it not quite
> >  good enough for, say, a recording studio; as we all know with realtime
> >  constraints the worst case scenario is important.
> 
> The kernel which you should be testing is most-recent -mm.  The -mm
> kernels have had a bunch of latency improvements which are queued for
> 2.6.11.  We need to know how that stuff performs - 2.6.10 is largely
> uninteresting from a development POV.

i think Lee is well aware of that - nevertheless his data point shows
that even the relatively low number of latency fixes that went into
2.6.10 (compared to what is pending in -mm and in -RT) are a step in the
right direction. I'd guess the biggest win was the ACPI related latency
fix, and maybe the softirq fixes.

	Ingo

  reply	other threads:[~2005-01-04  9:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-29 19:33 Latency results with 2.6.10 - looks good Lee Revell
2005-01-01  3:18 ` Lee Revell
2005-01-01  9:22   ` Andrew Morton
2005-01-04  9:51     ` Ingo Molnar [this message]
2005-01-04 10:05   ` Ingo Molnar

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=20050104095147.GA14787@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@linuxaudiosystems.com \
    --cc=rlrevell@joe-job.com \
    --cc=rncbc@rncbc.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