summaryrefslogtreecommitdiffstats
path: root/include/net/sctp/structs.h
diff options
context:
space:
mode:
authorVlastimil Babka <vbabka@suse.cz>2023-09-14 15:16:39 +0200
committerAndrew Morton <akpm@linux-foundation.org>2023-10-04 19:32:29 +0200
commit3dfbb555c98ac55b9d911f9af0e35014b445fb41 (patch)
treee294c7edce2ed542177f8a89964ff2b1f1fd9709 /include/net/sctp/structs.h
parenttrace-vmscan-postprocess: sync with tracepoints updates (diff)
downloadlinux-3dfbb555c98ac55b9d911f9af0e35014b445fb41.tar.xz
linux-3dfbb555c98ac55b9d911f9af0e35014b445fb41.zip
mm, vmscan: remove ISOLATE_UNMAPPED
This isolate_mode_t flag is effectively unused since 89f6c88a6ab4 ("mm: __isolate_lru_page_prepare() in isolate_migratepages_block()") as sc->may_unmap is now checked directly (and only node_reclaim has a mode that sets it to 0). The last remaining place is mm_vmscan_lru_isolate tracepoint for the isolate_mode parameter. That one was mainly used to indicate the active/inactive mode, which the trace-vmscan-postprocess.pl script consumed, but that got silently broken. After fixing the script by the previous patch, it does not need the isolate_mode anymore. So just remove the parameter and with that the whole ISOLATE_UNMAPPED flag. Link: https://lkml.kernel.org/r/20230914131637.12204-4-vbabka@suse.cz Signed-off-by: Vlastimil Babka <vbabka@suse.cz> Cc: Hugh Dickins <hughd@google.com> Cc: Mel Gorman <mgorman@techsingularity.net> Cc: Vlastimil Babka <vbabka@suse.cz> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'include/net/sctp/structs.h')
0 files changed, 0 insertions, 0 deletions