Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030201AbWISQcY (ORCPT ); Tue, 19 Sep 2006 12:32:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932329AbWISQcY (ORCPT ); Tue, 19 Sep 2006 12:32:24 -0400 Received: from viper.oldcity.dca.net ([216.158.38.4]:15812 "HELO viper.oldcity.dca.net") by vger.kernel.org with SMTP id S932314AbWISQcX (ORCPT ); Tue, 19 Sep 2006 12:32:23 -0400 Subject: Re: [PATCH] Migration of Standard Timers From: Lee Revell To: Dimitri Sivanich Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, Thomas Gleixner , Andi Kleen , Jes Sorensen In-Reply-To: <20060919152942.GA26863@sgi.com> References: <20060919152942.GA26863@sgi.com> Content-Type: text/plain Date: Tue, 19 Sep 2006 12:33:37 -0400 Message-Id: <1158683617.11682.14.camel@mindpipe> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 821 Lines: 19 On Tue, 2006-09-19 at 10:29 -0500, Dimitri Sivanich wrote: > This patch allows the user to migrate currently queued > standard timers from one cpu to another. Migrating > timers off of select cpus allows those cpus to run > time critical threads with minimal timer induced latency > (which can reach 100's of usec for a single timer as shown > on an X86_64 test machine), thereby improving overall > determinance on those selected cpus. Which driver or subsystem is doing 100s of usecs of work in a timer? Shouldn't another mechanism like a workqueue be used instead? Lee - 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/