Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755127Ab0FSIoJ (ORCPT ); Sat, 19 Jun 2010 04:44:09 -0400 Received: from hera.kernel.org ([140.211.167.34]:46592 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751143Ab0FSIoF (ORCPT ); Sat, 19 Jun 2010 04:44:05 -0400 Message-ID: <4C1C830B.5020806@kernel.org> Date: Sat, 19 Jun 2010 10:42:51 +0200 From: Tejun Heo User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Andi Kleen CC: Arjan van de Ven , mingo@elte.hu, tglx@linutronix.de, bphilips@suse.de, yinghai@kernel.org, akpm@linux-foundation.org, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, jeff@garzik.org, linux-ide@vger.kernel.org, stern@rowland.harvard.edu, gregkh@suse.de, khali@linux-fr.org Subject: Re: [PATCH 09/12] irq: implement IRQ expecting References: <1276443098-20653-1-git-send-email-tj@kernel.org> <1276443098-20653-10-git-send-email-tj@kernel.org> <20100616204854.4b036f87@infradead.org> <87zkyro1xl.fsf@basil.nowhere.org> In-Reply-To: <87zkyro1xl.fsf@basil.nowhere.org> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (hera.kernel.org [127.0.0.1]); Sat, 19 Jun 2010 08:42:52 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 932 Lines: 27 Hello, On 06/19/2010 10:35 AM, Andi Kleen wrote: >> I would like to suggest an (optional) argument to this with a duration >> within which to expect an interrupt.... >> >> that way in the backend we can plumb this also into the idle handler >> for C state selection... > > I'm not sure it's really that useful to power optimize > the lost interrupts polling case. It's just a last resort > fallback anyways and will be always less power efficient > because there will be unnecessary polls. IIUC, it's not to help or optimize polling itself. It just gives us a way to estimate when the next interrupt would be so that power can be optimized for non polling cases. Thanks. -- tejun -- 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/