linux-kernel - Re: [RFC v2][PATCH 4/9] Memory management

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48AD433E.7010905@linux.vnet.ibm.com>
Date:	Thu, 21 Aug 2008 15:58:14 +0530
From:	Balbir Singh <balbir@...ux.vnet.ibm.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Oren Laadan <orenl@...columbia.edu>,
	containers@...ts.linux-foundation.org, jeremy@...p.org,
	linux-kernel@...r.kernel.org, arnd@...db.de,
	dave@...ux.vnet.ibm.com
Subject: Re: [RFC v2][PATCH 4/9] Memory management - dump state

Ingo Molnar wrote:
> * Oren Laadan <orenl@...columbia.edu> wrote:
> 
>>  checkpoint/ckpt_x86.c   |   28 ++++
>>  checkpoint/rstr_x86.c   |    2 +
> 
> please move these into arch/x86/mm/checkpoint.c and 
> arch/x86/mm/restore.c. (also, please dont try to abbreviate too much in 
> filenames, makes it harder to follow changes later on, etc.)
> 
> Cool stuff btw! Any ETA on when more complex apps can be 
> checkpointed/restored? Also, shouldnt at least part of this effort be 
> joined with the live migration efforts of openvz? (or do you see 
> fundamental, unsolvable differences?)

My understanding is that this is a result of the joint discussion (with the
OpenVZ folks present) that happened during the containers min-summit prior to
OLS this year.

-- 
	Balbir
--
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/