diff options
| author |   Michal Hocko <mhocko@kernel.org> | 2016-05-19 17:11:34 -0700 |
|---|---|---|
| committer |   Linus Torvalds <torvalds@linux-foundation.org> | 2016-05-19 19:12:14 -0700 |
| commit | fda3d69be9fe7a24ad32b840cb2ed7c30b6ba1c9 (patch) | |
| tree | 573d6c40ed432dccaad8c8fb77ff5b2781150462 /mm/page_alloc.c | |
| parent | mm/mempolicy.c: vma_migratable() can return bool (diff) | |
| download | linux-rng-fda3d69be9fe7a24ad32b840cb2ed7c30b6ba1c9.tar.xz linux-rng-fda3d69be9fe7a24ad32b840cb2ed7c30b6ba1c9.zip | |
mm/memcontrol.c:mem_cgroup_select_victim_node(): clarify comment
> The comment seems to have not much to do with the code?
I guess the comment tries to say that the code path is triggered when we
charge the page which happens _before_ it is added to the LRU list and
so last_scanned_node might contain the stale data.
Cc: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/page_alloc.c')
0 files changed, 0 insertions, 0 deletions