Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754565Ab0ARQSA (ORCPT ); Mon, 18 Jan 2010 11:18:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754519Ab0ARQR7 (ORCPT ); Mon, 18 Jan 2010 11:17:59 -0500 Received: from netrider.rowland.org ([192.131.102.5]:51710 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754291Ab0ARQR6 (ORCPT ); Mon, 18 Jan 2010 11:17:58 -0500 Date: Mon, 18 Jan 2010 11:17:57 -0500 (EST) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: Oliver Neukum cc: "Rafael J. Wysocki" , LKML , linux-mm , , Andrew Morton Subject: Re: [linux-pm] [RFC][PATCH] PM: Force GFP_NOIO during suspend/resume (was: Re: Memory allocations in .suspend became very unreliable) In-Reply-To: <201001180853.31446.oliver@neukum.org> Message-ID: 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 Content-Length: 1083 Lines: 25 On Mon, 18 Jan 2010, Oliver Neukum wrote: > Am Montag, 18. Januar 2010 00:00:23 schrieb Rafael J. Wysocki: > > On Sunday 17 January 2010, Benjamin Herrenschmidt wrote: > > > On Sun, 2010-01-17 at 14:27 +0100, Rafael J. Wysocki wrote: > > ... > > > However, it's hard to deal with the case of allocations that have > > > already started waiting for IOs. It might be possible to have some VM > > > hook to make them wakeup, re-evaluate the situation and get out of that > > > code path but in any case it would be tricky. > > > > In the second version of the patch I used an rwsem that made us wait for these > > allocations to complete before we changed gfp_allowed_mask. > > This will be a very, very hot semaphore. What's the impact on performance? Can it be replaced with something having lower overhead, such as SRCU? Alan Stern -- 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/