vmscan: comment too_many_isolated()
Subsystems (3)
PATCH RESEND 1/1 vmscan: comment too_many_isolated()
Comment "Why it's doing so" rather than "What it does" as proposed by Andrew Morton.
Reviewed-by KOSAKI Motohiro <[email protected]>
Reviewed-by Minchan Kim <[email protected]>
Reviewed-by Rik van Riel <[email protected]>
Signed-off-by Wu Fengguang <[email protected]>
--- mm/vmscan.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
mm/vmscan.c +5 -1
@@ -1177,7 +1177,11 @@ int isolate_lru_page(struct page *page) }/* -* Are there way too many processes in the direct reclaim path already? +* A direct reclaimer may isolate SWAP_CLUSTER_MAX pages from the LRU list and +* then get resheduled. When there are massive number of tasks doing page +* allocation, such sleeping direct reclaimers may keep piling up on each CPU, +* the LRU list will go small and be scanned faster than necessary, leading to +* unnecessary swapping, thrashing and OOM. */ static int too_many_isolated (struct zone *zone,int file,struct scan_control *sc)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>