should_continue

Name:Reclaim/compaction is used for high-order allocation requests. It reclaims* order-0 pages before compacting the zone. should_continue_reclaim() returns* true if more pages should be reclaimed such that when the page allocator

Proto:static inline bool should_continue_reclaim(struct pglist_data *pgdat, unsigned long nr_reclaimed, struct scan_control *sc)

Type:bool

Parameter:

Type	Parameter	Name
struct pglist_data *	pgdat
unsigned long	nr_reclaimed
struct scan_control *	sc

2599

If Not Use reclaim/compaction for costly allocs or under memory pressure Then Return false

2612

If Not nr_reclaimed Then Return false

2616

When z <= The highest zone to isolate pages for reclaim from cycle

2617

zone = node_zones[z]

2618

If Not Returns true if a zone has pages managed by the buddy allocator.* All the reclaim decisions have to use this function rather than* populated_zone(). If the whole zone is reserved then we can easily* end up with populated_zone() && !managed_zone(). Then Continue

2622

Case compaction_suitable(zone, Allocation order , 0, The highest zone to isolate pages for reclaim from ) == COMPACT_SUCCESS

2623

Case compaction_suitable(zone, Allocation order , 0, The highest zone to isolate pages for reclaim from ) == COMPACT_CONTINUE

2624

Return false

2625

Default

2635

pages_for_compaction = Number of free order-0 pages that should be available above given watermark* to make sure compaction has reasonable chance of not running out of free* pages that it needs to isolate as migration target during its work.

2636

inactive_lru_pages = node_page_state(pgdat, NR_INACTIVE_FILE)

2637

If get_nr_swap_pages() > 0 Then inactive_lru_pages += node_page_state(pgdat, NR_INACTIVE_ANON)

2640

Return inactive_lru_pages > pages_for_compaction

**Caller**
Name	Describe
shrink_node

Source code conversion tool public plug-in interface	X
Support c/c++/esqlc/java Oracle/Informix/Mysql Plug-in can realize: logical Report Code generation and batch code conversion

Function report