DPDK patches and discussions
 help / color / mirror / Atom feed
From: amit sehas <cun23@yahoo.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_pktmbuf_pool_create performance
Date: Wed, 22 Apr 2020 23:51:32 +0000 (UTC)	[thread overview]
Message-ID: <106152608.25563.1587599492894@mail.yahoo.com> (raw)
In-Reply-To: <356213701.35888.1587599111210@mail.yahoo.com>

 It could also be that this is the function that is the most time consuming:malloc_heap_alloc_on_heap_id()
still looking, I suspect others have encountered such an issue and know what the problem is ...    On Wednesday, April 22, 2020, 04:45:11 PM PDT, amit sehas <cun23@yahoo.com> wrote:  
 
 I switched from utilizing dpdk 16.11.1 to dpdk 18.11.6, in the process I started utilizing --single-file-segments,previously I was utilizing a patch for the same functionality on dpdk-16.11.1. And while linking I somehowneed to link in -lnuma now which I previously did not need to. I don't know what dependencies have beenintroduced by dpdk-18.11.6 but I can no longer build my executables without linking in numa.
That is the only notable change I made. And nothing else has changed, huge pages, tlbs etc are all the same.
yet the performance of rte_pktmbuf_pool_create() has completely tanked, it has become much much slower.I am quite new to dpdk and am not sure what is going on … so I went in with a debugger and this is whati find:
this function call is taking up all the time:  rte_mempool_populate_default()
which in turn invokes the following which is taking all the time:   rte_memzone_reserve_aligned()
which in turn invokes the following which is taking all the time:memzone_reserve_aligned_thread_unsafe()
which in turn invokes the following which is taking all the time: malloc_heap_alloc()
which in turn invokes the following which is taking all the time: malloc_get_numa_socket()

My guess is that somehow numa has started interfering with the performance, but i am not quite sure what to do to fix it...
any help is greatly appreciated, i suspect someone familiar with the above should quickly identify the issue and its remedy...
regards  

      reply	other threads:[~2020-04-22 23:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <356213701.35888.1587599111210.ref@mail.yahoo.com>
2020-04-22 23:45 ` amit sehas
2020-04-22 23:51   ` amit sehas [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=106152608.25563.1587599492894@mail.yahoo.com \
    --to=cun23@yahoo.com \
    --cc=dev@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).