public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jussi Laako <jussi.laako@kolumbus.fi>
To: linux-audio-dev@music.columbia.edu
Cc: linux-kernel@vger.kernel.org
Subject: 2.4.x, patches and latencies
Date: Sun, 13 Jan 2002 14:59:09 +0200	[thread overview]
Message-ID: <3C41849D.72ECBC05@kolumbus.fi> (raw)

Hi,

Finally I got the my system back to 2.4.12-ac3-ll level latencies and
smoothness and it's in fact performing significantly better.

See http://www.pp.song.fi/~visitor/latencytest5/3x256.html for latency
results. (Sound driver is OSS 3.9.5f)

Patches used against 2.4.17 are:

 - Andre's IDE patch
 - Rik's rmap-11b
 - Ingo's O(1)-H6
 - Andrew's full lowlatency
 - My additions to lowlatency

Now I'm quite happy with this!


	- Jussi Laako

-- 
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B  39DD A4DE 63EB C216 1E4B
Available at PGP keyservers


             reply	other threads:[~2002-01-13 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 12:59 Jussi Laako [this message]
     [not found] ` <3C41AC11.4060806@drugphish.ch>
2002-01-13 17:12   ` 2.4.x, patches and latencies Jussi Laako
2002-01-19 12:45     ` Jussi Laako
2002-01-19 22:45       ` G . Sumner Hayes

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=3C41849D.72ECBC05@kolumbus.fi \
    --to=jussi.laako@kolumbus.fi \
    --cc=linux-audio-dev@music.columbia.edu \
    --cc=linux-kernel@vger.kernel.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