Re: [RFC PATCHv2] usb: move hub init and LED blink work to power efficient workqueue

2014-02-07 Thread Alan Stern
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-effic

Re: [RFC PATCHv2] usb: move hub init and LED blink work to power efficient workqueue

2014-02-07 Thread Greg Kroah-Hartman
On Fri, Feb 07, 2014 at 10:20:57AM -0500, Alan Stern wrote: > 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 i

Re: [RFC PATCHv2] usb: move hub init and LED blink work to power efficient workqueue

2014-02-07 Thread Zoran Markovic
I believe there may still be use cases where you want to wake up the same CPU that scheduled the work. Thanks for the Ack. Can you please queue this for 3.14? Regards, Zoran On 2 February 2014 08:10, Alan Stern wrote: > On Sat, 1 Feb 2014, Zoran Markovic wrote: > >> From: Shaibal Dutta >> >> A

Re: [RFC PATCHv2] usb: move hub init and LED blink work to power efficient workqueue

2014-02-02 Thread Alan Stern
On Sat, 1 Feb 2014, Zoran Markovic wrote: > From: Shaibal Dutta > > Allow the scheduler to select the best CPU to handle hub initalization > and LED blinking work. This extends idle residency times on idle CPUs > and conserves power. > > This functionality is enabled when CONFIG_WQ_POWER_EFFICI