From: Waiman Long <longman@redhat.com>
To: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>, Roman Gushchin <guro@fb.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Shakeel Butt <shakeelb@google.com>,
Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [PATCH v2 0/2] mm, slab: Extend slab/shrink to shrink all memcg caches
Date: Thu, 18 Jul 2019 14:09:00 -0400 [thread overview]
Message-ID: <4d2ca559-4a59-1368-7b40-f05b9aefe84e@redhat.com> (raw)
In-Reply-To: <20190718180733.18596-1-longman@redhat.com>
On 7/18/19 2:07 PM, Waiman Long wrote:
> v2:
> - Just extend the shrink sysfs file to shrink all memcg caches without
> adding new semantics.
> - Add a patch to report the time of the shrink operation.
>
> This patchset enables the slab/shrink sysfs file to shrink all the
> memcg caches that are associated with the given root cache. The time of
> the shrink operation can now be read from the shrink file.
>
> Waiman Long (2):
> mm, slab: Extend slab/shrink to shrink all memcg caches
> mm, slab: Show last shrink time in us when slab/shrink is read
>
> Documentation/ABI/testing/sysfs-kernel-slab | 14 +++++---
> include/linux/slub_def.h | 1 +
> mm/slab.h | 1 +
> mm/slab_common.c | 37 +++++++++++++++++++++
> mm/slub.c | 14 +++++---
> 5 files changed, 59 insertions(+), 8 deletions(-)
>
Sorry, it is a mistake. Please ignore it.
-Longman
next prev parent reply other threads:[~2019-07-18 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 18:07 [PATCH v2 0/2] mm, slab: Extend slab/shrink to shrink all memcg caches Waiman Long
2019-07-18 18:09 ` Waiman Long [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-17 20:24 Waiman Long
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=4d2ca559-4a59-1368-7b40-f05b9aefe84e@redhat.com \
--to=longman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--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).