linux-kernel - Re: kernel processes - are they really needed?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 1 Nov 2007 21:51:34 -0400
From:	Dmitry Torokhov <dtor@...ightbb.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Ram <vshrirama@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: kernel processes - are they really needed?

On Wednesday 31 October 2007 13:33, Andi Kleen wrote:
> "Dmitry Torokhov" <dmitry.torokhov@...il.com> writes:
> 
> > On 10/24/07, Andi Kleen <andi@...stfloor.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/