From: Lee Revell <rlrevell@joe-job.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>
Subject: Latency results with 2.6.10 - looks good
Date: Wed, 29 Dec 2004 14:33:40 -0500 [thread overview]
Message-ID: <1104348820.5218.42.camel@krustophenia.net> (raw)
After testing JACK with vanilla 2.6.10, it appears that the scheduling
latency of 2.6.10 is a vast improvement over previous kernel releases.
JACK seems to be usable with a period of 32 and 64 frames, I cannot
produce xruns by moving the mouse or any amount of display or disk
activity. Previous kernel releases were somewhat worse than Windows XP
in this area, 2.6.10 is definitely better, maybe as good as OSX.
So, it appears that all of the latency fixes going upstream from Ingo
and others have really made a difference. More testing is needed but it
looks like we may finally have a kernel that's usable (and in fact quite
good) out of the box for low latency audio. Good work!
Lee
next reply other threads:[~2004-12-29 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 19:33 Lee Revell [this message]
2005-01-01 3:18 ` Latency results with 2.6.10 - looks good Lee Revell
2005-01-01 9:22 ` Andrew Morton
2005-01-04 9:51 ` Ingo Molnar
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=1104348820.5218.42.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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