Mel Gorman <mgorman@xxxxxxxxxxxxxxxxxxx> writes: > On Fri, Sep 09, 2016 at 08:31:27AM -0700, Linus Torvalds wrote: >> On Fri, Sep 9, 2016 at 2:59 AM, Mel Gorman <mgorman@xxxxxxxxxxxxxxxxxxx> wrote: >> > >> > The progression of this series has been unsatisfactory. >> >> Yeah, I have to say that I particularly don't like patch #1. > > There isn't many ways to make it prettier. Making it nicer is partially > hindered by the fact that tree_lock is IRQ-safe for IO completions but > even if that was addressed there might be lock ordering issues. > >> It's some >> rather nasty complexity for dubious gains, and holding the lock for >> longer times might have downsides. >> > > Kswapd reclaim would delay a parallel truncation for example. Doubtful it > matters but the possibility is there. > > The gain in swapping is nice but ramdisk is excessively artifical. It might > matter if someone reported it made a big difference swapping to faster > storage like SSD or NVMe although the cases where fast swap is important > are few -- overcommitted host with multiple idle VMs with a new active VM > starting is the only one that springs to mind. I will try to provide some data for the NVMe disk. I think the trend is that the performance of the disk is increasing fast and will continue in the near future at least. We found we cannot saturate the latest NVMe disk when swapping because of locking issues in swap and page reclaim path. The swap usage problem could be a "Chicken and Egg" problem. Because swap performance is poor, nobody uses swap, and because nobody uses swap, nobody works on improving the performance of the swap. With the faster and faster storage device, swap could be more popular in the future if we optimize its performance to catch up with the performance of the storage. >> So I think this series is one of those "we need to find that it makes >> a big positive impact" to make sense. >> > > Agreed. I don't mind leaving it on the back burner unless Dave reports > it really helps or a new bug report about realistic tree_lock contention > shows up. Best Regards, Huang, Ying -- 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>