On Fri, 27 Apr 2007, Rafael J. Wysocki wrote:remember, this is being done inside the kernel. the kernel can do things like saving off the scheduler queue to prevent any userspace from running during the snapshot, it could then move selected pids over to a new queue to selectivly 'unfreeze' whatever you need (like the X processes for example) and then proceed normally (allowing processes to be spawned, forked, etc without activiating the rest of userspace becouse the rest just won't be available to be scheduled) and userspace can tell the kernel the list of pids to unfreeze so the kernel doesn't need to try and guess. David Lang -
| Kok, Auke | Re: -mm merge plans for 2.6.23 - ioat/dma engine |
| Jeff Garzik | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Matthew Garrett | [PATCH] Remove process freezer from suspend to RAM pathway |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
git: | |
