From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, power@bughost.org
Cc: linux-kernel@vger.kernel.org, Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: A few questions and issues with dynticks, NOHZ and powertop
Date: Sun, 4 Apr 2010 12:35:15 +0200 [thread overview]
Message-ID: <20100404103515.GA4962@comet.dominikbrodowski.net> (raw)
In-Reply-To: <20100403235326.GA23445@core.coreip.homeip.net>
Hi Dmitry,
On Sat, Apr 03, 2010 at 04:53:26PM -0700, Dmitry Torokhov wrote:
> On Sun, Apr 04, 2010 at 12:33:28AM +0200, Dominik Brodowski wrote:
> >
> > 4) SynPS/2 touchpad:
> > Why does moving the touchpad lead to sooo many IRQs? I can't look as fast
> > as the mouse pointer seems to get new data:
> > 62,5% (473,1) <interrupt> : PS/2 keyboard/mouse/touchpad
> >
>
> 80 pps @ 6 bytes/packet = 480 interrupts/sec.
>
> You can try using psmouse.rate=40 to limit it to 40 pps which should
> bring it to the rate of standard PS/2 mouse at the expense of
> sensitivity...
Excellent. Maybe this could be added to the Tips&Tricks section at the
Powertop website?
I guess obtaining all 6 bytes at once is not really possible? It
seems a new byte only appears ~1.75 ms after the last one, at least on my
notebook, so waiting for this is not an option...
Best,
Dominik
PS: Dmitry, got something small for you in return:
[PATCH] i8042: spelling fix
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
diff --git a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c
index 9302ba0..f61233e 100644
--- a/drivers/input/serio/i8042.c
+++ b/drivers/input/serio/i8042.c
@@ -38,7 +38,7 @@ MODULE_PARM_DESC(noaux, "Do not probe or use AUX (mouse) port.");
static bool i8042_nomux;
module_param_named(nomux, i8042_nomux, bool, 0);
-MODULE_PARM_DESC(nomux, "Do not check whether an active multiplexing conrtoller is present.");
+MODULE_PARM_DESC(nomux, "Do not check whether an active multiplexing controller is present.");
static bool i8042_unlock;
module_param_named(unlock, i8042_unlock, bool, 0);
next prev parent reply other threads:[~2010-04-04 10:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 22:33 Dominik Brodowski
2010-04-03 23:53 ` Dmitry Torokhov
2010-04-04 10:35 ` Dominik Brodowski [this message]
2010-04-05 20:54 ` Dmitry Torokhov
2010-04-04 10:47 ` Dominik Brodowski
2010-04-05 3:42 ` Arjan van de Ven
2010-04-05 20:41 ` Dominik Brodowski
2010-04-05 20:52 ` Dmitry Torokhov
2010-04-04 15:17 ` Alan Stern
2010-04-04 16:39 ` Dominik Brodowski
2010-04-04 20:47 ` Paul E. McKenney
2010-04-04 23:37 ` Paul E. McKenney
2010-04-05 3:44 ` Arjan van de Ven
2010-04-05 4:22 ` Paul E. McKenney
2010-04-05 14:40 ` Arjan van de Ven
2010-04-05 15:14 ` Paul E. McKenney
2010-04-05 16:07 ` Arjan van de Ven
2010-04-05 16:22 ` Paul E. McKenney
2010-04-05 16:23 ` Arjan van de Ven
2010-04-05 16:40 ` Paul E. McKenney
2010-04-05 18:44 ` david
2010-04-05 19:48 ` Arjan van de Ven
2010-04-05 20:34 ` Paul E. McKenney
2010-04-05 21:03 ` Dominik Brodowski
2010-04-05 21:38 ` Paul E. McKenney
2010-04-05 22:11 ` Dominik Brodowski
2010-04-05 22:31 ` Paul E. McKenney
2010-04-06 20:45 ` Dominik Brodowski
2010-04-06 20:59 ` Paul E. McKenney
2010-04-08 19:59 ` [RFC PATCH] nohz/sched: disable ilb on !mc_capable() Dominik Brodowski
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=20100404103515.GA4962@comet.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=arjan@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=power@bughost.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®