DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org, jianbo.liu@linaro.org, viktorin@rehivetech.com
Subject: Re: [dpdk-dev] [PATCH] doc: arm64: document DPDK application profiling methods
Date: Tue, 04 Oct 2016 14:40:47 +0200	[thread overview]
Message-ID: <1570506.0gxVEm9dQ5@xps13> (raw)
In-Reply-To: <1475577630-14318-1-git-send-email-jerin.jacob@caviumnetworks.com>

Thanks for providing a patch so quickly :)

2016-10-04 16:10, Jerin Jacob:
> +The PMU based scheme useful for high accuracy performance profiling.

A verb is missing.

> +Find below the example steps to configure the PMU based cycle counter on an
> +armv8 machine.
> +
> +.. code-block:: console
> +
> +    git clone https://github.com/jerinjacobk/armv8_pmu_cycle_counter_el0
> +    cd armv8_pmu_cycle_counter_el0
> +    make
> +    sudo insmod pmu_el0_cycle_counter.ko
> +    cd $DPDK_DIR
> +    make config T=arm64-armv8a-linuxapp-gcc
> +    echo "CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU=y" >> build/.config
> +    make

What about the ARM 32 code that Jan is using?

> +.. warning::
> +
> +    This method can not be used in production systems as this may alter PMU
> +    state used by standard Linux user space tool like perf.

More details please?

  reply	other threads:[~2016-10-04 12:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 10:40 Jerin Jacob
2016-10-04 12:40 ` Thomas Monjalon [this message]
2016-10-04 12:45   ` Jan Viktorin
2016-10-05  8:43 ` [dpdk-dev] [PATCH v2] " Jerin Jacob
2016-10-26 20:07   ` Thomas Monjalon
2016-11-03 12:30     ` Mcnamara, John
2016-11-04 14:00   ` Mcnamara, John
2016-11-08  3:32   ` [dpdk-dev] [PATCH v3] " Jerin Jacob
2016-11-08  5:57     ` Jianbo Liu
2016-11-10 23:41       ` Thomas Monjalon

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=1570506.0gxVEm9dQ5@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=jianbo.liu@linaro.org \
    --cc=viktorin@rehivetech.com \
    /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;
as well as URLs for NNTP newsgroup(s).