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 ;)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 07 2002 - 22:00:25 EST