From: Andrew Morton <akpm@osdl.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, pavel@suse.cz, nigel@suspend2.net
Subject: Re: [PATCH -mm] swsusp: freeze user space processes first
Date: Sun, 5 Feb 2006 01:38:59 -0800 [thread overview]
Message-ID: <20060205013859.60a6e5ab.akpm@osdl.org> (raw)
In-Reply-To: <200602051014.43938.rjw@sisk.pl>
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> Hi,
>
> This patch allows swsusp to freeze processes successfully under heavy load
> by freezing userspace processes before kernel threads.
>
> ...
>
> /* 0 = success, else # of processes that we failed to stop */
> int freeze_processes(void)
> {
> - int todo;
> + int todo, nr_user, user_frozen;
> unsigned long start_time;
> struct task_struct *g, *p;
> unsigned long flags;
>
> printk( "Stopping tasks: " );
> start_time = jiffies;
> + user_frozen = 0;
> do {
> - todo = 0;
> + nr_user = todo = 0;
> read_lock(&tasklist_lock);
> do_each_thread(g, p) {
> if (!freezeable(p))
> continue;
> if (frozen(p))
> continue;
> -
> - freeze(p);
> - spin_lock_irqsave(&p->sighand->siglock, flags);
> - signal_wake_up(p, 0);
> - spin_unlock_irqrestore(&p->sighand->siglock, flags);
> - todo++;
> + if (p->mm && !(p->flags & PF_BORROWED_MM)) {
> + /* The task is a user-space one.
> + * Freeze it unless there's a vfork completion
> + * pending
> + */
> + if (!p->vfork_done)
> + freeze_process(p);
> + nr_user++;
> + } else {
> + /* Freeze only if the user space is frozen */
> + if (user_frozen)
> + freeze_process(p);
> + todo++;
> + }
> } while_each_thread(g, p);
> read_unlock(&tasklist_lock);
> + todo += nr_user;
> + if (!user_frozen && !nr_user) {
> + sys_sync();
> + start_time = jiffies;
> + }
> + user_frozen = !nr_user;
> yield(); /* Yield is okay here */
> - if (todo && time_after(jiffies, start_time + TIMEOUT)) {
> - printk( "\n" );
> - printk(KERN_ERR " stopping tasks timed out (%d tasks remaining)\n", todo );
> + if (todo && time_after(jiffies, start_time + TIMEOUT))
> break;
The logic in that loop makes my brain burst.
What happens if a process does vfork();sleep(100000000)?
next prev parent reply other threads:[~2006-02-05 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-05 9:14 Rafael J. Wysocki
2006-02-05 9:38 ` Andrew Morton [this message]
2006-02-05 10:34 ` Rafael J. Wysocki
2006-02-05 10:50 ` Ingo Molnar
2006-02-05 11:11 ` Rafael J. Wysocki
2006-02-05 11:18 ` Pavel Machek
2006-02-05 11:39 ` Rafael J. Wysocki
2006-02-05 13:34 ` Rafael J. Wysocki
2006-02-10 20:20 ` vfork makes processes uninterruptible [was Re: [PATCH -mm] swsusp: freeze user space processes first] Pavel Machek
2006-02-05 11:11 ` [PATCH -mm] swsusp: freeze user space processes first Pavel Machek
2006-02-05 14:22 ` Ingo Molnar
2006-02-10 20:36 ` 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=20060205013859.60a6e5ab.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@suspend2.net \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome