From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752965AbeDKLCI (ORCPT ); Wed, 11 Apr 2018 07:02:08 -0400 Received: from mga02.intel.com ([134.134.136.20]:23934 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752929AbeDKLCG (ORCPT ); Wed, 11 Apr 2018 07:02:06 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,435,1517904000"; d="scan'208";a="49894780" Message-ID: <1523444522.2753.218.camel@gmail.com> Subject: Re: [PATCH][v3] tools/power turbostat: if --max_loop, print for specific time of loops From: Artem Bityutskiy Reply-To: dedekind1@gmail.com To: Yu Chen , Len Brown Cc: Rafael J Wysocki , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Date: Wed, 11 Apr 2018 14:02:02 +0300 In-Reply-To: <20180411103038.12735-1-yu.c.chen@intel.com> References: <20180411103038.12735-1-yu.c.chen@intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 (3.26.6-1.fc27) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org A couple of nitpicks. On Wed, 2018-04-11 at 18:30 +0800, Yu Chen wrote: > @@ -48,6 +48,7 @@ char *proc_stat = "/proc/stat"; > FILE *outf; > int *fd_percpu; > struct timespec interval_ts = {5, 0}; > +int iterations; OK, out of several choices, you selected "iterations". > unsigned int debug; > unsigned int quiet; > unsigned int sums_need_wide_columns; > @@ -470,6 +471,7 @@ void help(void) > " {core | package | j,k,l..m,n-p }\n" > "--quiet skip decoding system configuration header\n" > "--interval sec Override default 5-second measurement interval\n" > + "--iterations loops The number of loops if interval is specified\n" Since "iterations" is the term, be consistent and do not mix it with "loops". Who knows may be the "loops" term will be used for something else in the future. Use something like this: "--iterations count Number of measurement iterations (requires ' --interval')" > print this help mkk > "--list list column headers only\n" > "--out file create or truncate \"file\" for all output\n" > @@ -2565,6 +2567,7 @@ void turbostat_loop() > { > int retval; > int restarted = 0; > + int loops = 0; Please, name variables in a consistent manner, this should really be something like 'int iters = 0'. Or may be 'done_iters', or something. But not "loops". > @@ -4999,6 +5010,7 @@ void cmdline(int argc, char **argv) > {"Dump", no_argument, 0, 'D'}, > {"debug", no_argument, 0, 'd'}, /* internal, not documented */ > {"interval", required_argument, 0, 'i'}, > + {"iterations", required_argument, 0, 't'}, If you used term "count", you could have consistent long and short option names, like '--count / -c'. I find '--iterations / -t' to be inconsistent, and harder to remember the short option, because I think about time, not "iterations" when I see -t.