On Fri 23-12-16 13:18:51, Nils Holland wrote: > On Fri, Dec 23, 2016 at 11:51:57AM +0100, Michal Hocko wrote: > > TL;DR > > drop the last patch, check whether memory cgroup is enabled and retest > > with cgroup_disable=memory to see whether this is memcg related and if > > it is _not_ then try to test with the patch below > > Right, it seems we might be looking in the right direction! So I > removed the previous patch from my kernel and verified if memory > cgroup was enabled, and indeed, it was. So I booted with > cgroup_disable=memory and ran my ordinary test again ... and in fact, > no ooms! OK, thanks for confirmation. I could have figured that earlier. The pagecache differences in such a short time should have raised the red flag and point towards memcgs... [...] > > I would appreciate to stick with your setup to not pull new unknows into > > the picture. > > No problem! It's just likely that I won't be able to test during the > following days until Dec 27th, but after that I should be back to > normal and thus be able to run further tests in a timely fashion. :-) no problem at all. I will try to cook up a patch in the mean time. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
