[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87132478-5dfd-4cde-820d-83427c18f4d1@vivo.com>
Date: Fri, 15 Dec 2023 09:06:07 +0800
From: Bixuan Cui <cuibixuan@...o.com>
To: Yu Zhao <yuzhao@...gle.com>
Cc: akpm@...ux-foundation.org, mm-commits@...r.kernel.org,
rostedt@...dmis.org, mhiramat@...nel.org, mathieu.desnoyers@...icios.com,
opensource.kernel@...o.com, Linux-MM <linux-mm@...ck.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next v3 2/2] mm: vmscan: add new event to trace shrink
lru
在 2023/12/14 11:59, Yu Zhao 写道:
>> Example of output:
>> kswapd0-103 [007] ..... 1098.353020: mm_vmscan_lru_shrink_active_start: nid=0
>> kswapd0-103 [007] ..... 1098.353040: mm_vmscan_lru_shrink_active_end: nid=0 nr_taken=32 nr_active=0 nr_deactivated=32 nr_referenced=0 priority=6 flags=RECLAIM_WB_FILE|RECLAIM_WB_ASYNC
>> kswapd0-103 [007] ..... 1098.353040: mm_vmscan_lru_shrink_inactive_start: nid=0
>> kswapd0-103 [007] ..... 1098.353094: mm_vmscan_lru_shrink_inactive_end: nid=0 nr_scanned=32 nr_reclaimed=0 nr_dirty=0 nr_writeback=0 nr_congested=0 nr_immediate=0 nr_activate_anon=0 nr_activate_file=0 nr_ref_keep=32 nr_unmap_fail=0 priority=6 flags=RECLAIM_WB_ANON|RECLAIM_WB_ASYNC
>> kswapd0-103 [007] ..... 1098.353094: mm_vmscan_lru_shrink_inactive_start: nid=0
>> kswapd0-103 [007] ..... 1098.353162: mm_vmscan_lru_shrink_inactive_end: nid=0 nr_scanned=32 nr_reclaimed=21 nr_dirty=0 nr_writeback=0 nr_congested=0 nr_immediate=0 nr_activate_anon=0 nr_activate_file=0 nr_ref_keep=11 nr_unmap_fail=0 priority=6 flags=RECLAIM_WB_FILE|RECLAIM_WB_ASYNC
>>
>> Signed-off-by: Bixuan Cui<cuibixuan@...o.com>
> NAK.
>
> A _start should always be paired with an _end unless there is a good
> reason not to.
Yes, I want to get the duration of shrink lru and slab (including
shrink_active_list()/shrink_inactive_list()/shrinker->count_objects()/shrinker->scan_objects()),and
then calculate the memory recycling rate.
>
> mm-commits@ is the wrong mailing list to submit MM patches.
Thanks for reminding.
>
> Is the build error Andrew pointed out earlier fixed? If so, where is
> it credited to him?
Build error has been fixed in v2 patch, changes log:
v3: Swap the positions of 'nid' and 'freeable' to prevent the hole in
the trace event.
v2: Modify trace_mm_vmscan_lru_shrink_inactive() in evict_folios() at
the same time.
Thanks
Bixuan Cui
Powered by blists - more mailing lists