From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933254AbZHVVoa (ORCPT ); Sat, 22 Aug 2009 17:44:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932761AbZHVVo3 (ORCPT ); Sat, 22 Aug 2009 17:44:29 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:46243 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932376AbZHVVo3 (ORCPT ); Sat, 22 Aug 2009 17:44:29 -0400 From: "Rafael J. Wysocki" To: Pavel Machek Subject: Re: [RFC][PATCH 1/3] PM: Asynchronous resume of devices Date: Sat, 22 Aug 2009 23:45:24 +0200 User-Agent: KMail/1.12.0 (Linux/2.6.31-rc6-rjw; KDE/4.3.0; x86_64; ; ) Cc: "linux-pm" , "linux-acpi" , Linux Kernel Mailing List , Zhang Rui , Len Brown , Alan Stern , Arjan van de Ven References: <200908122218.13975.rjw@sisk.pl> <200908152259.18417.rjw@sisk.pl> <20090822092429.GC11448@elf.ucw.cz> In-Reply-To: <20090822092429.GC11448@elf.ucw.cz> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200908222345.24834.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Saturday 22 August 2009, Pavel Machek wrote: > Hi! > > > > Do we really need async for noirq handlers? > > > > Yes, we do. Specifically, for PCI. > > Do noirq parts of PCI handling really so long that we need to make > them async? I think so. It may get 10 ms to handle a PCI device at this stage usually and this is all waiting. If you multiply that by the number of PCI devices ... > Async in normal paths looks pretty much okay to me, but in noirq > parts, locking is tricky, etc... The locking is actually simpler in that case. Thanks, Rafael