From: Dmitry Torokhov <dtor@insightbb.com>
To: Andi Kleen <andi@firstfloor.org>
Subject: Re: kernel processes - are they really needed?
Date: Thu, 1 Nov 2007 21:51:34 -0400
User-Agent: KMail/1.9.3
Cc: Ram <vshrirama@gmail.com>, linux-kernel@vger.kernel.org
References: <8bf247760710240637w686f1a2fxdf63a649787eca25@mail.gmail.com> <d120d5000710310935i13629beahdc01e775e3cf6aa@mail.gmail.com> <p73k5p32nqk.fsf@bingen.suse.de>
In-Reply-To: <p73k5p32nqk.fsf@bingen.suse.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200711012151.35573.dtor@insightbb.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1164
Lines: 37

On Wednesday 31 October 2007 13:33, Andi Kleen wrote:
> "Dmitry Torokhov" <dmitry.torokhov@gmail.com> writes:
> 
> > On 10/24/07, Andi Kleen <andi@firstfloor.org> wrote:
> >>
> >> My favourite for a ridiculous thread was and is "kpsmoused"
> >>
> >
> > Mouse querying can take significant amount of time. Do you really want
> > all your other events to be delayed just because kernel tries to get
> > mouse back in order?
> 
> How long?

If a mouse is stubborn and does not want to get enabled it may sleep
up to 1 sec.

> 
> 
> >
> > Although I probably want to kill it if mouse resync is disabled...
> 
> How often does that happen? Can't you just start a thread for this
> as needed? Or if it's a simple algorithm you can just use a state machine
> using timers?
>

The IRQ handler is already too complex, I'd rather not mess with a state
machine. I will see how to kill the thread if resync is disabled.

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