* RFC: How to write a page to swap with [near] zero impact on memory?
@ 2003-02-24 0:47 Nigel Cunningham
0 siblings, 0 replies; only message in thread
From: Nigel Cunningham @ 2003-02-24 0:47 UTC (permalink / raw)
To: Linux Memory Management
Hi all.
I'm beginning to port the 2.4 beta 18 version, which allows the user to
suspend to disk what is pretty close to a complete image of RAM at the
time the suspend is initiated. Since this implies working in conditions
where there might be only a few hundred pages available, I carefully
accounted for pages in use and worked to free buffers and swapcache
pages that were added during the image-saving process. I'm wanting to
implement the same thing under 2.5, and would like advice on the best
way to do it. (Ideally, I'd like to write a page and have everything at
the end exactly as it was at the start, except that a copy of the page
is on disk as well as in memory).
I've spent some time looking at mm/*.c, but I won't pretend for a moment
to have a fraction of the knowledge that you guys have. I thus thought
I'd be wise to talk with you all before I submit any patches for
comments. What suggestions would you provide about minimising the impact
of writing a page to swap?
Thanks in advance for any help and regards,
Nigel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-02-24 0:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-02-24 0:47 RFC: How to write a page to swap with [near] zero impact on memory? Nigel Cunningham
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox