Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp3857263imd; Mon, 29 Oct 2018 13:30:58 -0700 (PDT) X-Google-Smtp-Source: AJdET5fWlw2/zWiEBSzbCSnk9kfi3FX8wPerenoP4y9S5EqN2FzYQrAyKA11cCITMzbZgYUd+rJw X-Received: by 2002:a62:4784:: with SMTP id p4-v6mr14908822pfi.257.1540845058059; Mon, 29 Oct 2018 13:30:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540845058; cv=none; d=google.com; s=arc-20160816; b=KejGk5tAc6pquw8S/kn2rDFNWSFHJMwS/pIOtNQNjZCB++s72MYPrKNrZtNRHW/+Hs FGthNV0l+AL7KuYhEGOJ+BHD5T0hfnXVYdtQ7jPjW/nwDQXzGwXe7rHTC50zWvoG7N3t x7PNivUSJP6GfaiVW4tSahEg4KZgyJfyCc8YazlAWP0R2VaccbcawgCIgZLumKcmbIe/ 4ITsVdrJhmcWhj/t00dyJig4hwHXgd3Tc/gmtotOvqfp1tJZl7GU+5Osqf8kBm5uJXQk 3uMQZzxeUC3hlyGFpdISdn/gA2gvUZucqJ0RLEdY65HQQmaWSq5/LreuwT2XI032dM5r +1fQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject; bh=SnRaCdrrGEgsGb9fUqkGapYSaJ0wqLfI+4RKnaMMbJY=; b=yo87yfByKwbkWQoxeGOvBQfufgaG0u5GW3SYeENBuCOl5cHXiEIfmgiufJe+B3qC9u 6Gik+xTKbEfB8+z66HuCao00FhffXiPaqW1PrsJZHhDyP/L+C3+Ce6QVdTRjHli/IyFa 3mo0xuiGKdIJk+W8K6yZXLuOc5q+CSqgCE2pjy9wS67jWviYBc8nytv5tc/DALXTyjY8 0K7WkccVKyhZiW4z/en8fSz8T5Sfv5sZ2iDImRqD+7K9jqjACFZ6PFC5fiYVoLpb0HcT yXtQanT3EYWNJ0C6mgJRxWQV6+3+AR1DJOhIBktTsmNhVImnecJV4MGHL9JxlsCghqBT oLAg== 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p14-v6si20972815plo.7.2018.10.29.13.30.42; Mon, 29 Oct 2018 13:30:58 -0700 (PDT) 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729700AbeJ3FUR convert rfc822-to-8bit (ORCPT + 99 others); Tue, 30 Oct 2018 01:20:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57248 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729553AbeJ3FUR (ORCPT ); Tue, 30 Oct 2018 01:20:17 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id BDA5E9A760; Mon, 29 Oct 2018 20:30:00 +0000 (UTC) Received: from llong.remote.csb (dhcp-17-8.bos.redhat.com [10.18.17.8]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2CB0D608EF; Mon, 29 Oct 2018 20:30:00 +0000 (UTC) Subject: Re: [PATCH] fs/proc: introduce /proc/stat2 file To: Davidlohr Bueso Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Davidlohr Bueso References: <20181029192521.23059-1-dave@stgolabs.net> <0afed890-7c5a-93ee-cdb9-e30775bd9cf1@redhat.com> <20181029200050.iejuxckzbm742dmw@linux-r8p5> From: Waiman Long Organization: Red Hat Message-ID: <3c5ba85b-5114-c751-0114-ac2cb64c02ea@redhat.com> Date: Mon, 29 Oct 2018 16:29:59 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <20181029200050.iejuxckzbm742dmw@linux-r8p5> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Mon, 29 Oct 2018 20:30:00 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/29/2018 04:00 PM, Davidlohr Bueso wrote: > On Mon, 29 Oct 2018, Waiman Long wrote: > >> I am wondering if /proc/stat_noirqs will be a more descriptive name of >> the intent of this new procfs file or we should just go with the more >> generic stat2 name. > > The reason why I went with '2' instead of a more rescriptive name > was that I think of the call as a drop-in replacement/extention to > stat. Therefore the same fields are maintained, otherwise with > stat_noirqs > I feel like instead of zeroing out, they should just be removed. > > But otoh, I have no strong objection in renaming either. > > Thanks, > Davidlohr I am just questioning the rationale for the stat2 name. I am not advocating to use stat_noirqs neither. BTW, since you are making stat2 compatible with stat, will that be easier from the user API perspective if we use a sysctl parameter to turn on and off IRQs reporting for /proc/stat, for example? I know that there are pros and cons for each approach, I just want to consider all the available options and choose the best one. Cheers, Longman