Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp6189569imu; Wed, 30 Jan 2019 10:17:05 -0800 (PST) X-Google-Smtp-Source: ALg8bN7E8ypTVYuYZ4Gl1ACsNQVmAlGWGBNQDP63Sq4MQfyoflxTgyDldxY3GP75Ftl/0ZuMuHFo X-Received: by 2002:a63:f615:: with SMTP id m21mr28975347pgh.428.1548872225748; Wed, 30 Jan 2019 10:17:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548872225; cv=none; d=google.com; s=arc-20160816; b=sUPS6r0wZyHUsM6ZeFCGZQXdLngK99ooPTZSpDOzFJwM1D39aaJUD2inkcJkG9k0Yj mgA/qx2DuSIkwjyXzZYDM15+MqMKLXPzOsx5/PSL/3FdcUJR1VPbUQxDflD5LCyjoPIa QDaPPJaXzw5jSF1XWp7PBpzl3V9dnlM+CHb77GBcSrA54LL/oYgHuLXbTWwSNHBYQEcC p5FWU8Yomv+iNjXLA/fWxf2NHBO68JX+vTYIuR0xi31eFa3ns6iQo+BGIkw/oQ7TV6Yh 78BGihDvAMUq2SDEWyLD2m7jfLy9Z2c73LsATQBTFAt6vbtWJnUi9Y2ssIX21gYNrLHM 5vEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=3W4UalfXa4tLjbHR50VZ2eyB3qrm+50BnUgHtZmFAQE=; b=psR1b8zcWK+kSkihACiVehPTExnAMHC1faxYfE7QzfoFeDFYLNKXCxz1eRkrddQXKU w1FatOLdApZZlYrvvHPASL6qcIfyYuh99pg/TD3PiDvRVhtNTGkxdpbUqxDvlepwuh9K JhstOWRc12Bkd/MsG5IwFILQdR8+2m1lVoJ5mcIAUqW4+w5HQiLYYPYZ459hxUuGFDBg l/1xp9dz7HyqhxdcAgqPQYoDT/5e2Ezk6GK2Y1Cr2yt9RCKvbRq4idHJSqS/XR05MABL hwV3erzf1FNkG2eVYH3zcWBZuuSNC46Wx8Dorx4aMFTy2IIa1BuQ3Y4Qv1RBOV2elnqw zTOA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t75si2047767pfi.193.2019.01.30.10.16.49; Wed, 30 Jan 2019 10:17:05 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732877AbfA3SQg (ORCPT + 99 others); Wed, 30 Jan 2019 13:16:36 -0500 Received: from mx2.suse.de ([195.135.220.15]:51766 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727402AbfA3SQf (ORCPT ); Wed, 30 Jan 2019 13:16:35 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 7CA96B01B; Wed, 30 Jan 2019 18:16:34 +0000 (UTC) Date: Wed, 30 Jan 2019 19:16:30 +0100 From: Michal Hocko To: Tejun Heo Cc: Johannes Weiner , Chris Down , Andrew Morton , Roman Gushchin , Dennis Zhou , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-mm@kvack.org, kernel-team@fb.com Subject: Re: [PATCH 2/2] mm: Consider subtrees in memory.events Message-ID: <20190130181630.GF18811@dhcp22.suse.cz> References: <20190128151859.GO18811@dhcp22.suse.cz> <20190128154150.GQ50184@devbig004.ftw2.facebook.com> <20190128170526.GQ18811@dhcp22.suse.cz> <20190128174905.GU50184@devbig004.ftw2.facebook.com> <20190129144306.GO18811@dhcp22.suse.cz> <20190129145240.GX50184@devbig004.ftw2.facebook.com> <20190130165058.GA18811@dhcp22.suse.cz> <20190130170658.GY50184@devbig004.ftw2.facebook.com> <20190130174117.GC18811@dhcp22.suse.cz> <20190130175222.GA50184@devbig004.ftw2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190130175222.GA50184@devbig004.ftw2.facebook.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 30-01-19 09:52:22, Tejun Heo wrote: > On Wed, Jan 30, 2019 at 06:41:17PM +0100, Michal Hocko wrote: > > But we are discussing the file name effectively. I do not see a long > > term maintenance burden. Confusing? Probably yes but that is were the > > Cost on user side. > > > documentation would be helpful. > > which is an a lot worse option with way higher total cost. And how exactly does the cost get any smaller with a mount option. The consumer of the API will likely not know there are two modes and check for it to figure out how to interpret those values. Or maybe I still do not follow how exactly is the mount option supposed to work. -- Michal Hocko SUSE Labs