From: Ben Hutchings <bhutchings@solarflare.com>
To: Tejun Heo <tj@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: don't use flush_scheduled_work() in IRQ affinity notifiers
Date: Fri, 17 Jun 2011 00:28:06 +0100 [thread overview]
Message-ID: <1308266886.2925.27.camel@bwh-desktop> (raw)
In-Reply-To: <20110615142917.GY8141@htj.dyndns.org>
On Wed, 2011-06-15 at 16:29 +0200, Tejun Heo wrote:
> cd7eab44e9 (genirq: Add IRQ affinity notifiers) added use of
> flush_scheduled_work() which is being deprecated. Add a dedicated
> workqueue and flush it instead of flushing system-wide workqueue.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ben Hutchings <bhutchings@solarflare.com>
> ---
> I'm planning on marking flush_scheduled_work() deprecated in
> linux-next soonish. It would be great if this patch (or something
> else which removes flush_scheduled_work() call somehow) can be
> included in linux-next.
[...]
> --- work.orig/kernel/irq/manage.c
> +++ work/kernel/irq/manage.c
> @@ -74,6 +74,16 @@ EXPORT_SYMBOL(synchronize_irq);
>
> #ifdef CONFIG_SMP
> cpumask_var_t irq_default_affinity;
> +static struct workqueue_struct *irq_affinity_notify_wq;
> +
> +static int __init irq_affinity_init(void)
> +{
> + irq_affinity_notify_wq = alloc_workqueue("irq_affinity_notify", 0, 0);
> + if (!irq_affinity_notify_wq)
> + return -ENOMEM;
> + return 0;
> +}
> +subsys_initcall(irq_affinity_init);
[...]
This facility is enabled on all configurations with NET && SMP &&
GENERIC_HARDIRQS, but at the moment is only useful for some net drivers
(currently only one). So I don't think it should be creating a task at
boot time. Does alloc_workqueue() still create any tasks immediately?
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-06-16 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 14:29 Tejun Heo
2011-06-15 14:30 ` Tejun Heo
2011-06-15 15:25 ` Thomas Gleixner
2011-06-16 23:28 ` Ben Hutchings [this message]
2011-06-17 9:45 ` Tejun Heo
2011-07-14 16:49 ` Ben Hutchings
2011-07-21 5:57 ` Tejun Heo
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=1308266886.2925.27.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®