linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Li Zefan <lizefan@huawei.com>, Johannes Weiner <hannes@cmpxchg.org>
Cc: cgroups@vger.kernel.org, kernel-team@fb.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH cgroup/for-4.17 2/2] Subject: cgroup: Limit event generation frequency
Date: Thu, 26 Apr 2018 14:35:14 -0700	[thread overview]
Message-ID: <20180426213514.GV1911913@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180323194753.GF2149215@devbig577.frc2.facebook.com>

On Fri, Mar 23, 2018 at 12:47:53PM -0700, Tejun Heo wrote:
> ".events" files generate file modified event to notify userland of
> possible new events.  Some of the events can be quite bursty
> (e.g. memory high event) and generating notification each time is
> costly and pointless.
> 
> This patch implements a event rate limit mechanism.  If a new
> notification is requested before 10ms has passed since the previous
> notification, the new notification is delayed till then.
> 
> As this only delays from the second notification on in a given close
> cluster of notifications, userland reactions to notifications
> shouldn't be delayed at all in most cases while avoiding notification
> storms.
> 
> Signed-off-by: Tejun Heo <tj@kernel.org>

Applied 1-2 to cgroup/for-4.18.

Thanks.

-- 
tejun

      reply	other threads:[~2018-04-26 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 19:47 [PATCH cgroup/for-4.17 1/2] cgroup: Explicitly remove core interface files Tejun Heo
2018-03-23 19:47 ` [PATCH cgroup/for-4.17 2/2] Subject: cgroup: Limit event generation frequency Tejun Heo
2018-04-26 21:35   ` 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=20180426213514.GV1911913@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    /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;
as well as URLs for NNTP newsgroup(s).