From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Venumadhav Josyula <vjosyula@gmail.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
users@dpdk.org, dev@dpdk.org,
Venumadhav Josyula <vjosyula@parallelwireless.com>
Subject: Re: [dpdk-users] [dpdk-dev] time taken for allocation of mempool.
Date: Fri, 6 Dec 2019 10:47:51 +0000 [thread overview]
Message-ID: <ea5a5237-bd26-77a4-366a-effaf4acc565@intel.com> (raw)
In-Reply-To: <CA+i0PGXRjnFPQkt2+R83Lf_2+xp9rhzgsa+yxqj07-p9=oihwA@mail.gmail.com>
On 18-Nov-19 4:43 PM, Venumadhav Josyula wrote:
> Hi Anatoly,
>
> After using iova-mode=va, i see my ports are not getting detected ? I
> thought it's working but I see following problem
>
> what could be the problem?
> i) I see allocation is faster
> ii) But my ports are not getting detected
> I take my word back that it entirely working..
>
> Thanks,
> Regards,
> Venu
>
"Ports are not getting detected" is a pretty vague description of the
problem. Could you please post the EAL initialization log (preferably
with --log-level=eal,8 added, so that there's more output)?
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-12-06 10:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 5:07 [dpdk-users] " Venumadhav Josyula
2019-11-13 5:12 ` Venumadhav Josyula
2019-11-13 8:32 ` [dpdk-users] [dpdk-dev] " Olivier Matz
2019-11-13 9:11 ` Venumadhav Josyula
2019-11-13 9:30 ` Olivier Matz
2019-11-13 9:19 ` Bruce Richardson
2019-11-13 17:26 ` Burakov, Anatoly
2019-11-13 21:01 ` Venumadhav Josyula
2019-11-14 9:44 ` Burakov, Anatoly
2019-11-14 9:50 ` Venumadhav Josyula
2019-11-14 9:57 ` Burakov, Anatoly
2019-11-18 16:43 ` Venumadhav Josyula
2019-12-06 10:47 ` Burakov, Anatoly [this message]
2019-12-06 10:49 ` Venumadhav Josyula
2019-11-14 8:12 ` Venumadhav Josyula
2019-11-14 9:49 ` Burakov, Anatoly
2019-11-14 9:53 ` Venumadhav Josyula
2019-11-18 16:45 ` [dpdk-users] " Venumadhav Josyula
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=ea5a5237-bd26-77a4-366a-effaf4acc565@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=users@dpdk.org \
--cc=vjosyula@gmail.com \
--cc=vjosyula@parallelwireless.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).