Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1459485
| From | Tomi Valkeinen <tomi.valkeinen@ti.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] omapfb: omapfb-main: Remove deprecated create_singlethread_workqueue |
| Date | 2016-08-10 20:40 +0200 |
| Message-ID | <s4GA4-f8-125@gated-at.bofh.it> (permalink) |
| References | <rQoCZ-1em-3@gated-at.bofh.it> <rQrrc-31L-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On 02/07/16 14:34, Tejun Heo wrote: > On Sat, Jul 02, 2016 at 02:00:56PM +0530, Bhaktipriya Shridhar wrote: >> The workqueue auto_update_work is involved in auto updating mode for >> manual-update displays. omapfb driver uses a delayed work item to update >> the display at a constant rate. >> >> Since these long-running work items aren't involved in memory reclaim in >> any way, system_long_wq has been used. > > Can you please explain why this is long-running? It shouldn't be long-running. update() should only start the transfer to the display. Although if something is not right (the user sets the auto-update frequency to too high), the work could end up waiting for the previous update to finish... It's a debugging feature, so maybe that's not an issue. Tomi
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH] omapfb: omapfb-main: Remove deprecated create_singlethread_workqueue Tomi Valkeinen <tomi.valkeinen@ti.com> - 2016-08-10 20:40 +0200
csiph-web