On Mon, Sep 04, 2017 at 10:30:32AM +0900, Byungchul Park wrote: > On Fri, Sep 01, 2017 at 06:38:52PM +0200, Peter Zijlstra wrote: > > And get tangled up with the workqueue annotation again, no thanks. > > Having the first few works see the thread setup isn't worth it. > > > > And your work_id annotation had the same problem. > > I keep asking you for an example because I really understand you. > > Fix my problematic example with your patches, > > or, > > Show me a problematic scenario with my original code, you expect. > > Whatever, it would be helpful to understand you.
I _really_ don't understand what you're worried about. Is it the kthread create and workqueue init or the pool->lock that is released/acquired in process_one_work()?
