workqueue with WQ_HIGHPRI set, has been used here
since a delay can cause the outcome to miss the refresh cycle.
Since there are only a fixed number of work items, explicit concurrency
limit is unnecessary here.
Signed-off-by: Bhaktipriya Shridhar
---
Changes in v2:
-Used a dedicated work
emory reclaim in
any way, system_long_wq has been used.
Work item has been flushed in ttm_mem_global_release() to ensure that
nothing is pending when the driver is disconnected.
Signed-off-by: Bhaktipriya Shridhar
---
drivers/gpu/drm/ttm/ttm_memory.c | 7 ++-
1 file changed, 2 insertions(
, WQ_MEM_RECLAIM has not been set.
Since there are only a fixed number of work items, explicit concurrency
limit is unnecessary here.
Signed-off-by: Bhaktipriya Shridhar
---
drivers/gpu/drm/radeon/radeon_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/radeon
) to ensure that there
are no pending tasks while disconnecting the driver.
Signed-off-by: Bhaktipriya Shridhar
---
drivers/gpu/drm/qxl/qxl_cmd.c | 2 +-
drivers/gpu/drm/qxl/qxl_drv.h | 1 -
drivers/gpu/drm/qxl/qxl_kms.c | 6 +-
3 files changed, 2 insertions(+), 7 deletions(-)
diff --git
een removed because with the
usage of system_wq, calls to destroy_workqueue() have been dropped,
which makes the label unnecessary.
Workitem is sync cancelled in dsicm_cancel_ulps_work() which is called
in dsicm_remove() to ensure that there are no workitems pending when the
driver is disconnected.
Please ignore this mail.
Thanks,
Bhaktipriya
On Tue, Jun 28, 2016 at 10:48 PM, Bhaktipriya Shridhar
wrote:
> The workqueue g2d_workq has only a single workitem(&g2d->runqueue_work)
> and hence doesn't require ordering. Also, it is not being used on a
> memory rec
Please ignore this mail.
Thanks,
Bhaktipriya
On Tue, Jun 28, 2016 at 10:56 PM, Bhaktipriya Shridhar
wrote:
> alloc_workqueue replaces deprecated create_singlethread_workqueue().
>
> A dedicated workqueue has been used since work items need to be flushed
> as a group rather than
Please ignore this mail.
Thanks,
Bhaktipriya
On Tue, Jun 28, 2016 at 10:53 PM, Bhaktipriya Shridhar
wrote:
> The workqueue "workqueue" has only a single workitem(&ddata->ulps_work) per
> panel_drv_data and hence doesn't require ordering.
> Also, it is not bein
Please ignore this mail.
On Tue, Jun 28, 2016 at 10:48 PM, Bhaktipriya Shridhar
wrote:
> The workqueue g2d_workq has only a single workitem(&g2d->runqueue_work)
> and hence doesn't require ordering. Also, it is not being used on a
> memory reclaim path. Hence, the singlet
, WQ_MEM_RECLAIM has not been set.
Since there are only a fixed number of work items, explicit concurrency
limit is unnecessary here.
Signed-off-by: Bhaktipriya Shridhar
---
drivers/gpu/drm/radeon/radeon_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/radeon
een removed because with the
usage of system_wq, calls to destroy_workqueue() have been dropped,
which makes the label unnecessary.
Workitem is sync cancelled in dsicm_cancel_ulps_work() which is called
in dsicm_remove() to ensure that there are no workitems pending when the
driver is disconnected.
with the usage of system_wq, calls to destroy_workqueue() have
been dropped, which makes the label unnecessary.
Work item has been flushed in g2d_remove() to ensure that nothing is
pending when the driver disconnects.
Signed-off-by: Bhaktipriya Shridhar
---
drivers/gpu/drm/exynos/exynos_drm_g2d
Ping!
Thanks,
Bhaktipriya
On Mon, Jun 20, 2016 at 8:41 PM, Tejun Heo wrote:
> On Sat, Jun 18, 2016 at 02:36:32PM +0530, Bhaktipriya Shridhar wrote:
>> System workqueues have been able to handle high level of concurrency
>> for a long time now and there's no reason to use
cality or global ordering guarantees unless the target CPU is
explicitly specified and thus the increase of local concurrency
shouldn't make any difference.
cancel_work_sync() has been used in _host1x_free_syncpt_irq() to ensure
that no work is pending by the time exit path runs.
Signed-off-by:
.
Signed-off-by: Bhaktipriya Shridhar
---
drivers/block/mtip32xx/mtip32xx.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/block/mtip32xx/mtip32xx.c
b/drivers/block/mtip32xx/mtip32xx.c
index 6053e46..4bfb75b 100644
--- a/drivers/block/mtip32xx/mtip32xx.c
+++ b/drivers
Thanks Oded. Sending v3 right away :)
On Sun, May 29, 2016 at 8:31 PM, Oded Gabbay wrote:
> On Thu, May 26, 2016 at 10:37 PM, Bhaktipriya Shridhar
> wrote:
>> alloc_workqueue replaces deprecated create_workqueue().
>>
>> create_workqueue has been replaced with alloc_w
.
flush_workqueue is unnecessary since destroy_workqueue() itself calls
drain_workqueue() which flushes repeatedly till the workqueue
becomes empty.
Hence flush_workqueue has been removed.
Signed-off-by: Bhaktipriya Shridhar
---
Changes in v3:
- Corrected space between arguments.
drivers/gpu/drm/amd
to ensure that work is not pending by the time
exit path runs.
Signed-off-by: Bhaktipriya Shridhar
---
drivers/gpu/host1x/dev.h| 1 -
drivers/gpu/host1x/hw/intr_hw.c | 8 ++--
drivers/gpu/host1x/intr.c | 4
3 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/driv
.
flush_workqueue is unnecessary since destroy_workqueue() itself calls
drain_workqueue() which flushes repeatedly till the workqueue becomes empty.
Hence flush_workqueue has been removed.
Signed-off-by: Bhaktipriya Shridhar
---
Changes in v2:
- added explanation for setting concurrency value to
19 matches
Mail list logo
