From: Jun Xiao <xiaojuntime@gmail.com>
To: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] dpdk-1.6.0r1 problem with Intel 82599ES
Date: Tue, 6 May 2014 10:55:52 +0800 [thread overview]
Message-ID: <CACyt=TFBj941_2A8vyt40L0KJiz+BPityr3jC+P_4tqknT2L5w@mail.gmail.com> (raw)
In-Reply-To: <CACyt=TEr4ZR-kqsVCK8s-BzZ5=C4YnPqtzBsVEPsfySWvF6paw@mail.gmail.com>
Sorry for the spam, I just noticed it's AMD cpu! Is it possible to
make it fail quickly if dpdk cannot really work with AMD cpu?
On Tue, May 6, 2014 at 10:26 AM, Jun Xiao <xiaojuntime@gmail.com> wrote:
> Hi,
>
> I am running dpdk-1.6.0r1 with Intel 82599ES with some problems:
> - The test driver is l2fwd, and it is started successfully without any
> problem (all DEBUG build flags are enabled, but I didn't find anything
> abnormal)
> - l2fwd cannot see any packet generated by pktgen on another machine.
> - The connectivity between l2fwd machine and pktgen machine is fine
> (verified by ping before igb_uio is loaded)
> - # tools/pci_unbind.py --status
>
> Network devices using IGB_UIO driver
> ====================================
> 0000:22:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection'
> drv=igb_uio unused=
> 0000:22:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection'
> drv=igb_uio unused=
>
> Network devices using kernel driver
> ===================================
> 0000:01:00.0 'NetXtreme II BCM5709 Gigabit Ethernet' if=em1 drv=bnx2
> unused=<none> *Active*
> 0000:01:00.1 'NetXtreme II BCM5709 Gigabit Ethernet' if=em2 drv=bnx2
> unused=<none>
>
> I am pretty confident on the procedures since I tried it out on
> another setup with Intel I350 Gigabit NIC.
>
> Thanks,
> Jun
next prev parent reply other threads:[~2014-05-06 2:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 2:26 Jun Xiao
2014-05-06 2:55 ` Jun Xiao [this message]
2014-05-06 3:06 ` Jun Xiao
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='CACyt=TFBj941_2A8vyt40L0KJiz+BPityr3jC+P_4tqknT2L5w@mail.gmail.com' \
--to=xiaojuntime@gmail.com \
--cc=dev@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).