Message-ID: <3C40B6F3.1531F931@zip.com.au>
Date: Sat, 12 Jan 2002 14:21:39 -0800
From: Andrew Morton <akpm@zip.com.au>
MIME-Version: 1.0
To: Jussi Laako <jussi.laako@kolumbus.fi>
CC: linux-kernel@vger.kernel.org, linux-audio-dev@music.columbia.edu
Subject: Re: [PATCH] Additions to full lowlatency patch
In-Reply-To: <3C40AF23.18C811A8@kolumbus.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

Jussi Laako wrote:
> 
> Hi,
> 
> I've done some changes to lowlatency patched kernel. Mainly "fixes" to DRM
> drivers and few network drivers. Most probably I have done something really
> stupid, but those work here(tm). Especially the Radeon driver patch has got
> a lot of testing and seems to have huge impact to latencies in my system.
> 

Thanks, Jussi - I'll crunch on this, merge the bits I agree with :)

As Arjan points out, the eepro100 change will cause deadlocks on SMP,
and general badness on uniprocessor.  But I've done a heap of testing
on a eepro100 machine and it hasn't been a problem.  I expect that
wait_for_cmd_done() is only a problem during device startup and shutdown.
And possibly in error recovery.

I take the position that device driver startup and shutdown functions
are a complete basket case, and they are on the "don't do that" list.
Generally, this is OK.  Latency-critical applications should be
careful to ensure that all required kernel modules are loaded beforehand,
and that the cron jobs which reap idle kernel modules be disabled.
Maybe, they should also ensure that any device-special files are held
open across the life of the application.

I used to take the same position on fileystem mount and unmount,  however
things like autofs and some applciations which poll cdrom drives made this
impractical, so filesystem mounts and unmounts are on the "do do that"
list.  I hope.

-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/