From: Pragash Vijayaragavan <pxv3620@rit.edu>
To: "Hristo.Trifonov" <Hristo.Trifonov@ul.ie>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] port 0 not present on board error
Date: Tue, 12 Dec 2017 09:13:15 -0500 [thread overview]
Message-ID: <CANp7S21_899BZPavQaXMM+p1XL66MNDOCcA4aiJu2sj8C1OjGw@mail.gmail.com> (raw)
In-Reply-To: <E6A390FF2129134EB58BFFFFDFFB5A844DFF29B1@ExMbx1.ul.campus>
Hi,
- Is this an issue only with the l3fwd app?
No every app which requires ports is
having an issue
- Did you try to run testpmd, skeleton or l2fwd?
Yea same issue
- Is the card working properly with the kernel driver?
Yes it works fine
- Did you try previous version of dpdk?
Which version should i try? I tried latest
17.11 and stable 17.05 so far
Thanks,
Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662
On Tue, Dec 12, 2017 at 9:02 AM, Hristo.Trifonov <Hristo.Trifonov@ul.ie>
wrote:
> Unfortunately I don't have XL710 NIC available to test.
>
> Off the top of my head:
>
> - Is this an issue only with the l3fwd app?
>
> - Did you try to run testpmd, skeleton or l2fwd?
>
> - Is the card working properly with the kernel driver?
>
> - Did you try previous version of dpdk?
>
> Hristo T.
>
next prev parent reply other threads:[~2017-12-12 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 14:02 Hristo.Trifonov
2017-12-12 14:13 ` Pragash Vijayaragavan [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-12 12:47 Hristo.Trifonov
2017-12-12 13:33 ` Pragash Vijayaragavan
2017-12-12 10:54 Hristo.Trifonov
2017-12-12 12:21 ` Pragash Vijayaragavan
2017-12-11 11:21 Hristo.Trifonov
2017-12-11 21:24 ` Pragash Vijayaragavan
2017-12-12 6:17 ` Pragash Vijayaragavan
2017-12-12 7:17 ` Stephen Hemminger
2017-12-08 12:11 Hristo.Trifonov
2017-12-08 20:22 ` Pragash Vijayaragavan
2017-12-08 4:01 Pragash Vijayaragavan
2017-12-08 4:18 ` Dave Boutcher
2017-12-08 4:21 ` Pragash Vijayaragavan
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=CANp7S21_899BZPavQaXMM+p1XL66MNDOCcA4aiJu2sj8C1OjGw@mail.gmail.com \
--to=pxv3620@rit.edu \
--cc=Hristo.Trifonov@ul.ie \
--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).