On Tue, 15 May 2001, Pavel Machek wrote:
>
> resume from disk is actually pretty hard to do in way it is readed linearily.
>
> While playing with swsusp patches (== suspend to disk) I found out that
> it was slow. It needs to do atomic snapshot, and only reasonable way to
> do that is free half of RAM, cli() and copy.
Note that "resume from disk" does _not_ have to necessarily resume kernel
data structures. It is enough if it just resumes the caches etc.
Don't get _too_ hung up about the power-management kind of "invisible
suspend/resume" sequence where you resume the whole kernel state.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Re: Getting FS access events H. Peter Anvin
- Re: Getting FS access events Albert D. Cahalan
- Re: Getting FS access events H. Peter Anvin
- Re: Getting FS access events Anton Altaparmakov
- Re: Getting FS access events H. Peter Anvin
- Re: Getting FS access events Anton Altaparmakov
- Re: Getting FS access events H. Peter Anvin
- Re: Getting FS access events Craig Milo Rogers
- Re: Getting FS access events Pavel Machek
- Re: Getting FS access events Pavel Machek
- Re: Getting FS access events Linus Torvalds
- Re: Getting FS access events Pavel Machek
- Re: Getting FS access events Linus Torvalds
- Re: Getting FS access events Stephen C. Tweedie
- Re: Getting FS access events Rogier Wolff
- Re: Getting FS access events Stephen C. Tweedie
- Re: Getting FS access events Richard Gooch
- Re: Fwd: Re: Getting FS access events Matthias Urlichs
- Re: Getting FS access events Linus Torvalds
- Re: Getting FS access events Alexander Viro
- Re: Getting FS access events David Woodhouse

