public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "G . Sumner Hayes" <sumner-kernel@forceovermass.com>
To: Jussi Laako <jussi.laako@kolumbus.fi>
Cc: linux-audio-dev@music.columbia.edu, linux-kernel@vger.kernel.org
Subject: Re: 2.4.x, patches and latencies
Date: Sat, 19 Jan 2002 17:45:24 -0500	[thread overview]
Message-ID: <20020119174524.A1387@forceovermass.com> (raw)
In-Reply-To: <3C41849D.72ECBC05@kolumbus.fi> <3C41AC11.4060806@drugphish.ch> <3C41BFF1.6FF714A1@kolumbus.fi> <3C496A67.5237873F@kolumbus.fi>
In-Reply-To: <3C496A67.5237873F@kolumbus.fi>; from jussi.laako@kolumbus.fi on Sat, Jan 19, 2002 at 02:45:27PM +0200

On Sat, Jan 19, 2002 at 02:45:27PM +0200, Jussi Laako wrote:
> I made a web page for my kernel patch combinations. Aimed primarily for low
> latency use.
> 
> http://www.pp.song.fi/~visitor/linux/
> 
> Latest 2.4.17-jl11 contains:
> 
>  - Andre's ide driver update
>  - Lionel's SiS ide driver update
>  - ALi ide fix
>  - Small AGP fix
>  - Updated VIA KT133/KT266 fix
>  - Rik's rmap-11c
>  - Ingo's sched-O1-J2
[SNIP]
> -jl11-ll also contains:
> 
>  - full lowlatency patch
>  - my DRM lowlatency patch

FWIW, I just built this and did a kernel compile+updatedb+xmms
test.  Normally (Red Hat's  2.4.7), xmms skips like mad under those
circumstances, with this patch it didn't skip at all.  And system "feel"
is good.

Not scientific numbers, and maybe not all that useful given the
huge number of variables in the patch, but I figured I'd throw it
out here.

Thanks for putting this patch up, Jussi.

  Sumner

      reply	other threads:[~2002-01-19 22:46 UTC|newest]

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

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=20020119174524.A1387@forceovermass.com \
    --to=sumner-kernel@forceovermass.com \
    --cc=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