public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [PATCH] Workqueue freezer support.
Date: Thu, 21 Jul 2005 17:38:24 +0200	[thread overview]
Message-ID: <20050721153824.GB1896@elf.ucw.cz> (raw)
In-Reply-To: <1121923059.2936.224.camel@localhost>

Hi!

> This patch implements freezer support for workqueues. The current
> refrigerator implementation makes all workqueues NOFREEZE, regardless of
> whether they need to be or not.
> 
> While this doesn't appear to have caused any problems with swsusp (ie
> Pavel's version) to date, this is no guarantee for the future.
> Furthermore, it seems better to me to treat kernel and userspace threads
> consistently, and it also enables us to err on the side of caution by
> default with new workqueues.
> 
> Queues can be made unfreezable via the new kthread_nonfreeze_run,
> create_nofreeze_workqueue and create_nofreeze_singlethread_workqueue
> calls, which take the same parameters as kthread_run, create_workqueue
> and create_singlethread_workqueue respectively. Existing call syntax is
> unchanged and the vast majority of current workqueue calls are therefore
> unaffected.
> 
> As far as Suspend2 goes, I don't rate this as critical. May save your
> hard disk partition one day, but that depends upon what workqueues get
> implemented in the future, what out of tree ones do and whether I've
> missed good rationale for having nofreeze on existing in tree instances.
> If you must flame me, call me overly careful :>.

> @@ -151,6 +158,20 @@ struct task_struct *kthread_create(int (
>  
>  	return create.result;
>  }
> +
> +struct task_struct *kthread_create(int (*threadfn)(void *data),
> +				   void *data,
> +				   const char namefmt[], ...)
> +{
> +	char result[TASK_COMM_LEN];
> +
> +	va_list args;
> +	va_start(args, namefmt);
> +	vsnprintf(result, TASK_COMM_LEN, namefmt, args);
> +	va_end(args);
> +	return _kthread_create(threadfn, data, 0, result);
> +}
> +

This is slightly ugly and uses lot of stack. Otherwise patch looks
okay. If you want me to apply it, be sure to put me into To: or at
least Cc:. Or perhaps you want to just mail it to akpm, noting that I
acked it (if you do something with the char result[] :-).

								Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.

  reply	other threads:[~2005-07-21 15:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21  5:17 [PATCH] Workqueue freezer support Nigel Cunningham
2005-07-21 15:38 ` Pavel Machek [this message]
2005-07-21 15:42   ` Ingo Molnar
2005-07-21 15:44     ` Pavel Machek
2005-07-21 19:42 ` Patrick Mochel
2005-07-22  3:02   ` [linux-pm] " Nigel Cunningham
2005-08-05 12:12   ` Nigel Cunningham
2005-08-06  5:06     ` Patrick Mochel
2005-08-08  0:46       ` Nigel Cunningham
2005-08-08  1:27         ` Con Kolivas
2005-08-08  1:38           ` Nigel Cunningham
2005-08-08 12:18       ` Nigel Cunningham

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=20050721153824.GB1896@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --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