DPDK patches and discussions
 help / color / mirror / Atom feed
From: <jayachandran.subramanian@wipro.com>
To: <hvreddy1110@gmail.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] Unable to start DPDK+Netshard
Date: Mon, 22 Aug 2016 05:50:54 +0000	[thread overview]
Message-ID: <HK2PR03MB1634DC7C7AA46FE2B9A6BF2295E80@HK2PR03MB1634.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <CAERxyUWZXs35R-pNjhAh0g9=norqOpjdkt3aBk=MRKY_oWJe3g@mail.gmail.com>

HI HVR,

Thanks a lot after increasing Huge pages to 1536 Mb , issue got resolved.

Also could you please let me know , we needs to configure the same Huge page/isolscpus  in grub configuration .

Could you please help me on that !

Thanks
Jay

From: harshavardhan Reddy [mailto:hvreddy1110@gmail.com]
Sent: Monday, August 22, 2016 11:14 AM
To: Jayachandran Subramanian (MFG & Tech) <jayachandran.subramanian@wipro.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Unable to start DPDK+Netshard


** This mail has been sent from an external source **
try o increase the hugepages to
4GB and run once again.
Also it depends on how much memory u are reserving in mempools and for rings..

Regards,
HVR

On Sun, Aug 21, 2016 at 4:08 PM, <jayachandran.subramanian@wipro.com<mailto:jayachandran.subramanian@wipro.com>> wrote:
Hi ,

When I start netshard with dpdk-pmd stack , getting the below error

RING: Cannot reserve memory
Failed to create mempool for Tx
RING: Cannot reserve memory
Failed to create mempool for Tx
Creating Rx mbuf pool 'dpdk_net_pktmbuf_pool8_rx' [1024 mbufs] ...
RING: Cannot reserve memory
Failed to create mempool for Tx

Configured huge pages and binded NIC to DPDK drivers

Please let me know how to resolve this issue, PFA nic binding / huge pages details.

Thanks
Jay
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. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>

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. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

  reply	other threads:[~2016-08-22  5:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21 10:38 jayachandran.subramanian
2016-08-22  5:44 ` harshavardhan Reddy
2016-08-22  5:50   ` jayachandran.subramanian [this message]
2016-08-22  7:44     ` harshavardhan Reddy

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=HK2PR03MB1634DC7C7AA46FE2B9A6BF2295E80@HK2PR03MB1634.apcprd03.prod.outlook.com \
    --to=jayachandran.subramanian@wipro.com \
    --cc=dev@dpdk.org \
    --cc=hvreddy1110@gmail.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).