From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH -mm] Freezer: Handle uninterruptible tasks
Date: Sat, 7 Jul 2007 09:46:47 +1000 [thread overview]
Message-ID: <200707070946.50153.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <200707070056.22560.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
Hi.
On Saturday 07 July 2007 08:56:21 Rafael J. Wysocki wrote:
> On Friday, 6 July 2007 22:26, Oleg Nesterov wrote:
> > Rafael J. Wysocki wrote:
> > >
> > > This patch makes the freezer skip uninterruptible user space tasks (ie.
such
> > > that have an mm of their own) when counting the tasks to be frozen. As
a
> > > result, these tasks have the TIF_FREEZE and TIF_SIGPENDING flags set,
but the
> > > freezer doesn't wait for them to enter the refrigerator. Nevertheless,
they
> > > will enter the refrigerator as soon as they change their state.
> >
> > A small correction: they will enter the refrigerator on return to
user-space.
>
> Yes, I should have written that explicitly.
>
> > Actually, TASK_INTERRUPTIBLE doesn't mean the task actually sleeps. It
could
> > be running or preempted... I am a bit worried :)
>
> Fortunately, similar approach has been tested quite extensively by suspend2,
> IIRC. :-)
That's right. I used to signal TASK_UNINTERRUPTIBLE (I take it the
INTERRUPTIBLE above is a typo) tasks, but ignore them when deciding whether
freezing was successful.
I've since dropped those modifications, but only because I'm actively trying
to get closer to mainline.
Regards,
Nigel
--
Nigel Cunningham
Christian Reformed Church of Cobden
103 Curdie Street, Cobden 3266, Victoria, Australia
Ph. +61 3 5595 1185 / +61 417 100 574
Communal Worship: 11 am Sunday.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-06 23:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 20:26 [RFC][PATCH -mm] Freezer: Handle uninterruptible tasks Oleg Nesterov
2007-07-06 22:38 ` Oliver Neukum
2007-07-06 23:00 ` Rafael J. Wysocki
2007-07-07 23:08 ` Rafael J. Wysocki
2007-07-06 22:56 ` Rafael J. Wysocki
2007-07-06 23:46 ` Nigel Cunningham [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-06 8:12 Rafael J. Wysocki
2007-07-06 15:01 ` Alan Stern
2007-07-07 23:08 ` Rafael J. Wysocki
2007-07-08 12:09 ` Pavel Machek
2007-07-08 13:55 ` Rafael J. Wysocki
2007-07-09 4:21 ` Jeremy Maitin-Shepard
2007-07-09 14:45 ` Alan Stern
2007-07-09 15:36 ` Jeremy Maitin-Shepard
2007-07-08 18:37 ` Pavel Machek
2007-07-07 7:50 ` Pavel Machek
2007-07-07 9:13 ` Nigel Cunningham
2007-07-07 11:31 ` Pavel Machek
2007-07-07 20:44 ` Rafael J. Wysocki
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=200707070946.50153.nigel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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