On Thu, 5 Jan 2017, Vlastimil Babka wrote: > Hmm that's probably why it's hard to understand, because "madvise > request" is just setting a vma flag, and the THP allocation (and defrag) > still happens at fault. > > I'm not a fan of either name, so I've tried to implement my own > suggestion. Turns out it was easier than expected, as there's no kernel > boot option for "defer", just for "enabled", so that particular worry > was unfounded. > > And personally I think that it's less confusing when one can enable defer > and madvise together (and not any other combination), than having to dig > up the difference between "defer" and "background". > I think allowing only two options to be combined amongst four available solo options is going to be confusing and then even more difficult for the user to understand what happens when they are combined. Thus, I think these options should only have one settable mode as they have always done. The kernel implementation takes less of a priority to userspace simplicitly, imo, and my patch actually cleans up much of the existing code and ends up adding fewer lines that yours. I consider it an improvement in itself. I don't see the benefit of allowing combined options. -- 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>