Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes:
> From: Johannes Berg <johannes.berg@xxxxxxxxx>
>
> Since wiphy work items can run pretty much arbitrary
> code in the stack/driver, it can take longer to run
> all of this, so we shouldn't be using system_wq via
> schedule_work(). Also, we lock the wiphy (which is
> the reason this exists), so use system_unbound_wq.
>
> Reported-by: Kalle Valo <kvalo@xxxxxxxxxx>
> Fixes: a3ee4dc84c4e ("wifi: cfg80211: add a work abstraction with special semantics")
> Signed-off-by: Johannes Berg <johannes.berg@xxxxxxxxx>
Thanks!
So the background of this is that I enabled
CONFIG_WQ_CPU_INTENSIVE_REPORT on my ath11k test box and saw:
[ 290.475631] workqueue: cfg80211_wiphy_work [cfg80211] hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
With Johannes' patch I don't see it anymore so:
Tested-by: Kalle Valo <kvalo@xxxxxxxxxx>
I do see one other warning about gc_worker but that's from netfilter and
nothing to do with wireless:
[ 440.486683] workqueue: gc_worker hogged CPU for >10000us 128 times, consider switching to WQ_UNBOUND
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
