[lkml]   [2015]   [Nov]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v3 00/22] kthread: Use kthread worker API more widely
On Wed, Nov 18, 2015 at 02:25:05PM +0100, Petr Mladek wrote:
> My intention is to make it easier to manipulate and maintain kthreads.
> Especially, I want to replace all the custom main cycles with a
> generic one. Also I want to make the kthreads sleep in a consistent
> state in a common place when there is no work.
> My first attempt was with a brand new API (iterant kthread), see
> . But I was
> directed to improve the existing kthread worker API. This is
> the 3rd iteration of the new direction.
> 1st patch: add support to check if a timer callback is being called
> 2nd..12th patches: improve the existing kthread worker API
> 13th..18th, 20th, 22nd patches: convert several kthreads into
> the kthread worker API, namely: khugepaged, ring buffer
> benchmark, hung_task, kmemleak, ipmi, IB/fmr_pool,
> memstick/r592, intel_powerclamp
> 21st, 23rd patches: do some preparation steps; they usually do
> some clean up that makes sense even without the conversion.
> Changes against v2:
> + used worker->lock to synchronize the operations with the work
> instead of the PENDING bit as suggested by Tejun Heo; it simplified
> the implementation in several ways
> + added timer_active(); used it together with del_timer_sync()
> to cancel the work a less tricky way
> + removed the controversial conversion of the RCU kthreads

Thank you! ;-)

Thanx, Paul

 \ /
  Last update: 2015-11-18 16:01    [W:0.202 / U:6.420 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site