public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Alexey Budankov <alexey.budankov@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Andi Kleen <ak@linux.intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v12 3/3]: perf record: extend trace writing to multi AIO
Date: Thu, 11 Oct 2018 15:45:59 +0200	[thread overview]
Message-ID: <20181011134559.GC29634@krava> (raw)
In-Reply-To: <39da34d3-7198-7514-b000-7bfbf382e526@linux.intel.com>

On Tue, Oct 09, 2018 at 11:59:31AM +0300, Alexey Budankov wrote:

SNIP

> @@ -1568,15 +1596,18 @@ static int parse_clockid(const struct option *opt, const char *str, int unset)
>  
>  #ifdef HAVE_AIO_SUPPORT
>  static int record__aio_parse(const struct option *opt,
> -			     const char *str __maybe_unused,
> +			     const char *str,
>  			     int unset)
>  {
>  	struct record_opts *opts = (struct record_opts *)opt->value;
>  
> -	if (unset)
> +	if (unset) {
>  		opts->nr_cblocks = 0;
> -	else
> -		opts->nr_cblocks = 1;
> +	} else {
> +		opts->nr_cblocks = strtol(str, NULL, 0);
> +		if (!opts->nr_cblocks)
> +			opts->nr_cblocks = 1;
> +	}
>  
>  	return 0;
>  }
> @@ -1886,8 +1917,8 @@ static struct option __record_options[] = {
>  	OPT_BOOLEAN(0, "dry-run", &dry_run,
>  		    "Parse options then exit"),
>  #ifdef HAVE_AIO_SUPPORT
> -	OPT_CALLBACK_NOOPT(0, "aio", &record.opts,
> -		     NULL, "Enable asynchronous trace writing mode",

hum, why removing --aio option? I though we will have:

  perf record --aio ....           # enables aio with default settings
  perf record --aio-cblocks=3 ...  # enabled aio with aio-cblocks=3


jirka

> +	OPT_CALLBACK(0, "aio-cblocks", &record.opts,
> +		     "n", "Use <n> control blocks in asynchronous trace writing mode (max: 4)",
>  		     record__aio_parse),

SNIP

  reply	other threads:[~2018-10-11 13:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09  8:39 [PATCH v12 0/3]: perf: reduce data loss when profiling highly parallel CPU bound workloads Alexey Budankov
2018-10-09  8:57 ` [PATCH v12 1/3] perf util: map data buffer for preserving collected data Alexey Budankov
2018-10-09  8:58 ` [PATCH v12 2/3]: perf record: enable asynchronous trace writing Alexey Budankov
2018-10-11 13:45   ` Jiri Olsa
2018-10-11 16:15     ` Alexey Budankov
2018-10-11 13:45   ` Jiri Olsa
2018-10-11 16:15     ` Alexey Budankov
2018-10-11 13:46   ` Jiri Olsa
2018-10-11 16:29     ` Alexey Budankov
2018-10-11 14:15   ` Jiri Olsa
2018-10-11 16:31     ` Alexey Budankov
2018-10-09  8:59 ` [PATCH v12 3/3]: perf record: extend trace writing to multi AIO Alexey Budankov
2018-10-11 13:45   ` Jiri Olsa [this message]
2018-10-11 16:14     ` Alexey Budankov
2018-10-11 13:46   ` Jiri Olsa
2018-10-11 16:24     ` Alexey Budankov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181011134559.GC29634@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexey.budankov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox