DPDK usage discussions
 help / color / mirror / Atom feed
From: Murali Krishna <murali.krishna@broadcom.com>
To: Krishna Mohan <mohankrimailing@gmail.com>
Cc: users@dpdk.org, medvedkinv@gmail.com
Subject: Re: [dpdk-users] unable to run l2fwd application due to 'Cause: No Ethernet ports - bye' error
Date: Mon, 21 Mar 2016 12:54:38 +0530	[thread overview]
Message-ID: <9cacdc6d75d2a433d5527d7f6f5f05f8@mail.gmail.com> (raw)
In-Reply-To: <CAMh-HsX_zZDQwjTTahOAUhiZ-TRTVdFaiT5QsEaK2i_p+j2Few@mail.gmail.com>

Thanks Krishna and Vladimir.



I am able to run l2fwd app with our Emulex PMD oce driver using –d Add
driver option



./l2fwd -c f -n 2 -d /DPDK2/librte_pmd_oce.so -- -q 1 -p 0x3



Regards,

Murali



*From:* Krishna Mohan [mailto:mohankrimailing@gmail.com]
*Sent:* Saturday, March 19, 2016 6:35 AM
*To:* murali.krishna@broadcom.com
*Cc:* users@dpdk.org; medvedkinv@gmail.com
*Subject:* Re: [dpdk-users] unable to run l2fwd application due to 'Cause:
No Ethernet ports - bye' error



Hi Murali,



The issue could be related to l2fwd trying to load enic poll mode driver
instead of oce driver.



>From your output I see ...



PMD: ENICPMD trace: rte_enic_pmd_init



ENIC is a Cisco Network Driver and you should be have something like

rte_oce_pmd_init



Can you check id table (vendor id/device id) in your OneConnect poll mode
driver ?



Thanks

Krishna

  reply	other threads:[~2016-03-21  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-19  1:04 Krishna Mohan
2016-03-21  7:24 ` Murali Krishna [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-18 15:11 Murali Krishna
2016-03-18 15:21 ` Vladimir Medvedkin
2016-03-18 15:26   ` Murali Krishna
2016-03-18 15:46   ` Murali Krishna
2016-03-18 17:18     ` Vladimir Medvedkin
2016-03-18 18:08       ` Murali Krishna

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=9cacdc6d75d2a433d5527d7f6f5f05f8@mail.gmail.com \
    --to=murali.krishna@broadcom.com \
    --cc=medvedkinv@gmail.com \
    --cc=mohankrimailing@gmail.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).