lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 26 Apr 2007 11:50:59 -0700 (PDT) From: David Lang <david.lang@...italinsight.com> To: Chase Venters <chase.venters@...entec.com> cc: Linus Torvalds <torvalds@...ux-foundation.org>, Nigel Cunningham <nigel@...el.suspend2.net>, Pekka Enberg <penberg@...helsinki.fi>, LKML <linux-kernel@...r.kernel.org> Subject: Re: Back to the future. On Thu, 26 Apr 2007, Chase Venters wrote: > On Thu, 26 Apr 2007, Linus Torvalds wrote: > >> >> Once you have that snapshot image in user space you can do anything you >> want. And again: you'd hav a fully working system: not any degradation >> *at*all*. If you're in X, then X will continue running etc even after the >> snapshotting, although obviously the snapshotting will have tried to page >> a lot of stuff out in order to make the snapshot smaller, so you'll likely >> be crawling. >> > > In fact... If you're just paging out to make a smaller snapshot (ie, not > to free up memory), couldn't you just swap it out (if it's not backed by a > file) then mark it as "half-released"... ie, the snapshot writing code > ignores it knowing that it will be available on disk at resume, but then > when the snapshot is complete it's still available in physical RAM, > preventing user-space from crawling due to the necessity of paging it all > back in? your swap space may end up being re-used before you restore with std David Lang - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists