From: Stephen Hemminger <stephen@networkplumber.org>
To: <jayachandran.subramanian@wipro.com>
Cc: <users@dpdk.org>, <qian.q.xu@intel.com>
Subject: Re: [dpdk-users] Issue while running more than 64 core
Date: Thu, 22 Sep 2016 08:31:00 -0700 [thread overview]
Message-ID: <20160922083100.6dc778ce@xeon-e3> (raw)
In-Reply-To: <HK2PR03MB1634DD95286018D62F46BC8995C90@HK2PR03MB1634.apcprd03.prod.outlook.com>
On Thu, 22 Sep 2016 12:07:17 +0000
<jayachandran.subramanian@wipro.com> wrote:
> Hi,
> I am running DPDK on 96 core machine (4 E7 CPUs with 24 cores each) ,we unable to utilize more than 64 core on 96 CPU server.
>
> CLI : AuthEngine --dpdk-pmd --network-stack native -c64 --host-ipv4-addr 10.165.*.* --gw-ipv4-addr 10.165.*.* --netmask-ipv4-addr 255.255.255.*
>
> Error : Failed to bootstrap AuthEngine: _Base_bitset::_M_do_to_ulong
This error is not from the DPDK code base, it is some proprietary code you are using.
Fix your own code, or if you bought it from someone complain to them.
Probably they code is trying to fit more than 64 CPU's into an unsigned long bitmask.
prev parent reply other threads:[~2016-09-22 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 12:07 jayachandran.subramanian
2016-09-22 15:31 ` Stephen Hemminger [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=20160922083100.6dc778ce@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jayachandran.subramanian@wipro.com \
--cc=qian.q.xu@intel.com \
--cc=users@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).