All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Bryant <raybry@engr.sgi.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Kirill Korotaev <dev@sw.ru>,
	Christoph Lameter <christoph@lameter.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	torvalds@osdl.org, lhms <lhms-devel@lists.sourceforge.net>
Subject: Re: [RFC] Fix SMP brokenness for PF_FREEZE and make freezing usable for other purposes
Date: Mon, 27 Jun 2005 09:59:33 -0500	[thread overview]
Message-ID: <42C01455.7020803@engr.sgi.com> (raw)
In-Reply-To: <20050627131709.GA30467@atrey.karlin.mff.cuni.cz>

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.
-----------------------------------------------

WARNING: multiple messages have this Message-ID (diff)
From: Ray Bryant <raybry@engr.sgi.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Kirill Korotaev <dev@sw.ru>,
	Christoph Lameter <christoph@lameter.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	torvalds@osdl.org, lhms <lhms-devel@lists.sourceforge.net>
Subject: Re: [RFC] Fix SMP brokenness for PF_FREEZE and make freezing usable for other purposes
Date: Mon, 27 Jun 2005 09:59:33 -0500	[thread overview]
Message-ID: <42C01455.7020803@engr.sgi.com> (raw)
In-Reply-To: <20050627131709.GA30467@atrey.karlin.mff.cuni.cz>

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: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2005-06-27 15:23 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 20:20 [RFC] Fix SMP brokenness for PF_FREEZE and make freezing usable for other purposes Christoph Lameter
2005-06-24 20:20 ` Christoph Lameter
2005-06-24 22:25 ` Nigel Cunningham
2005-06-24 22:25   ` Nigel Cunningham
2005-06-25  2:51 ` Pavel Machek
2005-06-25  2:51   ` Pavel Machek
2005-06-25  4:31   ` Christoph Lameter
2005-06-25  4:31     ` Christoph Lameter
2005-06-25  4:46     ` Nigel Cunningham
2005-06-25  4:46       ` Nigel Cunningham
2005-06-25 22:37     ` Pavel Machek
2005-06-25 22:37       ` Pavel Machek
2005-06-25  6:13   ` Christoph Lameter
2005-06-25  6:13     ` Christoph Lameter
2005-06-26  2:30     ` Pavel Machek
2005-06-26  2:30       ` Pavel Machek
2005-06-26  2:55       ` Christoph Lameter
2005-06-26  2:55         ` Christoph Lameter
2005-06-26  3:09         ` Pavel Machek
2005-06-26  3:09           ` Pavel Machek
2005-06-27  3:51           ` Christoph Lameter
2005-06-27  3:51             ` Christoph Lameter
2005-06-27  4:21             ` Pavel Machek
2005-06-27  4:21               ` Pavel Machek
2005-06-27  4:24             ` Linus Torvalds
2005-06-27  4:24               ` Linus Torvalds
2005-06-27  5:53               ` Christoph Lameter
2005-06-27  5:53                 ` Christoph Lameter
2005-06-27 14:13                 ` Pavel Machek
2005-06-27 14:13                   ` Pavel Machek
2005-06-27 15:13                   ` Christoph Lameter
2005-06-27 15:13                     ` Christoph Lameter
2005-06-28  6:18                     ` Kirill Korotaev
2005-06-28  6:18                       ` Kirill Korotaev
2005-06-28  7:01                       ` Christoph Lameter
2005-06-28  7:01                         ` Christoph Lameter
2005-06-28  7:30                         ` Kirill Korotaev
2005-06-28  7:30                           ` Kirill Korotaev
2005-06-28  8:13                           ` Kirill Korotaev
2005-06-28  8:13                             ` Kirill Korotaev
2005-06-28 14:02                             ` Christoph Lameter
2005-06-28 14:02                               ` Christoph Lameter
2005-06-28 14:01                           ` Christoph Lameter
2005-06-28 14:01                             ` Christoph Lameter
2005-06-28 12:47                       ` Pavel Machek
2005-06-28 12:47                         ` Pavel Machek
2005-07-01 17:06                         ` [SUSPEND 1/2]Replace PF_FREEZE with TIF_FREEZE Christoph Lameter
2005-07-01 17:06                           ` Christoph Lameter
2005-07-01 17:14                           ` [SUSPEND 2/2] Replace PF_FROZEN with TASK_FROZEN Christoph Lameter
2005-07-01 17:14                             ` Christoph Lameter
2005-06-28 21:50                 ` [RFC] Fix SMP brokenness for PF_FREEZE and make freezing usable for other purposes Ray Bryant
2005-06-28 21:50                   ` Ray Bryant
2005-06-28 21:54                   ` Christoph Lameter
2005-06-28 21:54                     ` Christoph Lameter
2005-07-03 11:06                     ` Pavel Machek
2005-07-03 11:06                       ` Pavel Machek
2005-06-26 10:54       ` Nigel Cunningham
2005-06-26 10:54         ` Nigel Cunningham
2005-06-25  6:18   ` Christoph Lameter
2005-06-25  6:18     ` Christoph Lameter
2005-06-25  7:35 ` Kirill Korotaev
2005-06-25  7:35   ` Kirill Korotaev
2005-06-27  7:06   ` Ray Bryant
2005-06-27  7:06     ` Ray Bryant
2005-06-27 13:17     ` Pavel Machek
2005-06-27 13:17       ` Pavel Machek
2005-06-27 14:59       ` Ray Bryant [this message]
2005-06-27 14:59         ` Ray Bryant
2005-06-27 18:05         ` Pavel Machek
2005-06-27 18:05           ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42C01455.7020803@engr.sgi.com \
    --to=raybry@engr.sgi.com \
    --cc=christoph@lameter.com \
    --cc=dev@sw.ru \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pavel@ucw.cz \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.