linux-kernel - Re: [PATCH 5/8] __cpu_up: use singlethreaded workqueue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070405120802.GB755@tv-sign.ru>
Date:	Thu, 5 Apr 2007 16:08:02 +0400
From:	Oleg Nesterov <oleg@...sign.ru>
To:	Gautham R Shenoy <ego@...ibm.com>
Cc:	akpm@...ux-foundation.org, paulmck@...ibm.com,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	vatsa@...ibm.com, "Rafael J. Wysocki" <rjw@...k.pl>, mingo@...e.hu,
	dipankar@...ibm.com, dino@...ibm.com,
	masami.hiramatsu.pt@...achi.com
Subject: Re: [PATCH 5/8] __cpu_up: use singlethreaded workqueue

On 04/02, Gautham R Shenoy wrote:
>
> Currently i386 and x86_64 __cpu_up uses the services of the kevents
> workqueue to bring the cpu up. Change this and use kthread workqueue
> instead which is single_threaded and won't be frozen during
> CPU_HOTPLUG.
>
> [...snip...]
>
> +void kthreadwq_queue_work(struct work_struct *work)
> +{
> +	queue_work(helper_wq, work);
> +}
> +
> +int kthreadwq_up()
> +{
> +	return (helper_wq != NULL);
> +}

Off-topic question: can't kernel/kmod.c use this workqueue too instead
of its own khelper_wq?

Oleg.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/