Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752258AbaFFPe7 (ORCPT ); Fri, 6 Jun 2014 11:34:59 -0400 Received: from mail-qg0-f51.google.com ([209.85.192.51]:34738 "EHLO mail-qg0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752192AbaFFPe6 (ORCPT ); Fri, 6 Jun 2014 11:34:58 -0400 Date: Fri, 6 Jun 2014 11:34:54 -0400 From: Tejun Heo To: Michal Hocko Cc: Johannes Weiner , Hugh Dickins , Andrew Morton , KAMEZAWA Hiroyuki , KOSAKI Motohiro , Greg Thelen , Michel Lespinasse , Roman Gushchin , LKML , linux-mm@kvack.org Subject: Re: [PATCH 2/2] memcg: Allow hard guarantee mode for low limit reclaim Message-ID: <20140606153454.GB14001@htj.dyndns.org> References: <20140606144421.GE26253@dhcp22.suse.cz> <1402066010-25901-1-git-send-email-mhocko@suse.cz> <1402066010-25901-2-git-send-email-mhocko@suse.cz> <20140606152914.GA14001@htj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140606152914.GA14001@htj.dyndns.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org A bit of addition. Let's *please* think through how memcg should be configured and different knobs / limits interact with each other and come up with a consistent scheme before adding more shits on top. This "oh I know this use case and maybe that behavior is necessary too, let's add N different and incompatible ways to mix and match them" doesn't fly. Aren't we suppposed to at least have learned that already? -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/