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: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Andi Kleen <ak@linux.intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/3] perf record: allocate affinity masks
Date: Wed, 12 Dec 2018 13:15:24 +0100	[thread overview]
Message-ID: <20181212121524.GC25240@krava> (raw)
In-Reply-To: <afb88628-7a04-3c36-2bc9-b5f5774f8e8f@linux.intel.com>

On Wed, Dec 12, 2018 at 10:38:23AM +0300, Alexey Budankov wrote:
> 
> Allocate affinity option and masks for mmap data buffers and
> record thread as well as initialize allocated objects.
> 
> Signed-off-by: Alexey Budankov <alexey.budankov@linux.intel.com>
> ---
>  tools/perf/builtin-record.c | 11 ++++++++++-
>  tools/perf/perf.h           |  5 +++++
>  tools/perf/util/evlist.c    |  6 +++---
>  tools/perf/util/evlist.h    |  2 +-
>  tools/perf/util/mmap.c      |  2 ++
>  tools/perf/util/mmap.h      |  3 ++-
>  6 files changed, 23 insertions(+), 6 deletions(-)
> 
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 882285fb9f64..4979719e54ae 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -81,6 +81,7 @@ struct record {
>  	bool			timestamp_boundary;
>  	struct switch_output	switch_output;
>  	unsigned long long	samples;
> +	cpu_set_t		affinity_mask;
>  };
>  
>  static volatile int auxtrace_record__snapshot_started;
> @@ -533,7 +534,8 @@ static int record__mmap_evlist(struct record *rec,
>  
>  	if (perf_evlist__mmap_ex(evlist, opts->mmap_pages,
>  				 opts->auxtrace_mmap_pages,
> -				 opts->auxtrace_snapshot_mode, opts->nr_cblocks) < 0) {
> +				 opts->auxtrace_snapshot_mode,
> +				 opts->nr_cblocks, opts->affinity) < 0) {
>  		if (errno == EPERM) {
>  			pr_err("Permission error mapping pages.\n"
>  			       "Consider increasing "
> @@ -1980,6 +1982,9 @@ int cmd_record(int argc, const char **argv)
>  # undef REASON
>  #endif
>  
> +	CPU_ZERO(&rec->affinity_mask);
> +	rec->opts.affinity = PERF_AFFINITY_SYS;
> +
>  	rec->evlist = perf_evlist__new();
>  	if (rec->evlist == NULL)
>  		return -ENOMEM;
> @@ -2143,6 +2148,10 @@ int cmd_record(int argc, const char **argv)
>  	if (verbose > 0)
>  		pr_info("nr_cblocks: %d\n", rec->opts.nr_cblocks);
>  
> +	pr_debug("affinity (UNSET:%d, NODE:%d, CPU:%d) = %d\n",
> +		 PERF_AFFINITY_SYS, PERF_AFFINITY_NODE,
> +		 PERF_AFFINITY_CPU, rec->opts.affinity);

please make this user friendly and display the actual string like "UNSET/NODE/CPU"

> +
>  	err = __cmd_record(&record, argc, argv);
>  out:
>  	perf_evlist__delete(rec->evlist);
> diff --git a/tools/perf/perf.h b/tools/perf/perf.h
> index 388c6dd128b8..08e75815de2f 100644
> --- a/tools/perf/perf.h
> +++ b/tools/perf/perf.h
> @@ -83,8 +83,13 @@ struct record_opts {
>  	clockid_t    clockid;
>  	u64          clockid_res_ns;
>  	int	     nr_cblocks;
> +	int	     affinity;
>  };
>  
> +#define PERF_AFFINITY_SYS  0
> +#define PERF_AFFINITY_NODE 1
> +#define PERF_AFFINITY_CPU  2

please put those to enum

thanks,
jirka

  parent reply	other threads:[~2018-12-12 12:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  7:30 [PATCH v1 0/3] Reduce NUMA related overhead in perf record profiling on large server systems Alexey Budankov
2018-12-12  7:40 ` [PATCH v1 2/3] perf record: apply affinity masks when reading mmap buffers Alexey Budankov
2018-12-12 12:14   ` Jiri Olsa
2018-12-13  6:26     ` Alexey Budankov
2018-12-12 12:15   ` Jiri Olsa
2018-12-13  7:04     ` Alexey Budankov
2018-12-12 12:15   ` Jiri Olsa
2018-12-13  6:26     ` Alexey Budankov
2018-12-12  7:44 ` [PATCH v1 3/3] perf record: implement --affinity=node|cpu option Alexey Budankov
2018-12-12  7:54 ` [PATCH v1 1/3] perf record: allocate affinity masks Alexey Budankov
     [not found] ` <afb88628-7a04-3c36-2bc9-b5f5774f8e8f@linux.intel.com>
2018-12-12 12:15   ` Jiri Olsa [this message]
2018-12-13  6:26     ` 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=20181212121524.GC25240@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