Received-SPF: pass (google.com: domain of linux-kernel+bounces-16482-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
From: Bixuan Cui <cuibixuan@vivo.com>
To: akpm@linux-foundation.org,
	rostedt@goodmis.org,
	mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com
Cc: linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	linux-mm@kvack.org,
	opensource.kernel@vivo.com,
	cuibixuan@vivo.com
Subject: [PATCH -next v5 0/2] Make memory reclamation measurable
Date: Thu,  4 Jan 2024 02:05:25 -0800
Message-Id: <20240104100527.3908-1-cuibixuan@vivo.com>
Content-Type: text/plain
Precedence: bulk
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0:
	=?us-ascii?Q?0luzV+Icj6u23Q4lyciz4F2DeayqpJhpV7U3KByrbVAenOSbj0L3d6+hLHlk?=
 =?us-ascii?Q?Hu0u6/8B3LBU9tUSip6z4R8HaAGt3M3yGaPzsmXALIY1DaQbvAHq2hVVgBd7?=
 =?us-ascii?Q?LFv0MbzIofAlHuNHQSi08XpqTp4NjLpea9S3Vx+jCjYg4rgK1vEw3WKR4eHO?=
 =?us-ascii?Q?7yaYlq1v3u9Oi3i5yjXOL202iILLKKafkZGmi7nPkmf+NSc4t8K72nkRA/Xd?=
 =?us-ascii?Q?oezNRipd8ZakFZzsPexBWtFSSbzLnU8xXZojfxoTWnpitmX1kW8yPt04VZbt?=
 =?us-ascii?Q?fEKGAs++rtaqlAm9emJX5CskJo8U2uZFC1AIRVGGl2iMiIc1uOujrveDZWpY?=
 =?us-ascii?Q?hESUtiosOZWSV7MtxdXGbDfY3MJMaFOy5kFcxdoDdYxgFPEoi0tRhrn53XhH?=
 =?us-ascii?Q?G6mucvDaA6yzVBJ3jamduj7HIrthLPhZcILWr0lz2u2+hE1GR06hcw6OPKQl?=
 =?us-ascii?Q?dn1wi++9QuDZ5qEUANHpHVJSzwEvFBaGyT3BmoU4d0omZa2JmPAbQWRXAR0F?=
 =?us-ascii?Q?LAn18uZQCBTSa4SQYGObxr7SlzeBGb/igxeFHrqvlHGX9zT0lMlL9Vockp9j?=
 =?us-ascii?Q?rMYV/9fr6zmvcUZlk2Jy2/z1smeB+khrQ6Sq56FqIJiIdaiM54IEQivBODrA?=
 =?us-ascii?Q?QkFvX4E++53GiiJVT4xkS6Xiq9IBoOEICI7YYK9dJ/4Xo1XVHzqOggdvJJBa?=
 =?us-ascii?Q?pNRg9cZNlW+u6iCn202dBXc1UnTJrVz14JPHg9ysPbO/cCZHQyqMCvvaVihE?=
 =?us-ascii?Q?L8hw9fgdOVRcJzzrcVtMv8QBC6TLil1Fx2RvIoO0KVee/eLj5gicLtpfyFdV?=
 =?us-ascii?Q?9y5FNHsaIIT7QIHNS9EkTulJ5W0FlS1fUlzyV59kF0bEwcuCYcs/HDCXh+eX?=
 =?us-ascii?Q?ln1sKjIveg8ZYnaxhEzBZty70HgDi4KvQGNALP3vTWUWUGAJQXL6VnvNdNfX?=
 =?us-ascii?Q?Hw2Petljw7aZbTF0Q9dj4r70x1/USwQYEwW4AlwcHzO/vWO/m+92wYPOL1ai?=
 =?us-ascii?Q?2AX0aMw0EG7gQeuRgVu3As6qsI+Rejmhn8M3zUISuyTOrrRkracOxV2Uu8EK?=
 =?us-ascii?Q?JgCFsHk19fP7oya1fnfqZogEd8w6Ccscrcz7CcPcOXHjKeCm6lga+0MXCI2O?=
 =?us-ascii?Q?jQcY92g3mrIOPwFk0rg61DT7aW2PLDwCoEeSoQ36ISMtzHuyY/daOMTbby0z?=
 =?us-ascii?Q?LcUKuR/WpXgB1rKkv71kvDH1oJSYOVLSwkW2nuxfZga0oBb+Irp/RxGKE9SG?=
 =?us-ascii?Q?n43BE/hIM+p5EWOM7paZiUGfuM72T1cxxaJtD2ttzKcGeJ/jq3h/JZgvhmQD?=
 =?us-ascii?Q?gcJx0p/3B/YX/IOq1Mt02N0+WAboY98uBzCxRxrjaN8jglhLP9q/7hGBGU6F?=
 =?us-ascii?Q?5ztnsVqqVq3yq4iKF5Xii66Q5A/hKy77ZSmTobbOn3Oapy084dNvJJJGsoEz?=
 =?us-ascii?Q?sTtLt2xFNdhgUZmZrdxd8A/pBFcBkC4qOXa3ztdHV1gofaos8ISpdel2Nws5?=
 =?us-ascii?Q?8u+h5Q/KMKMJkHl8IJHZvGHP3Tm3yGVuaaKsqbyZy8CrxrU34u27ress6Der?=
 =?us-ascii?Q?rYPCGA834psS+xuLYcvl0t2w9XreuWe5kYf1IcU+?=
X-OriginatorOrg: vivo.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0c6b9e98-a59d-4866-3914-08dc0d0cc128
X-MS-Exchange-CrossTenant-AuthSource: TYZPR06MB4045.apcprd06.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Jan 2024 10:06:01.7166
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 923e42dc-48d5-4cbe-b582-1a797a6412ed
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: xSX6LT5gd/9LChbG7diqDdWH3/vnVgBEyH2XV07fTw6UBMS+nneppFTtvtnM8gWko9digxkIGRUsuCw/rGcusA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SEZPR06MB5879

When the system memory is low, kswapd reclaims the memory. The key steps
of memory reclamation include
1.shrink_lruvec
  * shrink_active_list, moves folios from the active LRU to the inactive LRU
  * shrink_inactive_list, shrink lru from inactive LRU list
2.shrink_slab
  * shrinker->count_objects(), calculates the freeable memory
  * shrinker->scan_objects(), reclaims the slab memory

The existing tracers in the vmscan are as follows:

--do_try_to_free_pages
--shrink_zones
--trace_mm_vmscan_node_reclaim_begin (tracer)
--shrink_node
--shrink_node_memcgs
  --trace_mm_vmscan_memcg_shrink_begin (tracer)
  --shrink_lruvec
    --shrink_list
      --shrink_active_list
	  --trace_mm_vmscan_lru_shrink_active (tracer)
      --shrink_inactive_list
	  --trace_mm_vmscan_lru_shrink_inactive (tracer)
    --shrink_active_list
  --shrink_slab
    --do_shrink_slab
    --shrinker->count_objects()
    --trace_mm_shrink_slab_start (tracer)
    --shrinker->scan_objects()
    --trace_mm_shrink_slab_end (tracer)
  --trace_mm_vmscan_memcg_shrink_end (tracer)
--trace_mm_vmscan_node_reclaim_end (tracer)

If we get the duration and quantity of shrink lru and slab,
then we can measure the memory recycling, as follows

Measuring memory reclamation with bpf:
  LRU FILE:
	CPU COMM 	ShrinkActive(us) ShrinkInactive(us)  Reclaim(page)
	7   kswapd0	 	26		51		32
	7   kswapd0		52		47		13
  SLAB:
	CPU COMM 		OBJ_NAME		Count_Dur(us) Freeable(page) Scan_Dur(us) Reclaim(page)
	 1  kswapd0		super_cache_scan.cfi_jt     2		    341		   3225		128
	 7  kswapd0		super_cache_scan.cfi_jt     0		    2247	   8524		1024
	 7  kswapd0	        super_cache_scan.cfi_jt     2367	    0		   0		0

For this, add the new tracer to shrink_active_list/shrink_inactive_list
and shrinker->count_objects().

Changes:
v5: * Use 'DECLARE_EVENT_CLASS(mm_vmscan_lru_shrink_start_template' to
replace 'RACE_EVENT(mm_vmscan_lru_shrink_inactive/active_start'
    * Add the explanation for adding new shrink lru events into 'mm: vmscan: add new event to trace shrink lru'
v4: Add Reviewed-by and Changlog to every patch.
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 to fix build error.

cuibixuan (2):
  mm: shrinker: add new event to trace shrink count
  mm: vmscan: add new event to trace shrink lru

 include/trace/events/vmscan.h | 80 ++++++++++++++++++++++++++++++++++-
 mm/shrinker.c                 |  4 ++
 mm/vmscan.c                   | 11 +++--
 3 files changed, 90 insertions(+), 5 deletions(-)

-- 
2.17.1