From: Tejun Heo <tj@kernel.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] workqueue: always pass cascading responsibility to the next flusher
Date: Tue, 27 May 2014 10:27:36 -0400 [thread overview]
Message-ID: <20140527142736.GD22767@htj.dyndns.org> (raw)
In-Reply-To: <20140527142443.GC22767@htj.dyndns.org>
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
prev parent reply other threads:[~2014-05-27 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 11:58 Lai Jiangshan
2014-05-26 11:58 ` [PATCH 2/2] workqueue: remove the unneeded "while(true)" loop and adjust the indent Lai Jiangshan
2014-05-27 14:24 ` [PATCH 1/2] workqueue: always pass cascading responsibility to the next flusher Tejun Heo
2014-05-27 14:27 ` Tejun Heo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140527142736.GD22767@htj.dyndns.org \
--to=tj@kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome