From: Daniel Kan <dan@nyansa.com>
To: Selvaganapathy Chidambaram <selvaganapathyc@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Profiling tools for DPDK applications running on VM inside ESXi server
Date: Fri, 28 Feb 2014 22:00:34 -0800 [thread overview]
Message-ID: <A4289825-98FC-4EFC-A965-FC6C3AF9CA7F@nyansa.com> (raw)
In-Reply-To: <CAB3M1-HJ-6B-LF1L20VSuNT49YFFWmRNK6UJm-vE4Ev4iipepw@mail.gmail.com>
Thanks for the tip. Maybe it’s better to optimize code on bare metal before moving to VM.
Dan
On Feb 28, 2014, at 6:12 PM, Selvaganapathy Chidambaram <selvaganapathyc@gmail.com> wrote:
> Hi Dan,
>
> When we tried, perf did not work in ESX, it only works in KVM. oprofile works in timer mode in ESX.
>
> Thanks,
> Selvaganapathy.C.
>
>
> On Fri, Feb 28, 2014 at 6:07 PM, Daniel Kan <dan@nyansa.com> wrote:
> Hi,
> I’m wondering which profilers are best for profiling DPDK applications running on VM: perf, oprofile, vtune? The first 2 are open sourced while vtune is commercial. DPDK apps are running on ubuntu 12.04 and centos 6.5. Thanks.
>
> Dan
>
prev parent reply other threads:[~2014-03-01 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 2:07 Daniel Kan
2014-03-01 2:12 ` Selvaganapathy Chidambaram
2014-03-01 6:00 ` Daniel Kan [this message]
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=A4289825-98FC-4EFC-A965-FC6C3AF9CA7F@nyansa.com \
--to=dan@nyansa.com \
--cc=dev@dpdk.org \
--cc=selvaganapathyc@gmail.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).