From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Romulo Rosa <romuloros-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [dpdk-ovs] Problem with OVS
Date: Sun, 15 Dec 2013 09:02:25 +0100 [thread overview]
Message-ID: <8208309.oeISgDEZBG@x220> (raw)
In-Reply-To: <CALdSg2jCprYHbVvQyLwrNRTf1S2So_QvpHs+C6BG_xPMrYQF0g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
14/12/2013 13:54, Romulo Rosa :
> 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?
[...]
> 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=
No, Broadcom and Emulex NICs are not supported. But patches are welcomed.
By the way, you can use any NIC with pmd_pcap if you don't care about
performance.
--
Thomas
next prev parent reply other threads:[~2013-12-15 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 22:25 [dpdk-ovs] Problem with OVS Romulo Rosa
[not found] ` <CALdSg2hGieB85DEvTtrkugUhxC+qEJH8RFDVpwbHSkkRO=RiLw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-13 16:10 ` Paul Barrette
[not found] ` <52AB3176.7040800-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2013-12-14 15:54 ` Romulo Rosa
[not found] ` <CALdSg2jCprYHbVvQyLwrNRTf1S2So_QvpHs+C6BG_xPMrYQF0g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-15 6:39 ` Jyotiswarup Raiturkar
2013-12-15 8:02 ` Thomas Monjalon [this message]
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=8208309.oeISgDEZBG@x220 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=romuloros-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).