On Tue 03-05-16 14:00:39, Tim Chen wrote: [...] > include/linux/swap.h | 29 ++- > mm/swap_state.c | 253 +++++++++++++----- > mm/swapfile.c | 215 +++++++++++++-- > mm/vmscan.c | 725 ++++++++++++++++++++++++++++++++++++++------------- > 4 files changed, 945 insertions(+), 277 deletions(-) This is rather large change for a normally rare path. We have been trying to preserve the anonymous memory as much as possible and rather push the page cache out. In fact swappiness is ignored most of the time for the vast majority of workloads. So this would help anonymous mostly workloads and I am really wondering whether this is something worth bothering without further and deeper rethinking of our current reclaim strategy. I fully realize that the swap out sucks and that the new storage technologies might change the way how we think about anonymous memory being so "special" wrt. disk based caches but I would like to see a stronger use case than "we have been playing with some artificial use case and it scales better" -- Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>