summaryrefslogtreecommitdiffstats
path: root/mm/vmscan.c
diff options
context:
space:
mode:
authorliujinlong <liujinlong@kylinos.cn>2023-09-12 16:59:23 +0800
committerAndrew Morton <akpm@linux-foundation.org>2023-10-04 10:32:27 -0700
commited547ab6f4041c2186df672029eb17f98f44d125 (patch)
treecbd6753526385f874994b853fa987ea7c7b75fa9 /mm/vmscan.c
parent8a0e8bb112af28362514624fc46e20426b4bdf1f (diff)
downloadlinux-stable-ed547ab6f4041c2186df672029eb17f98f44d125.tar.gz
linux-stable-ed547ab6f4041c2186df672029eb17f98f44d125.tar.bz2
linux-stable-ed547ab6f4041c2186df672029eb17f98f44d125.zip
mm: vmscan: modify an easily misunderstood function name
When looking at the code in the memory part, I found that the purpose of the function prepare_scan_countis very different from the function name. It is easy to misunderstand when reading.The function prepare_scan_count mainly completes the assignment of the scan_control structure.Therefore, I suggest that the function name can be changed to prepare_scan_control, which is easier to understand. Link: https://lkml.kernel.org/r/20230912085923.27238-1-liujinlong@kylinos.cn Signed-off-by: liujinlong <liujinlong@kylinos.cn> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/vmscan.c')
-rw-r--r--mm/vmscan.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/mm/vmscan.c b/mm/vmscan.c
index 4a6551510b65..8a3f83e0231e 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -2208,7 +2208,7 @@ enum scan_balance {
SCAN_FILE,
};
-static void prepare_scan_count(pg_data_t *pgdat, struct scan_control *sc)
+static void prepare_scan_control(pg_data_t *pgdat, struct scan_control *sc)
{
unsigned long file;
struct lruvec *target_lruvec;
@@ -5834,7 +5834,7 @@ again:
nr_reclaimed = sc->nr_reclaimed;
nr_scanned = sc->nr_scanned;
- prepare_scan_count(pgdat, sc);
+ prepare_scan_control(pgdat, sc);
shrink_node_memcgs(pgdat, sc);