The patch titled
Subject: mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-checkpatch-fixes
has been added to the -mm tree. Its filename is
mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-checkpatch-fixes.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-checkpatch-fixes.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-checkpatch-fixes.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: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-checkpatch-fixes
reflow comment to avoid unnecessary 80-col overflows
Cc: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
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-checkpatch-fixes mm/vmscan.c
--- a/mm/vmscan.c~mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-checkpatch-fixes
+++ a/mm/vmscan.c
@@ -600,13 +600,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 akpm@xxxxxxxxxxxxxxxxxxxx are
i-need-old-gcc.patch
arm-arch-arm-include-asm-pageh-needs-personalityh.patch
ocfs2-return-erofs-when-filesystem-becomes-read-only-checkpatch-fixes.patch
mm.patch
tools-modifying-page-types-to-include-shared-map-counts-checkpatch-fixes.patch
tools-adding-support-for-idle-page-tracking-to-tool-fix.patch
mm-drop-vm_bug_on-from-__get_free_pages-fix.patch
mm-list_lruc-fold-__list_lru_count_one-into-its-caller.patch
mm-fadvise-fix-signed-overflow-ubsan-complaint-fix.patch
mm-clear-shrinker-bit-if-there-are-no-objects-related-to-memcg-checkpatch-fixes.patch
mm-sparsemem-defer-the-ms-section_mem_map-clearing-fix.patch
list_lru-prefetch-neighboring-list-entries-before-acquiring-lock-fix.patch
mm-oom-cgroup-aware-oom-killer-fix.patch
mm-oom-cgroup-aware-oom-killer-fix-2.patch
mm-oom-docs-describe-the-cgroup-aware-oom-killer-fix-2-fix.patch
kernel-hung_taskc-allow-to-set-checking-interval-separately-from-timeout-fix.patch
linux-next-rejects.patch
kernel-forkc-export-kernel_thread-to-modules.patch
slab-leaks3-default-y.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
