Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756546Ab0DEUmk (ORCPT ); Mon, 5 Apr 2010 16:42:40 -0400 Received: from isilmar.linta.de ([213.133.102.198]:38966 "EHLO linta.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756219Ab0DEUmg (ORCPT ); Mon, 5 Apr 2010 16:42:36 -0400 Date: Mon, 5 Apr 2010 22:41:43 +0200 From: Dominik Brodowski To: Arjan van de Ven , Dmitry Torokhov Cc: Adam Belay , Len Brown , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Peter Zijlstra , Alan Stern Subject: Re: A few questions and issues with dynticks, NOHZ and powertop Message-ID: <20100405204143.GB23159@comet.dominikbrodowski.net> Mail-Followup-To: Dominik Brodowski , Arjan van de Ven , Dmitry Torokhov , Adam Belay , Len Brown , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Peter Zijlstra , Alan Stern References: <20100403223328.GA4507@comet.dominikbrodowski.net> <20100403235326.GA23445@core.coreip.homeip.net> <20100404104708.GA5922@comet.dominikbrodowski.net> <4BB95C33.1050706@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BB95C33.1050706@linux.intel.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1612 Lines: 42 On Sun, Apr 04, 2010 at 08:42:43PM -0700, Arjan van de Ven wrote: > On 4/4/2010 3:47, Dominik Brodowski wrote: > >Hey, > > > >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) : 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... > > > >as a sidenote: if we know -- like here -- that the next IRQ will be issued > >soon, in approximately 1.75 ms (well, at least on my system), might it make > >sense to make tick_nohz_get_sleep_length() smarter to know about this? > > yes and no. > > if you are very sure (95%+ or so) then absolutely it needs to know about this > so that the C state selection code can make a better decision. > Right now it tries to look at history to guess this delay. > > Unfortunately we do not currently have such a concept in the code to make this > work... but it'd be really nice to have. Dmitry, are we "very sure" in this touchpad case? Best, Dominik -- 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/