Re: Re: [RFC PATCH] suspend/resume performance improvement

[EunTaik Lee]

>> When a task that calls state_store() to suspend
>> the device has used up most of its time slice,
>> suspend sometimes take too long. (User noticeable)
>> 
>> Suspend/resume is a system wide operation.
>> So, instead of depending on a userspace task's time
>> slice, let kworker do the work to avoid a long wait
>> on the runqueue.

> All of that seems to duplicate the existing autosleep.c functionality.

Yes, the effect of using the kworker in autosleep will be same performance-wise.
But if a platform doesn't use the autosleep functionality then we still have the problem.
So doesn't it make sense to implement it for the autosleep-disabled use cases?