From mboxrd@z Thu Jan  1 00:00:00 1970
From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
Date: Wed, 05 Jun 2002 12:51:08 +0000
Subject: Re: device model documentation 2/3
Message-Id: <marc-linux-hotplug-102328207905587@msgid-missing>
List-Id: <linux-hotplug.vger.kernel.org>
References: <marc-linux-hotplug-102338823505348@msgid-missing>
In-Reply-To: <marc-linux-hotplug-102338823505348@msgid-missing>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org


> SUSPEND_DISABLE tells the device to stop I/O transactions. When it
> stops transactions, or what it should do with unfinished transactions
> is a policy of the driver. After this call, the driver should not
> accept any other I/O requests.

Does this mean that memory allocations in the suspend/resume
implementations must be made with GFP_NOIO respectively
GFP_ATOMIC ?
It would seem so.

	Regards
		Oliver

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel