From: Anshu Boonapalli <anshu.boonapalli@gmail.com>
To: "Singh, Satish 1. (Nokia - IN/Bangalore)" <satish.1.singh@nokia.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK 17.11.2 - PMD: net_mlx5: mempool 0x7fc988c33e40: not virtually contiguous
Date: Wed, 8 Aug 2018 09:37:10 -0700 [thread overview]
Message-ID: <CA+=pU-J_bp_AWhPo=HjMHVLzZzA0tn4VX0vd1Tk_w-3GCDcejA@mail.gmail.com> (raw)
In-Reply-To: <DB5PR07MB152767E1533096374473CEA889260@DB5PR07MB1527.eurprd07.prod.outlook.com>
The system i am working on has ~1TB of RAM.
On Tue, Aug 7, 2018 at 9:28 PM Singh, Satish 1. (Nokia - IN/Bangalore) <
satish.1.singh@nokia.com> wrote:
> Hi,
>
> According to your configuration, yiu are allocation 80K*2MB = 160GB of
> memory, do you have that much Ram in your system?
>
> Regards,
> SATISH SINGH
>
> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Anshu Boonapalli
> Sent: Tuesday, August 7, 2018 10:33 PM
> To: users@dpdk.org
> Subject: [dpdk-users] DPDK 17.11.2 - PMD: net_mlx5: mempool
> 0x7fc988c33e40: not virtually contiguous
>
> hi,
>
> I am facing this failure intermittently during the rte_eal_init call, when
> using relatively large number of hugepages (~80k+ of 2MB hugepages).
>
> The mempool for this scenario is allocated using rte_mempool_create() and
> all associated documentation/source seems to indicate the pool returned
> should be virtually contiguous.
>
> Have any of you experienced this failure and figured out a resolution?
>
> Thanks,
> -Anshu
>
next prev parent reply other threads:[~2018-08-08 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 17:03 Anshu Boonapalli
2018-08-08 3:28 ` Singh, Satish 1. (Nokia - IN/Bangalore)
2018-08-08 16:37 ` Anshu Boonapalli [this message]
2018-08-08 17:26 ` Stephen Hemminger
2018-08-09 3:30 ` Singh, Satish 1. (Nokia - IN/Bangalore)
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+=pU-J_bp_AWhPo=HjMHVLzZzA0tn4VX0vd1Tk_w-3GCDcejA@mail.gmail.com' \
--to=anshu.boonapalli@gmail.com \
--cc=satish.1.singh@nokia.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).