The patch titled
Subject: mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-v9
has been added to the -mm tree. Its filename is
mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-v9.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-v9.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-v9.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
Subject: mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-v9
Link: http://lkml.kernel.org/r/153112561772.4097.11011071937553113003.stgit@localhost.localdomain
Signed-off-by: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
Acked-by: Vladimir Davydov <vdavydov.dev@xxxxxxxxx>
Tested-by: Shakeel Butt <shakeelb@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/vmscan.c | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff -puN mm/vmscan.c~mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-v9 mm/vmscan.c
--- a/mm/vmscan.c~mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-v9
+++ a/mm/vmscan.c
@@ -599,13 +599,14 @@ static unsigned long shrink_slab_memcg(g
if (ret == SHRINK_EMPTY) {
clear_bit(i, map->map);
/*
- * After the shrinker reported that it had no objects to free,
- * but before we cleared the corresponding bit in the memcg
- * shrinker map, a new object might have been added. To make
- * sure, we have the bit set in this case, we invoke the
- * shrinker one more time and re-set the bit if it reports that
- * it is not empty anymore. The memory barrier here pairs with
- * the barrier in memcg_set_shrinker_bit():
+ * After the shrinker reported that it had no objects to
+ * free, but before we cleared the corresponding bit in
+ * the memcg shrinker map, a new object might have been
+ * added. To make sure, we have the bit set in this
+ * case, we invoke the shrinker one more time and reset
+ * the bit if it reports that it is not empty anymore.
+ * The memory barrier here pairs with the barrier in
+ * memcg_set_shrinker_bit():
*
* list_lru_add() shrink_slab_memcg()
* list_add_tail() clear_bit()
_
Patches currently in -mm which might be from ktkhai@xxxxxxxxxxxxx are
memcg-remove-memcg_cgroup-id-from-idr-on-mem_cgroup_css_alloc-failure.patch
list_lru-combine-code-under-the-same-define.patch
mm-introduce-config_memcg_kmem-as-combination-of-config_memcg-config_slob.patch
mm-assign-id-to-every-memcg-aware-shrinker.patch
mm-assign-id-to-every-memcg-aware-shrinker-v9.patch
memcg-move-up-for_each_mem_cgroup-_tree-defines.patch
mm-assign-memcg-aware-shrinkers-bitmap-to-memcg.patch
mm-assign-memcg-aware-shrinkers-bitmap-to-memcg-v9.patch
mm-refactoring-in-workingset_init.patch
mm-refactoring-in-workingset_init-v9.patch
fs-refactoring-in-alloc_super.patch
fs-propagate-shrinker-id-to-list_lru.patch
list_lru-add-memcg-argument-to-list_lru_from_kmem.patch
list_lru-pass-dst_memcg-argument-to-memcg_drain_list_lru_node.patch
list_lru-pass-lru-argument-to-memcg_drain_list_lru_node.patch
mm-export-mem_cgroup_is_root.patch
mm-set-bit-in-memcg-shrinker-bitmap-on-first-list_lru-item-apearance.patch
mm-set-bit-in-memcg-shrinker-bitmap-on-first-list_lru-item-apearance-v9.patch
mm-iterate-only-over-charged-shrinkers-during-memcg-shrink_slab.patch
mm-iterate-only-over-charged-shrinkers-during-memcg-shrink_slab-v9.patch
mm-add-shrink_empty-shrinker-methods-return-value.patch
mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg.patch
mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-v9.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
