From: Venumadhav Josyula <vjosyula@gmail.com>
To: users@dpdk.org, dev@dpdk.org
Cc: Venumadhav Josyula <vjosyula@parallelwireless.com>
Subject: Re: [dpdk-users] time taken for allocation of mempool.
Date: Mon, 18 Nov 2019 22:15:23 +0530 [thread overview]
Message-ID: <CA+i0PGWLgP66ZYD1hazF+7cGAm8BeNWzKFYtmbJoDzqrQ9Rgqw@mail.gmail.com> (raw)
In-Reply-To: <CA+i0PGV9DxiwwyL-AXCuhMcndZ=11Yk+t6KOub-R7yYuaB1qzQ@mail.gmail.com>
PL note I am using dpdk 18-11...
On Wed, 13 Nov, 2019, 10:37 am Venumadhav Josyula, <vjosyula@gmail.com>
wrote:
> Hi ,
> We are using 'rte_mempool_create' for allocation of flow memory. This has
> been there for a while. We just migrated to dpdk-18.11 from dpdk-17.05. Now
> here is problem statement
>
> Problem statement :
> In new dpdk ( 18.11 ), the 'rte_mempool_create' take approximately ~4.4
> sec for allocation compared to older dpdk (17.05). We have som 8-9 mempools
> for our entire product. We do upfront allocation for all of them ( i.e.
> when dpdk application is coming up). Our application is run to completion
> model.
>
> Questions:-
> i) is that acceptable / has anybody seen such a thing ?
> ii) What has changed between two dpdk versions ( 18.11 v/s 17.05 ) from
> memory perspective ?
>
> Any pointer are welcome.
>
> Thanks & regards
> Venu
>
prev parent reply other threads:[~2019-11-18 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 5:07 Venumadhav Josyula
2019-11-13 5:12 ` Venumadhav Josyula
2019-11-13 8:32 ` [dpdk-users] [dpdk-dev] " Olivier Matz
2019-11-13 9:11 ` Venumadhav Josyula
2019-11-13 9:30 ` Olivier Matz
2019-11-13 9:19 ` Bruce Richardson
2019-11-13 17:26 ` Burakov, Anatoly
2019-11-13 21:01 ` Venumadhav Josyula
2019-11-14 9:44 ` Burakov, Anatoly
2019-11-14 9:50 ` Venumadhav Josyula
2019-11-14 9:57 ` Burakov, Anatoly
2019-11-18 16:43 ` Venumadhav Josyula
2019-12-06 10:47 ` Burakov, Anatoly
2019-12-06 10:49 ` Venumadhav Josyula
2019-11-14 8:12 ` Venumadhav Josyula
2019-11-14 9:49 ` Burakov, Anatoly
2019-11-14 9:53 ` Venumadhav Josyula
2019-11-18 16:45 ` Venumadhav Josyula [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=CA+i0PGWLgP66ZYD1hazF+7cGAm8BeNWzKFYtmbJoDzqrQ9Rgqw@mail.gmail.com \
--to=vjosyula@gmail.com \
--cc=dev@dpdk.org \
--cc=users@dpdk.org \
--cc=vjosyula@parallelwireless.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).