DPDK patches and discussions
 help / color / mirror / Atom feed
From: Romulo Rosa <romuloros@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-ovs] Problem with OVS
Date: Mon, 16 Dec 2013 10:42:48 -0200	[thread overview]
Message-ID: <CALdSg2hUUgfJEnt2Lr8ZPAeRFHrNAMLtUFePsuytfJymCVMO_A@mail.gmail.com> (raw)
In-Reply-To: <8208309.oeISgDEZBG@x220>

 Unfortunately performance is something I need for my graduate work. I also do
not have much time to develop a patch at the moment, maybe in a master's
thesis.
Thanks


2013/12/15 Thomas Monjalon <thomas.monjalon@6wind.com>

> 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
>



-- 
Rômulo Rosa Furtado

      reply	other threads:[~2013-12-16 12:42 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
2013-12-15  8:02     ` Thomas Monjalon
2013-12-16 12:42       ` Romulo Rosa [this message]

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=CALdSg2hUUgfJEnt2Lr8ZPAeRFHrNAMLtUFePsuytfJymCVMO_A@mail.gmail.com \
    --to=romuloros@gmail.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).