Date: Wed, 4 Jun 2003 09:47:37 +0200
From: Vojtech Pavlik <vojtech@ucw.cz>
To: Andrew Morton <akpm@digeo.com>
Cc: Yoann <linux-yoann@ifrance.com>, linux-kernel@vger.kernel.org,
       Vojtech Pavlik <vojtech@suse.cz>,
       "Albert D.Cahalan" <acahalan@cs.uml.edu>
Subject: Re: another must-fix: major PS/2 mouse problem
Message-ID: <20030604094737.C5345@ucw.cz>
References: <1054431962.22103.744.camel@cube> <3EDD87FD.6020307@ifrance.com> <20030603232155.1488c02f.akpm@digeo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20030603232155.1488c02f.akpm@digeo.com>; from akpm@digeo.com on Tue, Jun 03, 2003 at 11:21:55PM -0700
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1087
Lines: 28

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.

> Does that seem to match your observations?  Does the problem happen when
> the net traffic is high?
> 
> Which ethernet driver are you using?

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR
-
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/