[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1549899005-7760-1-git-send-email-l.luba@partner.samsung.com>
Date: Mon, 11 Feb 2019 16:30:03 +0100
From: Lukasz Luba <l.luba@...tner.samsung.com>
To: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Cc: b.zolnierkie@...sung.com, myungjoo.ham@...sung.com,
cw00.choi@...sung.com, kyungmin.park@...sung.com,
m.szyprowski@...sung.com, s.nawrocki@...sung.com, tkjos@...gle.com,
joel@...lfernandes.org, chris.diamand@....com, mka@...omium.org,
Lukasz Luba <l.luba@...tner.samsung.com>
Subject: [PATCH v2 0/2] drivers: devfreq: fix and optimize workqueue
mechanism
This patch set changes workqueue related features in devfreq framework.
First patch switches to delayed work instead of deferred.
The second switches to regular system work and deletes custom 'devfreq'.
Using deferred work in this context might harm the system performance.
When the CPU enters idle, deferred work is not fired. The devfreq device's
utilization does not have to be connected with a particular CPU.
The drivers for GPUs, Network on Chip, cache L3 rely on devfreq governor.
They all are missing opportunity to check the HW state and react when
the deferred work is not fired.
A corner test case, when Dynamic Memory Controller is utilized by CPUs running
on full speed, might show x5 worse performance if the crucial CPU is in idle.
Changes:
v2:
- single patch split into two
- added cover letter
link for the previous version and discussion:
https://marc.info/?l=linux-pm&m=154904631226997&w=2
Regards,
Lukasz Luba
Lukasz Luba (2):
drivers: devfreq: change devfreq workqueue mechanism
drivers: devfreq: change deferred work into delayed
drivers/devfreq/devfreq.c | 27 +++++++--------------------
1 file changed, 7 insertions(+), 20 deletions(-)
--
2.7.4
Powered by blists - more mailing lists