From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755360AbZD1VM3 (ORCPT ); Tue, 28 Apr 2009 17:12:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752254AbZD1VMU (ORCPT ); Tue, 28 Apr 2009 17:12:20 -0400 Received: from smtp.ultrahosting.com ([74.213.174.254]:52225 "EHLO smtp.ultrahosting.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751816AbZD1VMT (ORCPT ); Tue, 28 Apr 2009 17:12:19 -0400 Date: Tue, 28 Apr 2009 17:02:16 -0400 (EDT) From: Christoph Lameter X-X-Sender: cl@qirst.com To: Pavel Machek cc: Peter Zijlstra , Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: Scheduler regression: Too frequent timer interrupts(?) In-Reply-To: <20090423044228.GA2428@ucw.cz> Message-ID: References: <1239951613.23397.4107.camel@laptop> <1239977776.23397.4590.camel@laptop> <1239979901.23397.4638.camel@laptop> <1239982137.23397.4684.camel@laptop> <20090423044228.GA2428@ucw.cz> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 23 Apr 2009, Pavel Machek wrote: > I'd say that taking interrupt and returning in below 1000nsec is > impossible, even on very fast hw. Hmmm.... Could it be that CONFIG_NO_HZ caused the timer interrupt to be avoided in earlier releases? NO_HZ theory at least is to only schedule interrupts when necessary. So an interrupt is needed at the end of the scheduling intervals and not at HZ frequency.