On Fri 10-02-17 08:51:49, Greg KH wrote: > On Fri, Feb 10, 2017 at 08:21:32AM +0100, peter enderborg wrote: [...] > > Until then we have to polish this version as good as we can. It is > > essential for android as it is now. > > But if no one is willing to do the work to fix the reported issues, why > should it remain? Can you do the work here? You're already working on > fixing some of the issues in a differnt way, why not do the "real work" > here instead for everyone to benifit from? Well, to be honest, I do not think that the current code is easily fixable. The approach was wrong from the day 1. Abusing slab shrinkers is just a bad place to stick this logic. This all belongs to the userspace. For that we need a proper mm pressure notification which is supposed to be vmpressure but that one also doesn't seem to work all that great. So rather than trying to fix unfixable I would stronly suggest focusing on making vmpressure work reliably. -- Michal Hocko SUSE Labs _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
