From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758170AbaAJWOp (ORCPT ); Fri, 10 Jan 2014 17:14:45 -0500 Received: from zene.cmpxchg.org ([85.214.230.12]:60196 "EHLO zene.cmpxchg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751658AbaAJWOm (ORCPT ); Fri, 10 Jan 2014 17:14:42 -0500 Date: Fri, 10 Jan 2014 17:14:32 -0500 From: Johannes Weiner To: David Rientjes Cc: Andrew Morton , Michal Hocko , KAMEZAWA Hiroyuki , linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, "Eric W. Biederman" Subject: Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves Message-ID: <20140110221432.GD6963@cmpxchg.org> References: <20131218200434.GA4161@dhcp22.suse.cz> <20131219144134.GH10855@dhcp22.suse.cz> <20140107162503.f751e880410f61a109cdcc2b@linux-foundation.org> <20140109144757.e95616b4280c049b22743a15@linux-foundation.org> <20140109161246.57ea590f00ea5b61fdbf5f11@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 09, 2014 at 04:23:50PM -0800, David Rientjes wrote: > On Thu, 9 Jan 2014, Andrew Morton wrote: > > > > > It was dropped because the other memcg developers disagreed with it. > > > > > > > > > > It was acked-by Michal. Michal acked it before we had most of the discussions and now he is proposing an alternate version of yours, a patch that you are even discussing with him concurrently in another thread. To claim he is still backing your patch because of that initial ack is disingenuous. > > And Johannes? > > > > Johannes is arguing for the same semantics that VMPRESSURE_CRITICAL and/or > memory thresholds provides, which disagrees from the list of solutions > that Documentation/cgroups/memory.txt gives for userspace oom handler > wakeups and is required for any sane implementation. No, he's not and I'm sick of you repeating refuted garbage like this. You have convinced neither me nor Michal that your problem is entirely real and when confronted with doubt you just repeat the same points over and over. The one aspect of your change that we DO agree is valid is now fixed by Michal in a separate attempt because you could not be bothered to incorporate feedback into your patch.