* + mm-skip-retry-when-new-limit-is-not-below-old-one-in-page_counter_set_max.patch added to mm-unstable branch
@ 2022-08-22 21:27 Andrew Morton
0 siblings, 0 replies; only message in thread
From: Andrew Morton @ 2022-08-22 21:27 UTC (permalink / raw)
To: mm-commits, minhquangbui99, akpm
The patch titled
Subject: mm: Skip retry when new limit is not below old one in page_counter_set_max
has been added to the -mm mm-unstable branch. Its filename is
mm-skip-retry-when-new-limit-is-not-below-old-one-in-page_counter_set_max.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-skip-retry-when-new-limit-is-not-below-old-one-in-page_counter_set_max.patch
This patch will later appear in the mm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
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 via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: Bui Quang Minh <minhquangbui99@gmail.com>
Subject: mm: Skip retry when new limit is not below old one in page_counter_set_max
Date: Sun, 21 Aug 2022 22:40:55 +0700
In page_counter_set_max, we want to make sure the new limit is not below
the concurrently-changing counter value. We read the counter and check
that the limit is not below the counter before the swap. After the swap,
we read the counter again and retry in case the counter is incremented as
this may violate the requirement. Even though the page_counter_try_charge
can see the old limit, it is guaranteed that the counter is not above the
old limit after the increment. So in case the new limit is not below the
old limit, the counter is guaranteed to be not above the new limit too.
We can skip the retry in this case to optimize a little bit.
Link: https://lkml.kernel.org/r/20220821154055.109635-1-minhquangbui99@gmail.com
Signed-off-by: Bui Quang Minh <minhquangbui99@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/page_counter.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/page_counter.c~mm-skip-retry-when-new-limit-is-not-below-old-one-in-page_counter_set_max
+++ a/mm/page_counter.c
@@ -193,7 +193,7 @@ int page_counter_set_max(struct page_cou
old = xchg(&counter->max, nr_pages);
- if (page_counter_read(counter) <= usage)
+ if (page_counter_read(counter) <= usage || nr_pages >= old)
return 0;
counter->max = old;
_
Patches currently in -mm which might be from minhquangbui99@gmail.com are
mm-skip-retry-when-new-limit-is-not-below-old-one-in-page_counter_set_max.patch
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-08-22 21:27 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-08-22 21:27 + mm-skip-retry-when-new-limit-is-not-below-old-one-in-page_counter_set_max.patch added to mm-unstable branch Andrew Morton
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.