Messages in this thread |  | | | Date | Thu, 16 Sep 2004 14:13:00 +0200 | | From | Pavel Machek <> | | Subject | Re: [PATCH] Suspend2 Merge: Driver model patches 0/2 |
Hi!
> > > do it later: > > > > > > Suspend all other drivers. > > > Write pageset 2 (page cache). > > > Suspend used drivers. > > > Make atomic copy. > > > Resume used drivers. > > > Write pageset 1 (atomic copy) > > > Suspend used drivers. > > > Power down all. > > > > What is problem with: > > > > Write pageset 2 > > Suspend all drivers (avoiding slow operations) > > Make atomic copy > > Resume all drivers (avoiding slow operations) > > Write pageset 1 > > Suspend all drivers > > Power down all. > > It's always interesting trying to remember your logic for doing > something after the fact :>. If I recall correctly, it goes like this: > > Writing two pagesets forces me to account for memory usage much more > carefully. I need to ensure before I start to write the image that I > know exactly what the size is and have allocated enough memory to do the > write. If I get some driver coming along and grabbing memory for who > knows what (hotplug, anyone? :>), I may get stuck halfway through > writing the image with no memory to use. I also have to be paranoid > about how much memory is available because I save that too (some of it > may have become slab by the time I do the atomic copy).
What prevents video driver or disk driver to grab some memory? Tree containing disk device can be pretty big [pci-usb-usb_hub-disk] and contain some hot-pluggable components.
Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - 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/
|  |