From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <xiaojuntime@gmail.com>
Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com
 [209.85.217.175]) by dpdk.org (Postfix) with ESMTP id 7FE25AFDD
 for <dev@dpdk.org>; Tue,  6 May 2014 04:56:07 +0200 (CEST)
Received: by mail-lb0-f175.google.com with SMTP id l4so2200282lbv.34
 for <dev@dpdk.org>; Mon, 05 May 2014 19:56:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :content-type; bh=xukGyjen1SkPt5mOP1W0Y56WyGOKs+jZ2TmADD288F8=;
 b=LfCjxFmMBP2JJNtdNxdBsZ67SYIQOr8oPkHuUuqgRMJFKHZOdDL67uS5s79gkeU40Q
 2IXutmWcfXDfWTeLuLx5jykSZSkwy2O9BWzD22uLpfaMW+OMs6AOpGvy3WxVMy3VoBi1
 SBWurWnIgqGgT7c122aCKj60x8JcdGR+cpBf4EgnukiOJnvelx5R5oTdc/DOEtNq2bnH
 gkkhvHdD+zIJ4KozXrLc7weDxZjqDs0vb4k/wwafEw8hbQXqVWYnrhUkf9SkPDCwHLGz
 OUqq3MemOcd21OGtd9Go4YB5jzh6EGwrHNgSxgNwaAxH8RLu9JOr+edfrvHHMA7smGNy
 9M5A==
X-Received: by 10.152.5.202 with SMTP id u10mr4345577lau.42.1399344972547;
 Mon, 05 May 2014 19:56:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.130.163 with HTTP; Mon, 5 May 2014 19:55:52 -0700 (PDT)
In-Reply-To: <CACyt=TEr4ZR-kqsVCK8s-BzZ5=C4YnPqtzBsVEPsfySWvF6paw@mail.gmail.com>
References: <CACyt=TEr4ZR-kqsVCK8s-BzZ5=C4YnPqtzBsVEPsfySWvF6paw@mail.gmail.com>
From: Jun Xiao <xiaojuntime@gmail.com>
Date: Tue, 6 May 2014 10:55:52 +0800
Message-ID: <CACyt=TFBj941_2A8vyt40L0KJiz+BPityr3jC+P_4tqknT2L5w@mail.gmail.com>
To: dev <dev@dpdk.org>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Tue, 06 May 2014 10:12:05 +0200
Subject: Re: [dpdk-dev] dpdk-1.6.0r1 problem with Intel 82599ES
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 02:56:07 -0000

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