From: Pavel Machek <pavel@suse.cz>
To: linux-hotplug@vger.kernel.org
Subject: Re: device model documentation 2/3
Date: Sun, 02 Jun 2002 04:49:08 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102338823505348@msgid-missing> (raw)
Hi!
> > > 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.
swsusp works for me (tm). SO structure should be 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)
Special casing swap is not enough -- you can well have memory full of data
for regular filesystem.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
_______________________________________________________________
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
next reply other threads:[~2002-06-02 4:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 4:49 Pavel Machek [this message]
2002-06-05 12:41 ` device model documentation 2/3 Oliver Neukum
2002-06-05 12:51 ` Oliver Neukum
2002-06-05 19:04 ` Patrick Mochel
2002-06-05 19:11 ` Patrick Mochel
2002-06-05 21:52 ` Oliver Neukum
2002-06-05 21:54 ` Oliver Neukum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-102338823505348@msgid-missing \
--to=pavel@suse.cz \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).