From: Bixuan Cui <cuibixuan@vivo.com>
To: Yu Zhao <yuzhao@google.com>
Cc: rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-mm@kvack.org, opensource.kernel@vivo.com
Subject: Re: [PATCH -next v4 2/2] mm: vmscan: add new event to trace shrink lru
Date: Thu, 21 Dec 2023 11:16:28 +0800 [thread overview]
Message-ID: <65adb1a4-51c5-40f7-b345-f278abb4ef4d@vivo.com> (raw)
In-Reply-To: <CAOUHufZjxjra9Cfw8YC2eA-xsikPw=K5=1ew55hKTdYhMwjUig@mail.gmail.com>
在 2023/12/21 1:54, Yu Zhao 写道:
>> Signed-off-by: Bixuan Cui<cuibixuan@vivo.com>
>> Reviewed-by: Andrew Morton<akpm@linux-foundation.org>
>> ---
>> v4: Add Reviewed-by and Changlog to every patch.
> Where did Andrew provide his Reviewed-by?Hi,
I just want to add Reviewed-by to my patch to thank the reveiw of Steven
and Andrew.:-)
>
>> v2: Modify trace_mm_vmscan_lru_shrink_inactive() in evict_folios() at the same time to fix build error.
> The reason v3 was NAK'ed was not mentioned or fixed in v4.
>
> So NAK again.
The build error pointed out by Andrew has been fixed in [mm: vmscan: add
new event to trace shrink lru]:
@@ -4524,9 +4528,10 @@ static int evict_folios(struct lruvec *lruvec,
struct scan_control *sc, int swap
if (list_empty(&list))
return scanned;
retry:
+ trace_mm_vmscan_lru_shrink_inactive_start(pgdat->node_id);
reclaimed = shrink_folio_list(&list, pgdat, sc, &stat, false);
sc->nr_reclaimed += reclaimed;
- trace_mm_vmscan_lru_shrink_inactive(pgdat->node_id,
+ trace_mm_vmscan_lru_shrink_inactive_end(pgdat->node_id,
scanned, reclaimed, &stat, sc->priority,
type ? LRU_INACTIVE_FILE : LRU_INACTIVE_ANON);
Are there any other reasons for NAK? And thank you for your review.
Thanks
Bixuan Cui
prev parent reply other threads:[~2023-12-21 3:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 1:21 [PATCH -next v4 0/2] Make memory reclamation measurable Bixuan Cui
2023-12-20 1:21 ` [PATCH -next v4 1/2] mm: shrinker: add new event to trace shrink count Bixuan Cui
2023-12-20 1:21 ` [PATCH -next v4 2/2] mm: vmscan: add new event to trace shrink lru Bixuan Cui
2023-12-20 17:36 ` Steven Rostedt
2023-12-20 17:54 ` Yu Zhao
2023-12-21 3:16 ` Bixuan Cui [this message]
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=65adb1a4-51c5-40f7-b345-f278abb4ef4d@vivo.com \
--to=cuibixuan@vivo.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=rostedt@goodmis.org \
--cc=yuzhao@google.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