From: Andrew Morton <akpm@linux-foundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: hannes@cmpxchg.org, mhocko@kernel.org, vdavydov.dev@gmail.com,
guro@fb.com, riel@surriel.com, linux-kernel@vger.kernel.org,
kernel-team@fb.com, cgroups@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCHSET] mm, memcontrol: Implement memory.swap.events
Date: Mon, 26 Mar 2018 14:39:31 -0700 [thread overview]
Message-ID: <20180326143931.41a15320fd4d4af26c86d42e@linux-foundation.org> (raw)
In-Reply-To: <20180324165127.701194-1-tj@kernel.org>
On Sat, 24 Mar 2018 09:51:25 -0700 Tejun Heo <tj@kernel.org> wrote:
> This patchset implements memory.swap.events which contains max and
> fail events so that userland can monitor and respond to swap running
> out. It contains the following two patches.
>
> 0001-mm-memcontrol-Move-swap-charge-handling-into-get_swa.patch
> 0002-mm-memcontrol-Implement-memory.swap.events.patch
>
> This patchset is on top of the "cgroup/for-4.17: Make cgroup_rstat
> available to controllers" patchset[1] and "mm, memcontrol: Make
> cgroup_rstat available to controllers" patchset[2] and also available
> in the following git branch.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-memcg-swap.events
This doesn't appear to be in linux-next yet. It should be by now if it's
targeted at 4.17?
next prev parent reply other threads:[~2018-03-26 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 16:51 [PATCHSET] mm, memcontrol: Implement memory.swap.events Tejun Heo
2018-03-24 16:51 ` [PATCH 1/2] mm, memcontrol: Move swap charge handling into get_swap_page() Tejun Heo
2018-03-24 16:51 ` [PATCH 2/2] mm, memcontrol: Implement memory.swap.events Tejun Heo
2018-03-26 21:39 ` Andrew Morton [this message]
2018-03-27 13:52 ` [PATCHSET] " Tejun Heo
2018-04-12 14:13 ` Michal Hocko
2018-04-12 15:38 ` Tejun Heo
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=20180326143931.41a15320fd4d4af26c86d42e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=riel@surriel.com \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.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).