DPDK usage discussions
 help / color / mirror / Atom feed
From: Junguk Cho <jmanbal@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] MEMPOOL contentions
Date: Fri, 2 Sep 2016 12:37:59 -0600	[thread overview]
Message-ID: <CAMNaBtPZ8uKvR+kDsKwP3ySPMwMKxqYAZXwCE1q3X7ZkHWpDeg@mail.gmail.com> (raw)
In-Reply-To: <1532B974-9164-47AE-ADBE-3BE74E590619@intel.com>

Hi, Keith.

Thank you for reply.

I reached those setup.
My question is when I run my app after these setup, how to get statistics?
In other words, where can I see some statistics like file or screen?


Thanks,
Junguk

2016-09-02 12:35 GMT-06:00 Wiles, Keith <keith.wiles@intel.com>:

>
> Regards,
> Keith
>
> > On Sep 2, 2016, at 1:27 PM, Junguk Cho <jmanbal@gmail.com> wrote:
> >
> > Hi,
> >
> > In my setup, I created one mempool which is shared with 5 rings.
> > So, I want to know statistics of contentions between 5 rings like taking
> > time to get one mbuf.
> > In the manual, there are some options like CONFIG_RTE_LIBRTE_MEMPOOL_
> DEBUG.
>
> Add the option to your config file uses in the build of DPDK and set the
> value to ‘y’ instead of ’n’.
>
> Example: edit or copy say defconfig_x86_64-native-linuxapp-gcc and add
> something like this;
>
> CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG=y
>
> Then rebuild DPDK using something like ‘make install
> T=x86_64-native-linux-gcc -j'
>
> > However, I don't know how to use it.
> >
> > Is there any reference?
> >
> > Intuitively, as the number of rings are increase, I think the contention
> > happened frequently.
> > So, to avoid this, is increasing CONFIG_RTE_MEMPOOL_CACHE_MAX_SIZE one
> > solution?
> >
> >
> > Thanks,
> > Junguk
>
>

      reply	other threads:[~2016-09-02 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 18:27 Junguk Cho
2016-09-02 18:35 ` Wiles, Keith
2016-09-02 18:37   ` Junguk Cho [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=CAMNaBtPZ8uKvR+kDsKwP3ySPMwMKxqYAZXwCE1q3X7ZkHWpDeg@mail.gmail.com \
    --to=jmanbal@gmail.com \
    --cc=keith.wiles@intel.com \
    --cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).