DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Mahesh Ishwar Mathad <mi.mahesh@globaledgesoft.com>,
	users <users-bounces@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] doubts on dpdk qos-sched sample application
Date: Tue, 25 Jul 2017 17:28:31 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BA84E86@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1979240322.9360088.1500964351065.JavaMail.zimbra@globaledgesoft.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mahesh Ishwar
> Mathad
> Sent: Tuesday, July 25, 2017 7:33 AM
> To: users <users-bounces@dpdk.org>; dev@dpdk.org
> Subject: [dpdk-dev] doubts on dpdk qos-sched sample application
> 
> Hi Team,
> 
> $ ./build/qos_sched -c 0xe -n 4 -- --pfc "0,1,3,2" --cfg "profile.cfg"EAL:
> Detected 4 lcore(s)
> PMD: bnxt_rte_pmd_init() called for (null)
> EAL: PCI device 0000:01:00.0 on NUMA socket -1
> EAL: probe driver: 8086:10c9 rte_igb_pmd
> EAL: PCI device 0000:01:00.1 on NUMA socket -1
> EAL: probe driver: 8086:10c9 rte_igb_pmd
> EAL: Error - exiting with code: 1
> Cause: Cannot init mbuf pool for socket 0
> 
> I getting error something like this: Cannot init mbuf pool for socket 0.
> 
> $ grep -i Huge /proc/meminfo
> AnonHugePages: 350208 kB
> HugePages_Total: 476
> HugePages_Free: 476
> HugePages_Rsvd: 0
> HugePages_Surp: 0
> Hugepagesize: 2048 kB
> 
> Is 476 hugepages are sufficient to execute qos_sched application?
> 

Probably not enough, as traffic management requires large buffer pools.

By default, this app builds a mempool of 2M buffers for each output port:

#define NB_MBUF   (2*1024*1024)


> Could you help me in running this app as per my system configuration.
> 
> Disclaimer:- The information contained in this electronic message and any
> attachments to this message are intended for the exclusive use of the
> addressee(s) and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately and destroy all copies of this message and any attachments. The
> views expressed in this E-mail message (including the enclosure/(s) or
> attachment/(s) if any) are those of the individual sender, except where the
> sender expressly, and with authority, states them to be the views of
> GlobalEdge. Before opening any mail and attachments please check them for
> viruses .GlobalEdge does not accept any liability for virus infected mails.

      reply	other threads:[~2017-07-25 17:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25  6:32 Mahesh Ishwar Mathad
2017-07-25 17:28 ` Dumitrescu, Cristian [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=3EB4FA525960D640B5BDFFD6A3D891267BA84E86@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=mi.mahesh@globaledgesoft.com \
    --cc=users-bounces@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).