From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stas Sergeev <stsp@aknet.ru>
Subject: Re: 1.1.5.1-5 regressions and other bugs
Date: Fri, 18 Jul 2003 20:25:36 +0400
Sender: linux-msdos-owner@vger.kernel.org
Message-ID: <3F181F80.6030306@aknet.ru>
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="------------060006090208090600000603"
Return-path: <linux-msdos-owner@vger.kernel.org>
List-Id: <linux-msdos.vger.kernel.org>
To: linux-msdos@vger.kernel.org

This is a multi-part message in MIME format.
--------------060006090208090600000603
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hello.

Robert Komar wrote:
> The times between the slowdowns would get longer as I
> increased the hogthreshold, but would never go away
> entirely.  Is this expected or a bug?
I guess the "bug" is too rough definition
for such a small issue.
Anyway the attached patch will probably make
it a bit better.
Does it help?

--------------060006090208090600000603
Content-Type: text/plain;
 name="m_sleep.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="m_sleep.diff"

--- src/base/async/int.c	Thu Jul 17 20:48:51 2003
+++ src/base/async/int.c	Fri Jul 18 20:17:04 2003
@@ -1790,9 +1790,10 @@
 /* Ok now we test to see if the mouse has been taking a break and we can let the 
  * system get on with some real work. :-) */
    if (trigger1 >= config.hogthreshold*200) {
-     if (config.hogthreshold && CAN_SLEEP() && ++trigger >= config.hogthreshold)  {
+     if (config.hogthreshold && CAN_SLEEP() &&
+        trigger++ > (config.hogthreshold - 1) * 20)  {
        m_printf("Ignoring the quiet mouse.\n");
-       usleep(INT2F_IDLE_USECS);
+       usleep(INT15_IDLE_USECS);
        trigger=0;
      }
      trigger1--;

--------------060006090208090600000603--