Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 6 Jan 2003 07:50:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 6 Jan 2003 07:50:04 -0500 Received: from ns.indranet.co.nz ([210.54.239.210]:40654 "EHLO mail.acheron.indranet.co.nz") by vger.kernel.org with ESMTP id ; Mon, 6 Jan 2003 07:50:03 -0500 Date: Tue, 07 Jan 2003 01:58:04 +1300 From: Andrew McGregor To: Andrew Morton , "Grover, Andrew" cc: Pavel Machek , ACPI mailing list , kernel list Subject: Re: [ACPI] acpi_os_queue_for_execution() Message-ID: <20150000.1041857884@localhost.localdomain> In-Reply-To: <3E196C17.7D318CAF@digeo.com> References: <3E196C17.7D318CAF@digeo.com> X-Mailer: Mulberry/3.0.0b10 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 737 Lines: 20 --On Monday, January 06, 2003 03:44:23 -0800 Andrew Morton wrote: > acpi_thermal_run is doing many sinful things. Blocking memory > allocations as well as launching kernel threads from within a > timer handler. > > Converting it to use schedule_work() or schedule_delayed_work() > would fix that up. So *that* is why ACPI kernels are so slow on my laptop (Dell i8k), and make so much heat. I bet one of those threads ends up busy looping because of other brokenness. - 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/