DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>
To: Romulo Rosa <romuloros@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-ovs] Problem with OVS
Date: Sun, 15 Dec 2013 12:09:10 +0530	[thread overview]
Message-ID: <CAJn5u1mXuMpgxtVY3vakirrC5wYAmf5iHcdad1ukfmKf25deHA@mail.gmail.com> (raw)
In-Reply-To: <CALdSg2jCprYHbVvQyLwrNRTf1S2So_QvpHs+C6BG_xPMrYQF0g@mail.gmail.com>

Hi Romulo

You can check lib/librte_eal/common/include/rte_pci_dev_ids.h for supported
NICs.
Also from your pci_unbind status , does not look like any NIC is bound to
igb_uio..


On Sat, Dec 14, 2013 at 9:24 PM, Romulo Rosa <romuloros@gmail.com> wrote:

> Thanks Paul,
>
> But i think my NICS are not supportted by Intel DPDK. In this link they are
> not listed http://dpdk.org/doc/nics. Anyone know if there are other
> supported cards?
>
> ./tools/pci_unbind.py --status
>
> Network devices using IGB_UIO driver
> ====================================
> <none>
>
> Network devices using kernel driver
> ===================================
> 0000:03:00.0 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eth0
> *drv=tg3* unused=
> *Active*
> 0000:03:00.1 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eth1 *drv=tg3*
>  unused=
> 0000:03:00.2 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eth2 *drv=tg3*
>  unused=
> 0000:03:00.3 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eth3 *drv=tg3*
>  unused=
> 0000:07:00.0 'OneConnect 10Gb NIC (be3)' if=eth4* drv=be2net* unused=
> 0000:07:00.1 'OneConnect 10Gb NIC (be3)' if=eth5 *drv=be2net* unused=
>
> Other network devices
> =====================
> <none>
>
>
> 2013/12/13 Paul Barrette <paul.barrette@windriver.com>
>
> >
> > On 12/12/2013 05:25 PM, Romulo Rosa wrote:
> >
> >> Hi,
> >>
> >> i'm tryin to run OVS and i get a error. In documentation was mentioned a
> >> possible solution for this problem but it didnt work to me. Someone have
> >> any idea how to solve this problem?
> >> The uio module is loaded.
> >>
> >> *Command: *./datapath/dpdk/build/ovs_dpdk -c 0xf -n 4 -- -p 0xc
> >>
> > I think you have the wrong port mask.  Try using -p 0x3.
> >
> > Pb
> >
> >>   -n 2 -k 2
> >> --stats=1 --vswitchd=0 --client_switching_core=1
> >> --config="(0,0,2),(1,0,3)"
> >>
> >> *Error: *
> >>
> >> EAL: Core 2 is ready (tid=43fd700)
> >> EAL: Core 3 is ready (tid=3bfc700)
> >> EAL: Core 1 is ready (tid=4bfe700)
> >> WARNING: requested port 2 not present - ignoring
> >> WARNING: requested port 3 not present - ignoring
> >> config = 16,0,2
> >> config = 17,0,3
> >> nb_cfg_params = 2
> >> Creating mbuf pool 'MProc_pktmbuf_pool' [14336 mbufs] ...
> >> HASH: Enabling CRC32 instruction for hashing
> >> APP: memzone address is 2ef33980
> >> EAL: Error - exiting with code: 1
> >>    Cause: Cannot allocate memory for port tx_q details
> >>
> >> Thanks!
> >>
> >
> >
>
>
> --
> Rômulo Rosa Furtado
>

  reply	other threads:[~2013-12-15  6:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 22:25 Romulo Rosa
2013-12-13 16:10 ` Paul Barrette
2013-12-14 15:54   ` Romulo Rosa
2013-12-15  6:39     ` Jyotiswarup Raiturkar [this message]
2013-12-15  8:02     ` Thomas Monjalon
2013-12-16 12:42       ` Romulo Rosa

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=CAJn5u1mXuMpgxtVY3vakirrC5wYAmf5iHcdad1ukfmKf25deHA@mail.gmail.com \
    --to=jyotisr5@googlemail.com \
    --cc=dev@dpdk.org \
    --cc=romuloros@gmail.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).