lkml.org 
[lkml]   [2014]   [May]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] workqueue: always pass cascading responsibility to the next flusher
On Tue, May 27, 2014 at 10:24:43AM -0400, Tejun Heo wrote:
> So, I think hiding latencies which can easily in millisecs range is
> important. It isn't a performance optimization. It almost becomes a
> correctness issue when the problem is severely hit and the amount of

Another way to think about it is considering flushing an event
notification mechanism. Doing the above can reliably induce tens of
millisecs of latency in event delivery on the right combination of
work items and flush patterns, which isn't acceptable. We sure still
can fail to such state when the flush color space is exhausted but
this is a lot easier to trigger.

Thanks.

--
tejun


\
 
 \ /
  Last update: 2014-05-27 17:01    [W:0.050 / U:0.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site