From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alex Dubov <oakad@yahoo.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Pierre Ossman <drzeus@drzeus.cx>, Pavel Machek <pavel@ucw.cz>,
Gautham R Shenoy <ego@in.ibm.com>
Subject: Re: Freezeable workqueues [Was: 2.6.22-rc1: Broken suspend on SMP with tifm]
Date: Tue, 15 May 2007 22:54:27 +0200 [thread overview]
Message-ID: <200705152254.28911.rjw@sisk.pl> (raw)
In-Reply-To: <390169.9239.qm@web36708.mail.mud.yahoo.com>
On Tuesday, 15 May 2007 02:56, Alex Dubov wrote:
> >
> > > > - Do we need freezeable workqueues ?
> > >
> > > Well, we have at least one case in which they appear to be useful.
> >
>
> I need freezeable wq exactly for the fact that they are synchronized with suspend/resume. My
> workitem may do device_register/unregister and it can (and will be) scheduled from irq handler
> during resume. As far as I understand, before freezeable wqs, kthreads were the only way to
> achieve this behavior,
That's correct.
> which is less convenient.
Thanks for the explanation.
Greetings,
Rafael
next prev parent reply other threads:[~2007-05-15 20:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 19:32 2.6.22-rc1: Broken suspend on SMP with tifm Rafael J. Wysocki
2007-05-13 20:08 ` Oleg Nesterov
2007-05-13 20:30 ` Oleg Nesterov
2007-05-13 20:50 ` Rafael J. Wysocki
2007-05-13 20:50 ` Oleg Nesterov
2007-05-13 21:22 ` Rafael J. Wysocki
2007-05-13 21:34 ` Oleg Nesterov
2007-05-13 21:50 ` Rafael J. Wysocki
2007-05-13 21:54 ` Oleg Nesterov
2007-05-13 22:21 ` Rafael J. Wysocki
2007-05-13 22:32 ` Oleg Nesterov
2007-05-14 3:24 ` Alex Dubov
2007-05-14 5:57 ` Rafael J. Wysocki
2007-05-14 16:55 ` Freezeable workqueues [Was: 2.6.22-rc1: Broken suspend on SMP with tifm] Oleg Nesterov
2007-05-14 21:27 ` Rafael J. Wysocki
2007-05-14 21:48 ` Oleg Nesterov
2007-05-15 0:56 ` Alex Dubov
2007-05-15 20:54 ` Rafael J. Wysocki [this message]
2007-05-15 20:54 ` Rafael J. Wysocki
2007-05-20 19:54 ` Oleg Nesterov
2007-05-20 20:48 ` Rafael J. Wysocki
2007-05-20 21:06 ` Oleg Nesterov
2007-05-20 21:49 ` Rafael J. Wysocki
2007-05-13 20:33 ` 2.6.22-rc1: Broken suspend on SMP with tifm Rafael J. Wysocki
2007-05-13 21:52 ` [PATCH] for 2.6.22, make freezeable workqueues singlethread Oleg Nesterov
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=200705152254.28911.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=drzeus@drzeus.cx \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=oakad@yahoo.com \
--cc=oleg@tv-sign.ru \
--cc=pavel@ucw.cz \
/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