linux-kernel - Re: [RFC PATCHv2] usb: move hub init and LED blink work to power efficient 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]

Date:	Fri, 7 Feb 2014 10:20:57 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Zoran Markovic <zoran.markovic@...aro.org>
cc:	lkml <linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>,
	Shaibal Dutta <shaibal.dutta@...adcom.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	Xenia Ragiadakou <burzalodowa@...il.com>,
	Julius Werner <jwerner@...omium.org>,
	Krzysztof Mazur <krzysiek@...lesie.net>,
	Matthias Beyer <mail@...ermatthias.de>,
	Dan Williams <dan.j.williams@...el.com>,
	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	Thomas Pugliese <thomas.pugliese@...il.com>
Subject: Re: [RFC PATCHv2] usb: move hub init and LED blink work to power
 efficient workqueue

Please don't top-post.

On Fri, 7 Feb 2014, Zoran Markovic wrote:

> I believe there may still be use cases where you want to wake up the
> same CPU that scheduled the work.

Won't the majority of cases not care which CPU is used?  Therefore,
shouldn't the default behavior be to use the power-efficient work
queue?

> Thanks for the Ack. Can you please queue this for 3.14?

That's up to Greg KH.  He may decide it's not important enough to go 
into 3.14, and delay it until 3.15.

Alan Stern

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