Date: Wed, 4 Jun 2003 00:53:02 -0700
From: Andrew Morton <akpm@digeo.com>
To: Vojtech Pavlik <vojtech@ucw.cz>
Cc: linux-yoann@ifrance.com, linux-kernel@vger.kernel.org, vojtech@suse.cz,
       acahalan@cs.uml.edu
Subject: Re: another must-fix: major PS/2 mouse problem
Message-Id: <20030604005302.41f3b0b8.akpm@digeo.com>
In-Reply-To: <20030604094737.C5345@ucw.cz>
References: <1054431962.22103.744.camel@cube>
	<3EDD87FD.6020307@ifrance.com>
	<20030603232155.1488c02f.akpm@digeo.com>
	<20030604094737.C5345@ucw.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1021
Lines: 24

Vojtech Pavlik <vojtech@ucw.cz> wrote:
>
> On Tue, Jun 03, 2003 at 11:21:55PM -0700, Andrew Morton wrote:
> 
> > We believe that it may be due to the ethernet driver holding interrupts off
> > for too long when the traffic is heavy.
> 
> Note that this doesn't necessarily mean that the ethernet driver
> disables the interrupts for a too long time, it just means that the
> computer is only servicing the network interrupts at that time, and
> since the mouse interrupt does have a lower priority, it's serviced
> not very often and with huge delays.
> 
> In such a case the network driver should either use interrupt mitigation
> if the cards supports it (reading many packets per one interrupt) or
> switch to a polled mode.

Has this problem been observed in 2.4 kernels?

-
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/