From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-pm@lists.osdl.org, ncunningham@cyclades.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Corrected Workqueue freezer support.
Date: Thu, 21 Jul 2005 00:56:09 -0500 [thread overview]
Message-ID: <200507210056.09515.dtor_core@ameritech.net> (raw)
In-Reply-To: <1121923979.2939.237.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
On Thursday 21 July 2005 00:32, Nigel Cunningham wrote:
> (Fixed to remove the latent mention of syncthreads).
>
> This patch implements freezer support for workqueues. The current
> refrigerator implementation makes all workqueues NOFREEZE, regardless of
> whether they need to be or not.
>
I think kseriod and kgameportd threads can be left freezable.
--
Dmitry
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2005-07-21 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 5:32 [PATCH] Corrected Workqueue freezer support Nigel Cunningham
2005-07-21 5:56 ` Dmitry Torokhov [this message]
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=200507210056.09515.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=ncunningham@cyclades.com \
/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