From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Mochel Date: Wed, 05 Jun 2002 19:11:56 +0000 Subject: Re: device model documentation 2/3 Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, 5 Jun 2002, Oliver Neukum wrote: > > > 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. Why would you allocate memory on a resume transition? As for suspending, this is something that has been discussed a few times before. No definitive decision has come out of it because it hasn't been implemented yet. It hasn't been implemented yet because the infrastructure isn't complete. It's real close, but still not quite there. Nonetheless, you have to do one of a couple things: use GFP_NOIO or special case the swap device(s) so they don't stop I/O when everything else does. (Of course, you have to eventually stop it) Check the archives; there are lots of ideas there wrt this topic. But, there are bigger fish to fry in the meantime ;) -pat _______________________________________________________________ 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