On Wed 30-03-16 15:32:17, Peter Zijlstra wrote: > On Mon, Feb 29, 2016 at 01:58:14PM +0100, Michal Hocko wrote: > > I have tested on x86 with OOM situations with high mmap_sem contention > > (basically many parallel page faults racing with many parallel mmap/munmap > > tight loops) so the waiters for the write locks are routinely interrupted > > by SIGKILL. > > Aside from the one niggle (as per the other email) they look good to me > and I would take them through the tip/locking tree. Thanks for the review! I understand that tip/locking would be the most appropriate place but I am wondering whether this causes some issues with the follow up patches which use this new API and which I expect to go via Andrew's tree. That being said I do not care much but then we have a potential dependency between mmotm and tip/locking. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
