linux-kernel - Re: [PATCH] genirq: don't use flush_scheduled

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]

Date:	Fri, 17 Jun 2011 11:45:47 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] genirq: don't use flush_scheduled_work() in IRQ affinity
 notifiers

Hello,

On Fri, Jun 17, 2011 at 12:28:06AM +0100, Ben Hutchings wrote:
> 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?

Nope, no need to worry about it.  The only added overhead is the
memory occupied by workqueue itself (which includes small percpu area
but one systemwide one isn't gonna hurt anyone and we've been
decreasing the number of workqueues significantly).  It just serves as
a flush domain.

-- 
tejun
--
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/