| |||||||||||||
SwappingSwappingPosted Jul 23, 2011 5:55 UTC (Sat) by jeremiah (subscriber, #1221)In reply to: Swapping by mhelsley Parent article: Checkpoint/restart (mostly) in user space
I would think you could reserve an amount large enough to start a process to spool out and checkpoint the process to disk. It might not be the most efficient thing, but it might just get the job done. I obviously haven't looked at this/ heard enough to make an informed opinion, just seemed like a cool idea though. I'm curious why you need to know the amount of memory needed though?
(Log in to post comments)
Swapping Posted Jul 28, 2011 9:21 UTC (Thu) by mhelsley (subscriber, #11324) [Link]
Precisely to know how much memory to reserve as you suggested. Unless you're clever at managing it yet keeping it available during OOM that reserved memory is wasted memory. So you'd want to be careful not to waste too much.
Swapping Posted Jul 28, 2011 17:10 UTC (Thu) by jeremiah (subscriber, #1221) [Link]
Right, guess I misread something. Obviously you have to reserve enough mem for the checkpoint process, but that seems like it would be of a fixed and predictable size, probably even fairly small. I was under the impression that they were trying to figure out how big the process that was being killed was, which as long as it fits on a disk, which seems pretty likely, you don't really care. As long as there is always more free space on the drive, than there is total memory on the system, you never have a out of disk space problem.
|
|||||||||||||