From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 38991A0353;
	Wed, 13 Nov 2019 06:08:38 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 250E12C15;
	Wed, 13 Nov 2019 06:08:37 +0100 (CET)
Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com
 [209.85.167.47]) by dpdk.org (Postfix) with ESMTP id AB8122BF9;
 Wed, 13 Nov 2019 06:08:35 +0100 (CET)
Received: by mail-lf1-f47.google.com with SMTP id v8so770793lfa.12;
 Tue, 12 Nov 2019 21:08:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to:cc;
 bh=/sJ0W5TUZZ3FLWHs5+a86oytZdnZDGRXwa8LBjcbtEI=;
 b=iviQHT2NmYij0PXD0fhjK0+ED+Gh1pEPKix+CYO35Vrm8GCoWXdctfdJrFyG7RNiNu
 70XhwNC1Ly8/xAEek9pNvzWDHvLUXX6NMAm1fs94enZB0iq2RlsRRIAOc2uoJbi0+Al0
 xY/y5Gytq0RJ0SROJ9m4dM0PzWrZZLRp1+kqOHcw55PZUvL/2IP9HRsvZNZYnefVLe9Q
 ePH243VDnov9R5LTY6ucoI7U/zPpscEy04cnZ3kHuUVd9Ofx2pVw9bmRTXJdcRdY4Zdp
 bCQAmq9ZmDP+soogqNP8IXhcxpWbolJN6AioZQQGaZva4GKU/u1gplsge39sj4YJ17hc
 SDMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc;
 bh=/sJ0W5TUZZ3FLWHs5+a86oytZdnZDGRXwa8LBjcbtEI=;
 b=HsS7w44rYR4Bd/no+6dU8EuUC0E5Rw5BuZlIgHb9NldhR+tviUJVbbs27PZsd4yz7E
 VhKDwta80nR/Q7aVsi/XQ0FjUG/b8MTROBdEjFW1JQRTPWeVjQY7o1+qwxTzr17hA4yV
 eCPjg9aLvd5z4STSpGwMov9WT36dJaed2jfEe3z0/cVn6rWaQTvuNt+YXmo2CNiRUcTf
 Hd6iNJOuS4TTqNfVM6sB42joLUhOxXotoz+wS5w2+kOJKsw5n9eP/VgWKTADQeaY5U5w
 82tQztcU8POPplpfmT5Kc5a+CYxtKKYB3BRolQD67wf7U9kDiw8qMJwcuXP5fd5mBR61
 PCqw==
X-Gm-Message-State: APjAAAVujBILV2nMDVkTzXLXLTnTd1SibBTyLdGhxk1Ojt62J17QHj0e
 94H7LgcAF3DTgBa+S6k5nXNghFttHQJMddPkj/8qd8Hri/4=
X-Google-Smtp-Source: APXvYqwSPB77AppXKu+HIbThL42cPAmJ/EbCMO5syP1aWLhGHqANA8h6d++scbUu0p3vEfBpG7t5o3L//aoY3KxL7RA=
X-Received: by 2002:a19:c386:: with SMTP id t128mr1038743lff.7.1573621714581; 
 Tue, 12 Nov 2019 21:08:34 -0800 (PST)
MIME-Version: 1.0
From: Venumadhav Josyula <vjosyula@gmail.com>
Date: Wed, 13 Nov 2019 10:37:57 +0530
Message-ID: <CA+i0PGV9DxiwwyL-AXCuhMcndZ=11Yk+t6KOub-R7yYuaB1qzQ@mail.gmail.com>
To: users@dpdk.org, dev@dpdk.org
Cc: Venumadhav Josyula <vjosyula@parallelwireless.com>
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] time taken for allocation of mempool.
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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