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 <[email protected]> wrote: > On Sat, 1 Feb 2014, Zoran Markovic wrote: > >> From: Shaibal Dutta <[email protected]> >> >> 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_EFFICIENT is selected. >> >> Cc: Greg Kroah-Hartman <[email protected]> >> Cc: Alan Stern <[email protected]> >> Cc: Sarah Sharp <[email protected]> >> Cc: Xenia Ragiadakou <[email protected]> >> Cc: Julius Werner <[email protected]> >> Cc: Krzysztof Mazur <[email protected]> >> Cc: Matthias Beyer <[email protected]> >> Cc: Dan Williams <[email protected]> >> Cc: Mathias Nyman <[email protected]> >> Cc: Thomas Pugliese <[email protected]> >> Signed-off-by: Shaibal Dutta <[email protected]> >> [[email protected]: Rebased to latest kernel. Added commit message. >> Changed reference from system to power efficient workqueue for LEDs in >> check_highspeed() and hub_port_connect_change().] >> Signed-off-by: Zoran Markovic <[email protected]> > > Acked-off-by: Alan Stern <[email protected]> > > Is there some reason why schedule_delayed_work() doesn't use the > power-efficient work queue by default? > > Alan Stern > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
