From: Theodore Tso <tytso@mit.edu>
To: David Newall <davidn@davidnewall.com>
Cc: Jiri Kosina <jkosina@suse.cz>, "Fred ." <eldmannen@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Keys get stuck
Date: Wed, 12 Mar 2008 10:47:01 -0400 [thread overview]
Message-ID: <20080312144701.GZ15804@mit.edu> (raw)
In-Reply-To: <47D7B428.6010804@davidnewall.com>
On Wed, Mar 12, 2008 at 09:14:56PM +1030, David Newall wrote:
> It should be said that X implements auto-repeat out of necessity. While
> the kernel can report key down and up events, its further interpretation
> of those events is not appropriate. Many combinations of events are
> possible, such as keyboard plus mouse, and this precludes the kernel
> from providing a full interpretation. It would be wrong for it to even
> try. X is the proper place to implement auto-repeat for X.
The problem is that under heavy load the auto-repeat problem is real;
I've seen it as well, and it means that I've started to try to avoid
"make -j4" since that's a great way to trigger it.
- Ted
next prev parent reply other threads:[~2008-03-12 14:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 23:32 Keys get stuck Fred .
2008-03-12 0:04 ` Andrew Morton
2008-03-12 8:48 ` Sebastien Dugue
2008-03-12 10:32 ` Jiri Kosina
2008-03-12 10:44 ` David Newall
2008-03-12 14:47 ` Theodore Tso [this message]
2008-03-12 15:20 ` Stephen Hemminger
2008-03-12 16:47 ` David Newall
2008-03-12 16:49 ` Jiri Kosina
2008-03-12 21:22 ` Hans-Peter Jansen
2008-03-13 5:42 ` Mike Galbraith
2008-03-13 9:48 ` Jan Knutar
2008-03-13 11:28 ` Mike Galbraith
2008-03-13 11:31 ` Jiri Kosina
2008-03-13 12:02 ` Mike Galbraith
2008-03-13 12:02 ` Carlos R. Mafra
2008-03-13 12:06 ` Jiri Kosina
2008-03-13 12:19 ` Carlos R. Mafra
2008-03-13 12:21 ` Mike Galbraith
2008-03-13 14:18 ` Helge Hafting
2008-03-13 15:13 ` Swap makes X unfair (was Re: Keys get stuck) Carlos R. Mafra
2008-03-14 11:02 ` Helge Hafting
2008-03-15 22:11 ` Carlos R. Mafra
2008-03-16 15:27 ` Jan Knutar
2008-03-14 18:34 ` Keys get stuck Pavel Machek
2008-03-13 17:14 ` Pavel Machek
2008-03-13 17:56 ` Fred .
2008-03-13 18:03 ` Pavel Machek
2008-03-14 9:21 ` Jiri Kosina
2008-03-14 18:24 ` Pavel Machek
2008-03-14 21:34 ` Lennart Sorensen
2008-03-14 13:30 ` Lennart Sorensen
2008-03-14 19:35 ` Pavel Machek
2008-03-13 13:01 ` Mark Lord
[not found] <a6meN-2aj-39@gated-at.bofh.it>
[not found] ` <a6wxo-1xY-1@gated-at.bofh.it>
[not found] ` <a6wQO-1YG-1@gated-at.bofh.it>
[not found] ` <a6Zgb-5Hj-55@gated-at.bofh.it>
[not found] ` <a7iiO-2fq-39@gated-at.bofh.it>
2008-03-14 20:20 ` Bodo Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080312144701.GZ15804@mit.edu \
--to=tytso@mit.edu \
--cc=davidn@davidnewall.com \
--cc=eldmannen@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.