Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755605AbbHDInH (ORCPT ); Tue, 4 Aug 2015 04:43:07 -0400 Received: from casper.infradead.org ([85.118.1.10]:54235 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755531AbbHDInE (ORCPT ); Tue, 4 Aug 2015 04:43:04 -0400 Date: Tue, 4 Aug 2015 10:42:57 +0200 From: Peter Zijlstra To: Tejun Heo Cc: mingo@redhat.com, hannes@cmpxchg.org, lizefan@huawei.com, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com Subject: Re: [PATCH 1/3] cgroup: define controller file conventions Message-ID: <20150804084257.GJ25159@twins.programming.kicks-ass.net> References: <1438641689-14655-1-git-send-email-tj@kernel.org> <1438641689-14655-2-git-send-email-tj@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1438641689-14655-2-git-send-email-tj@kernel.org> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 638 Lines: 12 On Mon, Aug 03, 2015 at 06:41:27PM -0400, Tejun Heo wrote: > +- If a controller implements an absolute resource limit, the control > + knob should be named "max". The special token "max" should be used > + to represent no limit for both reading and writing. So what do you do with minimal resource guarantees? That's still an absolute resource limit and 'max' is obviously the wrong name. -- 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/