From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <42C01455.7020803@engr.sgi.com> Date: Mon, 27 Jun 2005 09:59:33 -0500 From: Ray Bryant MIME-Version: 1.0 Subject: Re: [RFC] Fix SMP brokenness for PF_FREEZE and make freezing usable for other purposes References: <1104805430.20050625113534@sw.ru> <42BFA591.1070503@engr.sgi.com> <20050627131709.GA30467@atrey.karlin.mff.cuni.cz> In-Reply-To: <20050627131709.GA30467@atrey.karlin.mff.cuni.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Pavel Machek Cc: Kirill Korotaev , Christoph Lameter , linux-mm@kvack.org, linux-kernel@vger.kernel.org, torvalds@osdl.org, lhms List-ID: Hi Pavel, Pavel Machek wrote: > > Should be very easy to solve with one semaphore. Simply make swsusp > wait until all migrations are done. > This may not be needed. If I understand things correctly, the system won't suspsend until all tasks have returned from system calls and end up in the refrigerator. So if a memory migration is running when someone tries to suspend the system, the suspend won't occur until the memory migration system call returns. Is that correct? What happens if a system call calls schedule() (or otherwise gets blocked, e. g. by trying to obtain a semaphore?) -- Best Regards, Ray ----------------------------------------------- Ray Bryant 512-453-9679 (work) 512-507-7807 (cell) raybry@sgi.com raybry@austin.rr.com The box said: "Requires Windows 98 or better", so I installed Linux. ----------------------------------------------- -- 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: aart@kvack.org