[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-26 Thread Arthas
Hi, Zhigang.
and testpmd also can't send any packet success. 

Regards,
  Arthas
-- Original --
From:  "Arthas";<kangzy1...@qq.com>;
Date:  Sat, Sep 26, 2015 10:48 PM
To:  "zlu"; "dev"; 

Subject:  Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, Zhigang, 
Thanks, I use mPIPE api can receive & send packets. but DPDK v2.1.0 with gx 
can't send & receive any packet. I guess hv layer dosn't  see any memory pages 
and register change, so any edesc  can't be reclaimed. Now I waiting for our 
tech supporter release MDE 4.3.3.  

Regards,
  Arthas



-- Original --
From:  "zlu";<z...@ezchip.com>;
Date:  Fri, Sep 25, 2015 10:44 PM
To:  "Arthas"; "'dev'"; 

Subject:  RE: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, Arthas

I don't see the failed messages in your log, so that can't give you useful
guidance.
Are you running testpmd or your own apps? Can you generate some
packets on another GX, and check if the dpdk can receive packets with
testpmd.

Overall, I recommend you to run our latest MDE, as that's we usually runs
with DPDK, so that we can reproduce you case.

Thanks
-Zhigang

>-Original Message-
>From: Arthas [mailto:kangzy1982 at qq.com]
>Sent: Friday, September 25, 2015 12:38 PM
>To: zlu; dev
>Subject: Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597
>
>Hi, Zhigang,
>  I fixed register memseg error, but gxio_mpipe_equeue_put_at send packet
>still failed.
>Command: run cat /proc/meminfo
>MemTotal:8230016 kB
>MemFree: 3866688 kB
>Buffers:   0 kB
>Cached:16576 kB
>SwapCached:0 kB
>Active:11392 kB
>Inactive:   9088 kB
>Active(anon):  11392 kB
>Inactive(anon): 9088 kB
>Active(file):  0 kB
>Inactive(file):0 kB
>Unevictable:   0 kB
>Mlocked:   0 kB
>SwapTotal: 0 kB
>SwapFree:  0 kB
>Dirty: 0 kB
>Writeback: 0 kB
>AnonPages: 0 kB
>Mapped: 3072 kB
>Shmem: 16320 kB
>Slab:  17024 kB
>SReclaimable:768 kB
>SUnreclaim:16256 kB
>KernelStack:   11456 kB
>PageTables:0 kB
>NFS_Unstable:  0 kB
>Bounce:0 kB
>WritebackTmp:  0 kB
>CommitLimit: 2017856 kB
>Committed_AS:  22976 kB
>VmallocTotal:4194304 kB
>VmallocUsed:  224704 kB
>VmallocChunk:3964864 kB
>Sequestered:   46144 kB
>HugePages_Total:   4
>HugePages_Free:0
>HugePages_Rsvd:0
>HugePages_Surp:0
>Hugepagesize:1048576 kB
>
>_init_dpdk_eal_params:  -c 0x -m 4096 -r 1 -n 1 --log-level 8
--vdev xgbe1
>--vdev xgbe2 --log-level 8 --no-hpet
>main: rte_eal_init.
>EAL: Detected lcore 0 as core 0 on socket 0
>EAL: Detected lcore 1 as core 1 on socket 0
>EAL: Detected lcore 2 as core 2 on socket 0
>EAL: Detected lcore 3 as core 3 on socket 0
>EAL: Detected lcore 4 as core 4 on socket 0
>EAL: Detected lcore 5 as core 5 on socket 0
>EAL: Detected lcore 6 as core 6 on socket 0
>EAL: Detected lcore 7 as core 7 on socket 0
>EAL: Detected lcore 8 as core 8 on socket 0
>EAL: Detected lcore 9 as core 9 on socket 0
>EAL: Detected lcore 10 as core 10 on socket 0
>EAL: Detected lcore 11 as core 11 on socket 0
>EAL: Detected lcore 12 as core 12 on socket 0
>EAL: Detected lcore 13 as core 13 on socket 0
>EAL: Detected lcore 14 as core 14 on socket 0
>EAL: Detected lcore 15 as core 15 on socket 0
>EAL: Detected lcore 16 as core 16 on socket 0
>EAL: Detected lcore 17 as core 17 on socket 0
>EAL: Detected lcore 18 as core 18 on socket 0
>EAL: Detected lcore 19 as core 19 on socket 0
>EAL: Detected lcore 20 as core 20 on socket 0
>EAL: Detected lcore 21 as core 21 on socket 0
>EAL: Detected lcore 22 as core 22 on socket 0
>EAL: Detected lcore 23 as core 23 on socket 0
>EAL: Detected lcore 24 as core 24 on socket 0
>EAL: Detected lcore 25 as core 25 on socket 0
>EAL: Detected lcore 26 as core 26 on socket 0
>EAL: Detected lcore 27 as core 27 on socket 0
>EAL: Detected lcore 28 as core 28 on socket 0
>EAL: Detected lcore 29 as core 29 on socket 0
>EAL: Detected lcore 30 as core 30 on socket 0
>EAL: Detected lcore 31 as core 31 on socket 0
>EAL: Detected lcore 32 as core 32 on socket 0
>EAL: Detected lcore 33 as core 33 on socket 0
>EAL: Detected lcore 34 as core 34 on socket 0
>EAL: Detected lcore 35 as core 35 on socket 0
>EAL: Support maximum 36 logical core(s) by configuration.
>EAL: Detected 36 lcore(s)
>EAL: Setting up physically contiguous memory...
>EAL: Ask a virtual ar

[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-26 Thread Arthas
Hi, Zhigang, 
Thanks, I use mPIPE api can receive & send packets. but DPDK v2.1.0 with gx 
can't send & receive any packet. I guess hv layer dosn't  see any memory pages 
and register change, so any edesc  can't be reclaimed. Now I waiting for our 
tech supporter release MDE 4.3.3.  

Regards,
  Arthas



-- Original --
From:  "zlu";<z...@ezchip.com>;
Date:  Fri, Sep 25, 2015 10:44 PM
To:  "Arthas"; "'dev'"; 

Subject:  RE: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, Arthas

I don't see the failed messages in your log, so that can't give you useful
guidance.
Are you running testpmd or your own apps? Can you generate some
packets on another GX, and check if the dpdk can receive packets with
testpmd.

Overall, I recommend you to run our latest MDE, as that's we usually runs
with DPDK, so that we can reproduce you case.

Thanks
-Zhigang

>-Original Message-
>From: Arthas [mailto:kangzy1982 at qq.com]
>Sent: Friday, September 25, 2015 12:38 PM
>To: zlu; dev
>Subject: Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597
>
>Hi, Zhigang,
>  I fixed register memseg error, but gxio_mpipe_equeue_put_at send packet
>still failed.
>Command: run cat /proc/meminfo
>MemTotal:8230016 kB
>MemFree: 3866688 kB
>Buffers:   0 kB
>Cached:16576 kB
>SwapCached:0 kB
>Active:11392 kB
>Inactive:   9088 kB
>Active(anon):  11392 kB
>Inactive(anon): 9088 kB
>Active(file):  0 kB
>Inactive(file):0 kB
>Unevictable:   0 kB
>Mlocked:   0 kB
>SwapTotal: 0 kB
>SwapFree:  0 kB
>Dirty: 0 kB
>Writeback: 0 kB
>AnonPages: 0 kB
>Mapped: 3072 kB
>Shmem: 16320 kB
>Slab:  17024 kB
>SReclaimable:768 kB
>SUnreclaim:16256 kB
>KernelStack:   11456 kB
>PageTables:0 kB
>NFS_Unstable:  0 kB
>Bounce:0 kB
>WritebackTmp:  0 kB
>CommitLimit: 2017856 kB
>Committed_AS:  22976 kB
>VmallocTotal:4194304 kB
>VmallocUsed:  224704 kB
>VmallocChunk:3964864 kB
>Sequestered:   46144 kB
>HugePages_Total:   4
>HugePages_Free:0
>HugePages_Rsvd:0
>HugePages_Surp:0
>Hugepagesize:1048576 kB
>
>_init_dpdk_eal_params:  -c 0x -m 4096 -r 1 -n 1 --log-level 8
--vdev xgbe1
>--vdev xgbe2 --log-level 8 --no-hpet
>main: rte_eal_init.
>EAL: Detected lcore 0 as core 0 on socket 0
>EAL: Detected lcore 1 as core 1 on socket 0
>EAL: Detected lcore 2 as core 2 on socket 0
>EAL: Detected lcore 3 as core 3 on socket 0
>EAL: Detected lcore 4 as core 4 on socket 0
>EAL: Detected lcore 5 as core 5 on socket 0
>EAL: Detected lcore 6 as core 6 on socket 0
>EAL: Detected lcore 7 as core 7 on socket 0
>EAL: Detected lcore 8 as core 8 on socket 0
>EAL: Detected lcore 9 as core 9 on socket 0
>EAL: Detected lcore 10 as core 10 on socket 0
>EAL: Detected lcore 11 as core 11 on socket 0
>EAL: Detected lcore 12 as core 12 on socket 0
>EAL: Detected lcore 13 as core 13 on socket 0
>EAL: Detected lcore 14 as core 14 on socket 0
>EAL: Detected lcore 15 as core 15 on socket 0
>EAL: Detected lcore 16 as core 16 on socket 0
>EAL: Detected lcore 17 as core 17 on socket 0
>EAL: Detected lcore 18 as core 18 on socket 0
>EAL: Detected lcore 19 as core 19 on socket 0
>EAL: Detected lcore 20 as core 20 on socket 0
>EAL: Detected lcore 21 as core 21 on socket 0
>EAL: Detected lcore 22 as core 22 on socket 0
>EAL: Detected lcore 23 as core 23 on socket 0
>EAL: Detected lcore 24 as core 24 on socket 0
>EAL: Detected lcore 25 as core 25 on socket 0
>EAL: Detected lcore 26 as core 26 on socket 0
>EAL: Detected lcore 27 as core 27 on socket 0
>EAL: Detected lcore 28 as core 28 on socket 0
>EAL: Detected lcore 29 as core 29 on socket 0
>EAL: Detected lcore 30 as core 30 on socket 0
>EAL: Detected lcore 31 as core 31 on socket 0
>EAL: Detected lcore 32 as core 32 on socket 0
>EAL: Detected lcore 33 as core 33 on socket 0
>EAL: Detected lcore 34 as core 34 on socket 0
>EAL: Detected lcore 35 as core 35 on socket 0
>EAL: Support maximum 36 logical core(s) by configuration.
>EAL: Detected 36 lcore(s)
>EAL: Setting up physically contiguous memory...
>EAL: Ask a virtual area of 0x1 bytes
>EAL: Virtual area found at 0x1fe4000 (size = 0x1)
>EAL: Requesting 4 pages of size 1024MB from socket 0
>EAL: TSC frequency is ~119 KHz
>EAL: WARNING: cpu flags constant_tsc=no nonstop_tsc=no -> using unreliable
>clock cycles !
>EAL: Master lcore 0 is ready (tid=f7f34690;cpuset=

[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-25 Thread Arthas
ed mbuf 0x1ff3a512f00, buffer 0x1ff3a513082 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a512680, buffer 0x1ff3a512802 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a511e00, buffer 0x1ff3a511f82 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a511580, buffer 0x1ff3a511702 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a510d00, buffer 0x1ff3a510e82 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a510480, buffer 0x1ff3a510602 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a50fc00, buffer 0x1ff3a50fd82 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a50f380, buffer 0x1ff3a50f502 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a50eb00, buffer 0x1ff3a50ec82 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a50e280, buffer 0x1ff3a50e402 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a50da00, buffer 0x1ff3a50db82 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a50d180, buffer 0x1ff3a50d302 into stack 2
PMD: xgbe1: Pushed mbuf 0x1ff3a50c900, buffer 0x1ff3a50ca82 into stack 2
PMD: xgbe1: Filled 128/128 buffers
PMD: rte_eth_dev_config_restore: port 0: MAC address array not supported
PMD: rte_eth_allmulticast_disable: Function not supported
_eth_dev_init: start port 0 success.
_eth_dev_init: enable port 0 promiscuous.
main:  Link Up - speed 1 Mbps - full-duplex
_tx_pkts_rand_init: Alloc 32 mbuf for port=0
_tx_pkts_rand_init: Prebuild 32 mbuf for port=0 
_tx_pkts_rand_init: Prebuild 32 mbuf for port=0 done.
main: launch lcore 1 _mbuf_random_task task port=0 txq=0
_mbuf_random_task: Start mbuf rand task port=0 pool=0x0x1ff36e3f5c0
_mbuf_random_task: Start mbuf rand task daddr=192.168.1.245 dport=80
_mbuf_random_task: Core 1 Exit..
_tx_rand_task: Start TX rand task port=0 txq=0 pkts_burst=32
_wait_for_dev_link_up: TX rand task Core 2 port 0 Link is Up
PMD: Trying to transmit 32 packets on xgbe1:0.
main: launch lcore 2 tx task port=0 txq=0
PMD: xgbe1:0: Sending packet 0x1ff3a50c200, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a50b980, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a50b100, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a50a880, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a50a000, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a509780, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a508f00, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a508680, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a507e00, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a507580, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a506d00, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a506480, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a505c00, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a505380, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a504b00, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a504280, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a503a00, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a503180, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a502900, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a502080, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a501800, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a500f80, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a500700, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a4ffe80, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a4ff600, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a4fed80, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a4fe500, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a4fdc80, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a4fd400, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a4fcb80, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a4fc300, len 62
PMD: xgbe1:0: Sending packet 0x1ff3a4fba80, len 62
PMD: Ask the mPIPE hardware to egress outstanding packets immediately.
PMD: Wait for mPIPE equeue slot 32  complete.

Regards.
  Arthas
------ Original --From:  "Arthas";;
Date:  Thu, Sep 24, 2015 01:38 PM
To:  "zlu"; "dev"; 

Subject:  Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, Zhigang,
  I checked error code and got a error information "(No more IOTLB entries)." & 
 xmit function gxio_mpipe_equeue_try_reserve_fast got "Insufficient DMA 
credits"!

Command: run ./testpmd -c 0x -m 6144 -n 1 -r 1 --vdev xgbe1 -- --rx=1 
--tx=2 --forward-mode=txonly -a --port-topology=chained
gxio_mpipe_init instance 0
gxio_mpipe_init instance 1
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 6 on socket 0
EAL: Detected lcore 7 as core 7 on socket 0
EAL: Detected lcore 8 as core 8 on socket 0
EAL: Detected lcore 9 as core 9 on socket 0
EAL: Detected lcore 10 as core 10 on socket 0
EAL: Detected lcore 11 as core 11 on socket 0
EAL: Detected lcore 12 as core 12 on socket 0
EAL: Detected lcore 13 as core 13 on socket 0
EAL: Detected lcore 14 as core 14 on socket 0
EAL: Detected lcore 15 as core 15 on socket 0
EAL: Detected lcore 16 as core 16 on socket 0
EAL: Detected lcore 17 as core 17 on socket 

[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-24 Thread Arthas
1:53:72:82:5A
Checking link statuses...
Port 0 Link Up - speed 1 Mbps - full-duplex
Done
No commandline core given, start packet forwarding
  txonly packet forwarding - CRC stripping disabled - packets/burst=32
  packet len=64 - nb packet segments=1
  nb forwarding cores=1 - nb forwarding ports=1
  RX queues=1 - RX desc=128 - RX free threshold=0
  RX threshold registers: pthresh=0 hthresh=0 wthresh=0
  TX queues=2 - TX desc=512 - TX free threshold=0
  TX threshold registers: pthresh=0 hthresh=0 wthresh=0
  TX RS bit threshold=0 - TXQ flags=0x0
Press enter to exit
Command: run cat /proc/meminfo
MemTotal:8230464 kB
MemFree: 1765120 kB
Buffers:   0 kB
Cached:42432 kB
SwapCached:0 kB
Active:27776 kB
Inactive:   8448 kB
Active(anon):  27776 kB
Inactive(anon): 8448 kB
Active(file):  0 kB
Inactive(file):0 kB
Unevictable:   0 kB
Mlocked:   0 kB
SwapTotal: 0 kB
SwapFree:  0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 0 kB
Mapped: 3008 kB
Shmem: 17856 kB
Slab:  17984 kB
SReclaimable:   1280 kB
SUnreclaim:16704 kB
KernelStack:   11456 kB
PageTables:0 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit:  969472 kB
Committed_AS:  41280 kB
VmallocTotal:4194304 kB
VmallocUsed:  224704 kB
VmallocChunk:3964864 kB
Sequestered:   50816 kB
HugePages_Total: 384
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:  16384 kB





-- Original --
From:  "Arthas";<kangzy1...@qq.com>;
Date:  Thu, Sep 24, 2015 11:47 AM
To:  "zlu"; "dev"; 

Subject:  Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, Zhigang
   I used "--hvx hugepagesz=16m --hvx hugepages=256", but testpmd still not 
work and exit. 
Command: run cat /proc/meminfo
MemTotal:8230464 kB
MemFree: 3872576 kB
Buffers:   0 kB
Cached:12480 kB
SwapCached:0 kB
Active:11200 kB
Inactive:   5888 kB
Active(anon):  11200 kB
Inactive(anon): 5888 kB
Active(file):  0 kB
Inactive(file):0 kB
Unevictable:   0 kB
Mlocked:   0 kB
SwapTotal: 0 kB
SwapFree:  0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages:  4736 kB
Mapped: 3072 kB
Shmem: 12480 kB
Slab:  16256 kB
SReclaimable:768 kB
SUnreclaim:15488 kB
KernelStack:   11648 kB
PageTables: 4096 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit: 2018048 kB
Committed_AS:  19328 kB
VmallocTotal:4194304 kB
VmallocUsed:  224704 kB
VmallocChunk:3964864 kB
Sequestered:   37184 kB
HugePages_Total: 256
HugePages_Free:  256
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:  16384 kB

Command: run ./testpmd -c 0x -m 2048 -n 1 -r 1 --vdev xgbe1 -- --rx=1 
--tx=2 --forward-mode=txonly -a --port-topology=chained
gxio_mpipe_init instance 0
gxio_mpipe_init instance 1
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 6 on socket 0
EAL: Detected lcore 7 as core 7 on socket 0
EAL: Detected lcore 8 as core 8 on socket 0
EAL: Detected lcore 9 as core 9 on socket 0
EAL: Detected lcore 10 as core 10 on socket 0
EAL: Detected lcore 11 as core 11 on socket 0
EAL: Detected lcore 12 as core 12 on socket 0
EAL: Detected lcore 13 as core 13 on socket 0
EAL: Detected lcore 14 as core 14 on socket 0
EAL: Detected lcore 15 as core 15 on socket 0
EAL: Detected lcore 16 as core 16 on socket 0
EAL: Detected lcore 17 as core 17 on socket 0
EAL: Detected lcore 18 as core 18 on socket 0
EAL: Detected lcore 19 as core 19 on socket 0
EAL: Detected lcore 20 as core 20 on socket 0
EAL: Detected lcore 21 as core 21 on socket 0
EAL: Detected lcore 22 as core 22 on socket 0
EAL: Detected lcore 23 as core 23 on socket 0
EAL: Detected lcore 24 as core 24 on socket 0
EAL: Detected lcore 25 as core 25 on socket 0
EAL: Detected lcore 26 as core 26 on socket 0
EAL: Detected lcore 27 as core 27 on socket 0
EAL: Detected lcore 28 as core 28 on socket 0
EAL: Detected lcore 29 as core 29 on socket 0
EAL: Detected lcore 30 as core 30 on socket 0
EAL: Detected lcore 31 as core 31 on socket 0
EAL: Detected lcore 32 as core 32 on socket 0
EAL: Detected lcore 33 as core 33 on socket 0
EAL: Detected lcore 34 as core 34 on socket 0
EAL: Detected lcore 35 as core 35 on socket 0
EAL: Supp

[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-24 Thread Arthas
EAL: lcore 27 is ready (tid=8d7ff060;cpuset=[27])
EAL: lcore 28 is ready (tid=8cfff060;cpuset=[28])
EAL: lcore 29 is ready (tid=8c7ff060;cpuset=[29])
EAL: lcore 30 is ready (tid=6bfff060;cpuset=[30])
EAL: lcore 31 is ready (tid=6b7ff060;cpuset=[31])
Set txonly packet forwarding mode
Auto-start selected
Configuring Port 0 (socket 0)
PMD: xgbe1: Registered segment 0x1ffdb00 - 0x1ffe6ff
PMD: xgbe1: Could not register memseg @0x1fee600, -.
PMD: xgbe1: Buffer stack memory 0x1ffe378 - 0x1ffe37d557f.
PMD: xgbe1: eDMA ring memory 0x1ffe37d8000 - 0x1ffe37d9fff.
PMD: xgbe1: iDMA ring 0 memory 0x1ffe377c000 - 0x1ffe377dfff.
Port 0: EE:D1:53:72:82:5A
Checking link statuses...
Port 0 Link Up - speed 1 Mbps - full-duplex
Done
No commandline core given, start packet forwarding
  txonly packet forwarding - CRC stripping disabled - packets/burst=32
  packet len=64 - nb packet segments=1
  nb forwarding cores=1 - nb forwarding ports=1
  RX queues=1 - RX desc=128 - RX free threshold=0
  RX threshold registers: pthresh=0 hthresh=0 wthresh=0
  TX queues=2 - TX desc=512 - TX free threshold=0
  TX threshold registers: pthresh=0 hthresh=0 wthresh=0
  TX RS bit threshold=0 - TXQ flags=0x0
Press enter to exit


Regards,
  Arthas



-- Original --
From:  "zlu";<z...@ezchip.com>;
Date:  Thu, Sep 24, 2015 09:47 AM
To:  "Arthas"; "'dev'"; 

Subject:  Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, Arthas

Seems like something wrong with memseg, could you try with
" --hvx hugepagesz=1G --hvx hugepages=4" to boot Gx card? This
helps reserve hugepages for DPDK, and check there are still such errors.

With regard to MDE-4.3.3, please contact your local tech support.

Thanks
-Zhigang

>-Original Message-
>From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Arthas
>Sent: Wednesday, September 23, 2015 11:56 PM
>To: zlu; dev
>Subject: Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597
>
>Hi, ZhiGang,
>  Can you tell me where can download TileraMDE-4.3.3 package?  My tilegx
>tech supporter only send me TileraMDE-4.2.4 version!
>:)
>
>Thanks,
>  Arthas
>
>
>
>
>-- Original --
>From:  "Arthas";;
>Date:  Wed, Sep 23, 2015 06:41 PM
>To:  "zlu"; "dev";
>
>Subject:  Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597
>
>
>
>Hi, ZhiGang
>  I checked source code and debug it , found dpdk function rte_eth_tx_burst
>with tilegx return 0 and no other error.  Can I contact  you directly?
>Regards,
>  Arthas
>
>
>
>-- Original --
>From:  "Arthas";;
>Date:  Wed, Sep 23, 2015 06:35 PM
>To:  "zlu"; "dev";
>
>Subject:  Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597
>
>
>
>Hi, ZhiGang
>   My tilegx boot parameter is "tile-monitor --dev gxpci${1} --hv-bin-dir
>/tilegx/tile/hv-bin-dir424/ --hvx dataplane=1-64".
>and testpmd start parameter is
>tile-monitor  --dev gxpci0 --resume --upload testpmd  testpmd  --run
>-+-  ./testpmd   -c 0x -m 2048 -n 1 -r 1 --vdev xgbe1 --  --rx=1
--tx=2
>--forward-mode=txonly -a --port-topology=chained -+-
>
> but xgbe1 can't xmit any packet.
>This is my run log:
>
>EAL: Detected lcore 0 as core 0 on socket 0
>EAL: Detected lcore 1 as core 1 on socket 0
>EAL: Detected lcore 2 as core 2 on socket 0
>EAL: Detected lcore 3 as core 3 on socket 0
>EAL: Detected lcore 4 as core 4 on socket 0
>EAL: Detected lcore 5 as core 5 on socket 0
>EAL: Detected lcore 6 as core 6 on socket 0
>EAL: Detected lcore 7 as core 7 on socket 0
>EAL: Detected lcore 8 as core 8 on socket 0
>EAL: Detected lcore 9 as core 9 on socket 0
>EAL: Detected lcore 10 as core 10 on socket 0
>EAL: Detected lcore 11 as core 11 on socket 0
>EAL: Detected lcore 12 as core 12 on socket 0
>EAL: Detected lcore 13 as core 13 on socket 0
>EAL: Detected lcore 14 as core 14 on socket 0
>EAL: Detected lcore 15 as core 15 on socket 0
>EAL: Detected lcore 16 as core 16 on socket 0
>EAL: Detected lcore 17 as core 17 on socket 0
>EAL: Detected lcore 18 as core 18 on socket 0
>EAL: Detected lcore 19 as core 19 on socket 0
>EAL: Detected lcore 20 as core 20 on socket 0
>EAL: Detected lcore 21 as core 21 on socket 0
>EAL: Detected lcore 22 as core 22 on socket 0
>EAL: Detected lcore 23 as core 23 on socket 0
>EAL: Detected lcore 24 as core 24 on socket 0
>EAL: Detected lcore 25 as core 25 on socket 0
>EAL: Detected lcore 26 as core 26 on socket 0
>EAL: Detected lcore 27 as core 27 on socket 0
>EAL: Detected lcore 28 as core 28 on socket 0
>EAL: Detected lcore 29 as core 29 on socket 0
>EAL: Detected lcore 30 as core 30 on socket 0
>EA

[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-24 Thread Arthas
Hi, ZhiGang,
  Can you tell me where can download TileraMDE-4.3.3 package?  My tilegx tech 
supporter only send me TileraMDE-4.2.4 version!
:)

Thanks,
  Arthas 




-- Original --
From:  "Arthas";<kangzy1...@qq.com>;
Date:  Wed, Sep 23, 2015 06:41 PM
To:  "zlu"; "dev"; 

Subject:  Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, ZhiGang
  I checked source code and debug it , found dpdk function rte_eth_tx_burst 
with tilegx return 0 and no other error.  Can I contact 
 you directly?
Regards,
  Arthas



-- Original --
From:  "Arthas";<kangzy1...@qq.com>;
Date:  Wed, Sep 23, 2015 06:35 PM
To:  "zlu"; "dev"; 

Subject:  Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, ZhiGang
   My tilegx boot parameter is "tile-monitor --dev gxpci${1} --hv-bin-dir 
/tilegx/tile/hv-bin-dir424/ --hvx dataplane=1-64". 
and testpmd start parameter is 
tile-monitor  --dev gxpci0 --resume --upload testpmd  testpmd  --run  -+-  
./testpmd   -c 0x -m 2048 -n 1 -r 1 --vdev xgbe1 --  --rx=1  --tx=2 
--forward-mode=txonly -a --port-topology=chained -+-

 but xgbe1 can't xmit any packet.  
This is my run log:

EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 6 on socket 0
EAL: Detected lcore 7 as core 7 on socket 0
EAL: Detected lcore 8 as core 8 on socket 0
EAL: Detected lcore 9 as core 9 on socket 0
EAL: Detected lcore 10 as core 10 on socket 0
EAL: Detected lcore 11 as core 11 on socket 0
EAL: Detected lcore 12 as core 12 on socket 0
EAL: Detected lcore 13 as core 13 on socket 0
EAL: Detected lcore 14 as core 14 on socket 0
EAL: Detected lcore 15 as core 15 on socket 0
EAL: Detected lcore 16 as core 16 on socket 0
EAL: Detected lcore 17 as core 17 on socket 0
EAL: Detected lcore 18 as core 18 on socket 0
EAL: Detected lcore 19 as core 19 on socket 0
EAL: Detected lcore 20 as core 20 on socket 0
EAL: Detected lcore 21 as core 21 on socket 0
EAL: Detected lcore 22 as core 22 on socket 0
EAL: Detected lcore 23 as core 23 on socket 0
EAL: Detected lcore 24 as core 24 on socket 0
EAL: Detected lcore 25 as core 25 on socket 0
EAL: Detected lcore 26 as core 26 on socket 0
EAL: Detected lcore 27 as core 27 on socket 0
EAL: Detected lcore 28 as core 28 on socket 0
EAL: Detected lcore 29 as core 29 on socket 0
EAL: Detected lcore 30 as core 30 on socket 0
EAL: Detected lcore 31 as core 31 on socket 0
EAL: Detected lcore 32 as core 32 on socket 0
EAL: Detected lcore 33 as core 33 on socket 0
EAL: Detected lcore 34 as core 34 on socket 0
EAL: Detected lcore 35 as core 35 on socket 0
EAL: Support maximum 36 logical core(s) by configuration.
EAL: Detected 36 lcore(s)
EAL: No free hugepages reported in hugepages-1024kB
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x1600 bytes
EAL: Virtual area found at 0x1ffd100 (size = 0x1600)
EAL: Ask a virtual area of 0x9000 bytes
EAL: Virtual area found at 0x1ff4000 (size = 0x9000)
EAL: Ask a virtual area of 0x200 bytes
EAL: Virtual area found at 0x1ff3d00 (size = 0x200)
EAL: Ask a virtual area of 0x1000 bytes
EAL: Virtual area found at 0x1ff2c00 (size = 0x1000)
EAL: Ask a virtual area of 0x4600 bytes
EAL: Virtual area found at 0x1fee500 (size = 0x4600)
EAL: Ask a virtual area of 0x200 bytes
EAL: Virtual area found at 0x1fee200 (size = 0x200)
EAL: Requesting 128 pages of size 16MB from socket 0
EAL: TSC frequency is ~119 KHz
EAL: WARNING: cpu flags constant_tsc=no nonstop_tsc=no -> using unreliable 
clock cycles !
EAL: Master lcore 0 is ready (tid=f7fa4690;cpuset=[0])
PMD: mpipe init xgbe1
PMD: xgbe1: Initialized mpipe device(mac ee:d1:53:72:82:5a).
EAL: lcore 1 is ready (tid=eb04f060;cpuset=[1])
EAL: lcore 2 is ready (tid=ea84f060;cpuset=[2])
EAL: lcore 3 is ready (tid=ea04f060;cpuset=[3])
EAL: lcore 4 is ready (tid=e984f060;cpuset=[4])
EAL: lcore 5 is ready (tid=d0fff060;cpuset=[5])
EAL: lcore 6 is ready (tid=d07ff060;cpuset=[6])
EAL: lcore 7 is ready (tid=e904f060;cpuset=[7])
EAL: lcore 8 is ready (tid=e884f060;cpuset=[8])
EAL: lcore 9 is ready (tid=e804f060;cpuset=[9])
EAL: lcore 10 is ready (tid=e784f060;cpuset=[10])
EAL: lcore 11 is ready (tid=b3fff060;cpuset=[11])
EAL: lcore 12 is ready (tid=b37ff060;cpuset=[12])
EAL: lcore 13 is ready (tid=b2fff060;cpuset=[13])
EAL: lcore 14 is ready (tid=b27ff060;cpuset=[14])
EAL: lcore 15 is ready (tid=b1fff060;cpuset=[15])
EAL: lcore 16 is ready (tid=b17ff060;cpuset=[16])
EAL: lcore 17 is ready (tid=b0fff060;cpuset=[17])
EAL: lcore 18 is ready (tid=2060;cpuset=[18])
EAL: lcore 19 is ready (tid=b07ff060;cpuset=[19])
EAL: lco

[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-23 Thread Arthas
Hi, ZhiGang
  I checked source code and debug it , found dpdk function rte_eth_tx_burst 
with tilegx return 0 and no other error.  Can I contact 
 you directly?
Regards,
  Arthas



-- Original --
From:  "Arthas";<kangzy1...@qq.com>;
Date:  Wed, Sep 23, 2015 06:35 PM
To:  "zlu"; "dev"; 

Subject:  Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, ZhiGang
   My tilegx boot parameter is "tile-monitor --dev gxpci${1} --hv-bin-dir 
/tilegx/tile/hv-bin-dir424/ --hvx dataplane=1-64". 
and testpmd start parameter is 
tile-monitor  --dev gxpci0 --resume --upload testpmd  testpmd  --run  -+-  
./testpmd   -c 0x -m 2048 -n 1 -r 1 --vdev xgbe1 --  --rx=1  --tx=2 
--forward-mode=txonly -a --port-topology=chained -+-

 but xgbe1 can't xmit any packet.  
This is my run log:

EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 6 on socket 0
EAL: Detected lcore 7 as core 7 on socket 0
EAL: Detected lcore 8 as core 8 on socket 0
EAL: Detected lcore 9 as core 9 on socket 0
EAL: Detected lcore 10 as core 10 on socket 0
EAL: Detected lcore 11 as core 11 on socket 0
EAL: Detected lcore 12 as core 12 on socket 0
EAL: Detected lcore 13 as core 13 on socket 0
EAL: Detected lcore 14 as core 14 on socket 0
EAL: Detected lcore 15 as core 15 on socket 0
EAL: Detected lcore 16 as core 16 on socket 0
EAL: Detected lcore 17 as core 17 on socket 0
EAL: Detected lcore 18 as core 18 on socket 0
EAL: Detected lcore 19 as core 19 on socket 0
EAL: Detected lcore 20 as core 20 on socket 0
EAL: Detected lcore 21 as core 21 on socket 0
EAL: Detected lcore 22 as core 22 on socket 0
EAL: Detected lcore 23 as core 23 on socket 0
EAL: Detected lcore 24 as core 24 on socket 0
EAL: Detected lcore 25 as core 25 on socket 0
EAL: Detected lcore 26 as core 26 on socket 0
EAL: Detected lcore 27 as core 27 on socket 0
EAL: Detected lcore 28 as core 28 on socket 0
EAL: Detected lcore 29 as core 29 on socket 0
EAL: Detected lcore 30 as core 30 on socket 0
EAL: Detected lcore 31 as core 31 on socket 0
EAL: Detected lcore 32 as core 32 on socket 0
EAL: Detected lcore 33 as core 33 on socket 0
EAL: Detected lcore 34 as core 34 on socket 0
EAL: Detected lcore 35 as core 35 on socket 0
EAL: Support maximum 36 logical core(s) by configuration.
EAL: Detected 36 lcore(s)
EAL: No free hugepages reported in hugepages-1024kB
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x1600 bytes
EAL: Virtual area found at 0x1ffd100 (size = 0x1600)
EAL: Ask a virtual area of 0x9000 bytes
EAL: Virtual area found at 0x1ff4000 (size = 0x9000)
EAL: Ask a virtual area of 0x200 bytes
EAL: Virtual area found at 0x1ff3d00 (size = 0x200)
EAL: Ask a virtual area of 0x1000 bytes
EAL: Virtual area found at 0x1ff2c00 (size = 0x1000)
EAL: Ask a virtual area of 0x4600 bytes
EAL: Virtual area found at 0x1fee500 (size = 0x4600)
EAL: Ask a virtual area of 0x200 bytes
EAL: Virtual area found at 0x1fee200 (size = 0x200)
EAL: Requesting 128 pages of size 16MB from socket 0
EAL: TSC frequency is ~119 KHz
EAL: WARNING: cpu flags constant_tsc=no nonstop_tsc=no -> using unreliable 
clock cycles !
EAL: Master lcore 0 is ready (tid=f7fa4690;cpuset=[0])
PMD: mpipe init xgbe1
PMD: xgbe1: Initialized mpipe device(mac ee:d1:53:72:82:5a).
EAL: lcore 1 is ready (tid=eb04f060;cpuset=[1])
EAL: lcore 2 is ready (tid=ea84f060;cpuset=[2])
EAL: lcore 3 is ready (tid=ea04f060;cpuset=[3])
EAL: lcore 4 is ready (tid=e984f060;cpuset=[4])
EAL: lcore 5 is ready (tid=d0fff060;cpuset=[5])
EAL: lcore 6 is ready (tid=d07ff060;cpuset=[6])
EAL: lcore 7 is ready (tid=e904f060;cpuset=[7])
EAL: lcore 8 is ready (tid=e884f060;cpuset=[8])
EAL: lcore 9 is ready (tid=e804f060;cpuset=[9])
EAL: lcore 10 is ready (tid=e784f060;cpuset=[10])
EAL: lcore 11 is ready (tid=b3fff060;cpuset=[11])
EAL: lcore 12 is ready (tid=b37ff060;cpuset=[12])
EAL: lcore 13 is ready (tid=b2fff060;cpuset=[13])
EAL: lcore 14 is ready (tid=b27ff060;cpuset=[14])
EAL: lcore 15 is ready (tid=b1fff060;cpuset=[15])
EAL: lcore 16 is ready (tid=b17ff060;cpuset=[16])
EAL: lcore 17 is ready (tid=b0fff060;cpuset=[17])
EAL: lcore 18 is ready (tid=2060;cpuset=[18])
EAL: lcore 19 is ready (tid=b07ff060;cpuset=[19])
EAL: lcore 20 is ready (tid=abfff060;cpuset=[20])
EAL: lcore 21 is ready (tid=ab7ff060;cpuset=[21])
EAL: lcore 22 is ready (tid=aafff060;cpuset=[22])
EAL: lcore 23 is ready (tid=aa7ff060;cpuset=[23])
EAL: lcore 24 is ready (tid=2f7ff060;cpuset=[24])
EAL: lcore 25 is ready (tid=2efff060;cpuset=[25])
EAL: lcore 26 is ready (tid=2e7ff060;cpuset=[26])
EAL: lcore 27 is ready (tid=2dfff060;cpuset=[27])
EAL: lcore 28 is ready 

[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-23 Thread Arthas
0x1ffd1c8557f.
PMD: xgbe1: eDMA ring memory 0x1ffd1c8a000 - 0x1ffd1c8bfff.
PMD: xgbe1: iDMA ring 0 memory 0x1ffd1c86000 - 0x1ffd1c87fff.
Port 0: EE:D1:53:72:82:5A
Checking link statuses...
Port 0 Link Up - speed 1 Mbps - full-duplex
Done
No commandline core given, start packet forwarding
  txonly packet forwarding - CRC stripping disabled - packets/burst=32
  packet len=64 - nb packet segments=1
  nb forwarding cores=1 - nb forwarding ports=1
  RX queues=1 - RX desc=128 - RX free threshold=0
  RX threshold registers: pthresh=0 hthresh=0 wthresh=0
  TX queues=2 - TX desc=512 - TX free threshold=0
  TX threshold registers: pthresh=0 hthresh=0 wthresh=0
  TX RS bit threshold=0 - TXQ flags=0x0
Press enter to exit


and another tilegx card output:
Command: run mpipe-stat xgbe1
Link   Tx pkt  Tx bits   Rx pkt  Rx bits   Tx err   Rx err

xgbe1   000000



Regards, Arthas


-- Original --
From:  "zlu";<z...@ezchip.com>;
Date:  Wed, Sep 23, 2015 03:34 PM
To:  "Arthas"; "'dev'"; 

Subject:  RE: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, Arthas

Does testpmd run OK, and what is boot parameter you used to boot Tile-Gx?

>-Original Message-
>From: Arthas [mailto:kangzy1982 at qq.com]
>Sent: Wednesday, September 23, 2015 1:21 PM
>To: dev
>Cc: zlu
>Subject: Re: [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597
>
>and I wrote a sample RX example, got an other information.
>
>
>PMD: xgbe1: Could not register memseg @0x1ffd200, -.
>PMD: xgbe1: Could not register memseg @0x1ff4100, -.
>PMD: xgbe1: Could not register memseg @0x1ff3e00, -.
>PMD: xgbe1: Could not register memseg @0x1ff2d00, -.
>PMD: xgbe1: Could not register memseg @0x1fee600, -.
>PMD: xgbe1: Could not register memseg @0x1fee300, -.
>PMD: xgbe1: Buffer stack memory 0x1fee4b9 - 0x1fee4be557f.
>PMD: xgbe1: eDMA ring memory 0x1fee4bf - 0x1fee4bf1fff.
>PMD: xgbe1: iDMA ring 0 memory 0x1fee4bec000 - 0x1fee4bedfff.
>
>
>
>  Regards, Arthas
>
>-- Original --
>From:  "Arthas";;
>Date:  Wed, Sep 23, 2015 01:17 PM
>To:  "dev";
>Subject:  [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597
>
>Hi, I'm working on tilegx platform.  and I wrote a sample dpdk trafgen for
tilegx.
>But I got a error with rte_mbuf rte_pktmbuf_append.
>
>PANIC in rte_mbuf_sanity_check():
>bad phys addr
>7: [/trafgen(_start+0x70) [0x100b308]]
>6: [/lib/libc.so.6(__libc_start_main+0x200) [0x1fff7a6e4c8]]
>5: [/trafgen(main+0x2148) [0x1017b78]]
>4: [/trafgen(rte_pktmbuf_dump+0x58) [0x102c7a8]]
>3: [/trafgen(rte_mbuf_sanity_check+0x1a8) [0x102c700]]
>2: [/trafgen(__rte_panic+0xc0) [0x1091e80]]
>1: [/trafgen(rte_dump_stack+0x40) [0x104cf00]]
>
>
>DPDK compiled with CONFIG_RTE_LIBRTE_MBUF_DEBUG=y!
>
> Regards, Arthas


[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-23 Thread Arthas
and I wrote a sample RX example, got an other information.


PMD: xgbe1: Could not register memseg @0x1ffd200, -.
PMD: xgbe1: Could not register memseg @0x1ff4100, -.
PMD: xgbe1: Could not register memseg @0x1ff3e00, -.
PMD: xgbe1: Could not register memseg @0x1ff2d00, -.
PMD: xgbe1: Could not register memseg @0x1fee600, -.
PMD: xgbe1: Could not register memseg @0x1fee300, -.
PMD: xgbe1: Buffer stack memory 0x1fee4b9 - 0x1fee4be557f.
PMD: xgbe1: eDMA ring memory 0x1fee4bf - 0x1fee4bf1fff.
PMD: xgbe1: iDMA ring 0 memory 0x1fee4bec000 - 0x1fee4bedfff.


  Regards, Arthas


-- Original --
From:  "Arthas";<kangzy1...@qq.com>;
Date:  Wed, Sep 23, 2015 01:17 PM
To:  "dev"; 

Subject:  [dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597



Hi, I'm working on tilegx platform.  and I wrote a sample dpdk trafgen for 
tilegx.  But I got a error with rte_mbuf rte_pktmbuf_append.

PANIC in rte_mbuf_sanity_check():
bad phys addr
7: [/trafgen(_start+0x70) [0x100b308]]
6: [/lib/libc.so.6(__libc_start_main+0x200) [0x1fff7a6e4c8]]
5: [/trafgen(main+0x2148) [0x1017b78]]
4: [/trafgen(rte_pktmbuf_dump+0x58) [0x102c7a8]]
3: [/trafgen(rte_mbuf_sanity_check+0x1a8) [0x102c700]]
2: [/trafgen(__rte_panic+0xc0) [0x1091e80]]
1: [/trafgen(rte_dump_stack+0x40) [0x104cf00]]


DPDK compiled with CONFIG_RTE_LIBRTE_MBUF_DEBUG=y!

 Regards, Arthas


[dpdk-dev] DPDK v2.1.0 tilegx on TileraMDE-4.2.2.169597

2015-09-23 Thread Arthas
Hi, I'm working on tilegx platform.  and I wrote a sample dpdk trafgen for 
tilegx.  But I got a error with rte_mbuf rte_pktmbuf_append.

PANIC in rte_mbuf_sanity_check():
bad phys addr
7: [/trafgen(_start+0x70) [0x100b308]]
6: [/lib/libc.so.6(__libc_start_main+0x200) [0x1fff7a6e4c8]]
5: [/trafgen(main+0x2148) [0x1017b78]]
4: [/trafgen(rte_pktmbuf_dump+0x58) [0x102c7a8]]
3: [/trafgen(rte_mbuf_sanity_check+0x1a8) [0x102c700]]
2: [/trafgen(__rte_panic+0xc0) [0x1091e80]]
1: [/trafgen(rte_dump_stack+0x40) [0x104cf00]]


DPDK compiled with CONFIG_RTE_LIBRTE_MBUF_DEBUG=y!

 Regards, Arthas


[dpdk-dev] DPDK v2.1.0 with tilegx problem

2015-09-07 Thread Arthas
This problem had solved! My tilegx libgxio don't support 
'gxio_mpipe_link_enumerate_mac', only provide API ''gxio_mpipe_link_enumerate', 
add new api 'gxio_mpipe_link_enumerate_mac' for libgxio and compile ok! :)

  /*
 typedef struct
{
  /** The address. */
  uint8_t mac[6];
}
_gxio_mpipe_link_mac_t;
/tilegx/src/sys/hv/include/hv/drv_mpipe_intf.h
 */
 int
gxio_mpipe_link_enumerate_mac(int idx, char* link_name, uint8_t *hw)
{
  int rv;
  _gxio_mpipe_link_name_t name;
  _gxio_mpipe_link_mac_t mac;
   gxio_mpipe_context_t* context = _gxio_get_link_context();
  if (!context)
return GXIO_ERR_NO_DEVICE;
   rv = gxio_mpipe_info_enumerate_aux(context, idx, , );
  if (rv >= 0) {
strncpy(link_name, name.name, sizeof (name.name));
memcpy(hw, , sizeof(_gxio_mpipe_link_mac_t));
  }
  return rv;
}


  Regards,
Arthas



 -- Original --
  From:  "Arthas";;
 Date:  Sat, Sep 5, 2015 09:48 AM
 To:  "dev"; 

 Subject:  [dpdk-dev] DPDK v2.1.0 with tilegx problem



Hi, I'm working on tilegx platform. but when I compiled DPDK 2.1.0 with tilegx 
target. I got a error.

/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:182: error: 
'GXIO_MPIPE_IQUEUE_ENTRY_128' undeclared here (not in a function)
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:182: error: array index in 
initializer not of integer type
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:182: error: (near 
initialization for 'mpipe_iqueue_sizes')
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:183: error: 
'GXIO_MPIPE_IQUEUE_ENTRY_512' undeclared here (not in a function)
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:183: error: array index in 
initializer not of integer type
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:183: error: (near 
initialization for 'mpipe_iqueue_sizes')
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:184: error: 
'GXIO_MPIPE_IQUEUE_ENTRY_2K' undeclared here (not in a function)
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:184: error: array index in 
initializer not of integer type
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:184: error: (near 
initialization for 'mpipe_iqueue_sizes')
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:185: error: 
'GXIO_MPIPE_IQUEUE_ENTRY_64K' undeclared here (not in a function)
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:185: error: array index in 
initializer not of integer type
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:185: error: (near 
initialization for 'mpipe_iqueue_sizes')
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c: In function 
'mpipe_link_mac':
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:1545: warning: implicit 
declaration of function 'gxio_mpipe_link_enumerate_mac'
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:1545: warning: nested extern 
declaration of 'gxio_mpipe_link_enumerate_mac'

My tilegx MDE version is TileraMDE-4.2.4.174600, but I can't found any 
definition of GXIO_MPIPE_IQUEUE_ENTRY_128/512/2K/64K.  
only found gxio_mpipe_link_enumerate_mac is a kernel global symbol. 

Did someon got this problem?

Regards,
Arthas


[dpdk-dev] DPDK v2.1.0 with tilegx problem

2015-09-05 Thread Arthas
Hi, I'm working on tilegx platform. but when I compiled DPDK 2.1.0 with tilegx 
target. I got a error.

/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:182: error: 
'GXIO_MPIPE_IQUEUE_ENTRY_128' undeclared here (not in a function)
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:182: error: array index in 
initializer not of integer type
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:182: error: (near 
initialization for 'mpipe_iqueue_sizes')
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:183: error: 
'GXIO_MPIPE_IQUEUE_ENTRY_512' undeclared here (not in a function)
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:183: error: array index in 
initializer not of integer type
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:183: error: (near 
initialization for 'mpipe_iqueue_sizes')
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:184: error: 
'GXIO_MPIPE_IQUEUE_ENTRY_2K' undeclared here (not in a function)
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:184: error: array index in 
initializer not of integer type
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:184: error: (near 
initialization for 'mpipe_iqueue_sizes')
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:185: error: 
'GXIO_MPIPE_IQUEUE_ENTRY_64K' undeclared here (not in a function)
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:185: error: array index in 
initializer not of integer type
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:185: error: (near 
initialization for 'mpipe_iqueue_sizes')
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c: In function 
'mpipe_link_mac':
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:1545: warning: implicit 
declaration of function 'gxio_mpipe_link_enumerate_mac'
/DPDK/dpdk-v2.1.0/drivers/net/mpipe/mpipe_tilegx.c:1545: warning: nested extern 
declaration of 'gxio_mpipe_link_enumerate_mac'

My tilegx MDE version is TileraMDE-4.2.4.174600, but I can't found any 
definition of GXIO_MPIPE_IQUEUE_ENTRY_128/512/2K/64K.  
only found gxio_mpipe_link_enumerate_mac is a kernel global symbol. 

Did someon got this problem?

Regards,
Arthas


[dpdk-dev] DPDK v2.0 testpmd with Mellanox ConnectX-3problem!

2015-04-27 Thread Arthas
Hi, Olga,
 I think I have solved this problem. 
 libibverbs & libmlx4 can't use dpdp.org and can't compile with static linking.
 I try use libibverbs-1.1.8mlnx1-OFED.2.4.45.ga305acd.src.rpm & 
libmlx4-1.0.6mlnx1-OFED.2.4.0.1.2.src and compile with dynamic. This two 
package in MLNX_OFED version 2.4-1.0.0 source package.
 and I use ofed_script  connectx_port_config  config Card with Ethernet mode .
 The testpmd was started with no error! :)

  Thanks a million!! :)

 Best Regards!
Kang


 -- Original --
  From:  "Arthas";;
 Date:  Mon, Apr 27, 2015 10:37 AM
 To:  "Olga Shern"; "dev"; 

 Subject:  Re: [dpdk-dev] DPDK v2.0 testpmd with Mellanox ConnectX-3problem!



3KS, Olga,
  My MLNX_OFED version 2.4-1.0.0 and libibverbs & libmlx4 download from 
dpdk.org. 
 when i try to run ibdev2netdev , it don't output any message! :(
 Here is my environment.
 # uname -r
3.10.0-mlx
 # lsmod 
mlx4_en 92824 0 - Live 0xa010f000 (O)
mlx4_ib 135033 0 - Live 0xa00e3000 (O)
ib_sa 24721 1 mlx4_ib, Live 0xa00d7000 (O)
ib_mad 31664 2 mlx4_ib,ib_sa, Live 0xa00ca000 (O)
mlx4_core 226516 2 mlx4_en,mlx4_ib, Live 0xa007c000 (O)
ib_uverbs 43309 0 - Live 0xa003f000 (O)
ib_core 79534 4 mlx4_ib,ib_sa,ib_mad,ib_uverbs, Live 0xa001d000 (O)
ib_addr 4273 2 ib_uverbs,ib_core, Live 0xa0017000 (O)
compat 4948 8 mlx4_en,mlx4_ib,ib_sa,ib_mad,mlx4_core,ib_uverbs,ib_core,ib_addr, 
Live 0xa0011000 (O)
 # mstflint  -d 02:00.0 q
Image type:  FS2
FW Version:  2.33.5100
FW Release Date: 25.1.2015
Product Version: 02.33.51.00
Rom Info:type=PXE version=3.4.460 devid=4099
Device ID:   4099
Description: Node Port1Port2Sys image
GUIDs:   0002c90300faa480 0002c90300faa481 0002c90300faa482 
0002c90300faa483 
MACs: 0002c9faa481 0002c9faa482
VSD: 
PSID:MT_1090110019
# ibv_devices 
libibverbs: Warning: dlopen(NULL) failed, assuming static linking.
libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
When linking libibverbs statically, driver must be statically linked 
too.
device node GUID
--  
 # ibv_devinfo  -l
libibverbs: Warning: dlopen(NULL) failed, assuming static linking.
libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
When linking libibverbs statically, driver must be statically linked 
too.
0 HCAs found:

/sys/class/infiniband_verbs # ls
abi_version  uverbs0
 # find . -name "mlx4*"
./proc/irq/148/mlx4-32 at :02:00.0
./proc/irq/147/mlx4-31 at :02:00.0
./proc/irq/146/mlx4-30 at :02:00.0
./proc/irq/145/mlx4-29 at :02:00.0
./proc/irq/144/mlx4-28 at :02:00.0
./proc/irq/143/mlx4-27 at :02:00.0
./proc/irq/142/mlx4-26 at :02:00.0
./proc/irq/141/mlx4-25 at :02:00.0
./proc/irq/140/mlx4-24 at :02:00.0
./proc/irq/139/mlx4-23 at :02:00.0
./proc/irq/138/mlx4-22 at :02:00.0
./proc/irq/137/mlx4-21 at :02:00.0
./proc/irq/136/mlx4-20 at :02:00.0
./proc/irq/135/mlx4-19 at :02:00.0
./proc/irq/134/mlx4-18 at :02:00.0
./proc/irq/133/mlx4-17 at :02:00.0
./proc/irq/132/mlx4-16 at :02:00.0
./proc/irq/131/mlx4-15 at :02:00.0
./proc/irq/130/mlx4-14 at :02:00.0
./proc/irq/129/mlx4-13 at :02:00.0
./proc/irq/128/mlx4-12 at :02:00.0
./proc/irq/127/mlx4-11 at :02:00.0
./proc/irq/126/mlx4-10 at :02:00.0
./proc/irq/125/mlx4-9 at :02:00.0
./proc/irq/124/mlx4-8 at :02:00.0
./proc/irq/123/mlx4-7 at :02:00.0
./proc/irq/122/mlx4-6 at :02:00.0
./proc/irq/121/mlx4-5 at :02:00.0
./proc/irq/120/mlx4-4 at :02:00.0
./proc/irq/119/mlx4-3 at :02:00.0
./proc/irq/118/mlx4-2 at :02:00.0
./proc/irq/117/mlx4-1 at :02:00.0
./proc/irq/116/mlx4-async at pci::02:00.0
./proc/driver/mlx4_ib
./sys/bus/pci/drivers/mlx4_core
./sys/devices/pci:00/:00:02.0/:02:00.0/mlx4_port1_mtu
./sys/devices/pci:00/:00:02.0/:02:00.0/mlx4_port2_mtu
./sys/devices/pci:00/:00:02.0/:02:00.0/infiniband/mlx4_0
./sys/devices/pci:00/:00:02.0/:02:00.0/mlx4_port1
./sys/devices/pci:00/:00:02.0/:02:00.0/mlx4_port2
./sys/class/infiniband/mlx4_0
./sys/module/ib_sa/holders/mlx4_ib
./sys/module/compat/holders/mlx4_en
./sys/module/compat/holders/mlx4_ib
./sys/module/compat/holders/mlx4_core
./sys/module/mlx4_en
./sys/module/mlx4_ib
./sys/module/ib_mad/holders/mlx4_ib
./sys/module/ib_core/holders/mlx4_ib
./sys/module/mlx4_core
./sys/module/mlx4_core/holders/mlx4_en
./sys/module/mlx4_core/holders/mlx4_ib
./lib/modules/3.10.0-mlx/extra/mlnx-ofa_kernel/drivers/net/ethernet/mellanox/mlx4
./lib/modules/3.10.0-mlx/extra/mlnx-ofa_kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_en.ko
./lib/modules/3.10.0-mlx/extr

[dpdk-dev] DPDK v2.0 testpmd with Mellanox ConnectX-3problem!

2015-04-27 Thread Arthas
3KS, Olga,
  My MLNX_OFED version 2.4-1.0.0 and libibverbs & libmlx4 download from 
dpdk.org. 
 when i try to run ibdev2netdev , it don't output any message! :(
 Here is my environment.
 # uname -r
3.10.0-mlx
 # lsmod 
mlx4_en 92824 0 - Live 0xa010f000 (O)
mlx4_ib 135033 0 - Live 0xa00e3000 (O)
ib_sa 24721 1 mlx4_ib, Live 0xa00d7000 (O)
ib_mad 31664 2 mlx4_ib,ib_sa, Live 0xa00ca000 (O)
mlx4_core 226516 2 mlx4_en,mlx4_ib, Live 0xa007c000 (O)
ib_uverbs 43309 0 - Live 0xa003f000 (O)
ib_core 79534 4 mlx4_ib,ib_sa,ib_mad,ib_uverbs, Live 0xa001d000 (O)
ib_addr 4273 2 ib_uverbs,ib_core, Live 0xa0017000 (O)
compat 4948 8 mlx4_en,mlx4_ib,ib_sa,ib_mad,mlx4_core,ib_uverbs,ib_core,ib_addr, 
Live 0xa0011000 (O)
 # mstflint  -d 02:00.0 q
Image type:  FS2
FW Version:  2.33.5100
FW Release Date: 25.1.2015
Product Version: 02.33.51.00
Rom Info:type=PXE version=3.4.460 devid=4099
Device ID:   4099
Description: Node Port1Port2Sys image
GUIDs:   0002c90300faa480 0002c90300faa481 0002c90300faa482 
0002c90300faa483 
MACs: 0002c9faa481 0002c9faa482
VSD: 
PSID:MT_1090110019
# ibv_devices 
libibverbs: Warning: dlopen(NULL) failed, assuming static linking.
libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
When linking libibverbs statically, driver must be statically linked 
too.
device node GUID
--  
 # ibv_devinfo  -l
libibverbs: Warning: dlopen(NULL) failed, assuming static linking.
libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
When linking libibverbs statically, driver must be statically linked 
too.
0 HCAs found:

/sys/class/infiniband_verbs # ls
abi_version  uverbs0
 # find . -name "mlx4*"
./proc/irq/148/mlx4-32 at :02:00.0
./proc/irq/147/mlx4-31 at :02:00.0
./proc/irq/146/mlx4-30 at :02:00.0
./proc/irq/145/mlx4-29 at :02:00.0
./proc/irq/144/mlx4-28 at :02:00.0
./proc/irq/143/mlx4-27 at :02:00.0
./proc/irq/142/mlx4-26 at :02:00.0
./proc/irq/141/mlx4-25 at :02:00.0
./proc/irq/140/mlx4-24 at :02:00.0
./proc/irq/139/mlx4-23 at :02:00.0
./proc/irq/138/mlx4-22 at :02:00.0
./proc/irq/137/mlx4-21 at :02:00.0
./proc/irq/136/mlx4-20 at :02:00.0
./proc/irq/135/mlx4-19 at :02:00.0
./proc/irq/134/mlx4-18 at :02:00.0
./proc/irq/133/mlx4-17 at :02:00.0
./proc/irq/132/mlx4-16 at :02:00.0
./proc/irq/131/mlx4-15 at :02:00.0
./proc/irq/130/mlx4-14 at :02:00.0
./proc/irq/129/mlx4-13 at :02:00.0
./proc/irq/128/mlx4-12 at :02:00.0
./proc/irq/127/mlx4-11 at :02:00.0
./proc/irq/126/mlx4-10 at :02:00.0
./proc/irq/125/mlx4-9 at :02:00.0
./proc/irq/124/mlx4-8 at :02:00.0
./proc/irq/123/mlx4-7 at :02:00.0
./proc/irq/122/mlx4-6 at :02:00.0
./proc/irq/121/mlx4-5 at :02:00.0
./proc/irq/120/mlx4-4 at :02:00.0
./proc/irq/119/mlx4-3 at :02:00.0
./proc/irq/118/mlx4-2 at :02:00.0
./proc/irq/117/mlx4-1 at :02:00.0
./proc/irq/116/mlx4-async at pci::02:00.0
./proc/driver/mlx4_ib
./sys/bus/pci/drivers/mlx4_core
./sys/devices/pci:00/:00:02.0/:02:00.0/mlx4_port1_mtu
./sys/devices/pci:00/:00:02.0/:02:00.0/mlx4_port2_mtu
./sys/devices/pci:00/:00:02.0/:02:00.0/infiniband/mlx4_0
./sys/devices/pci:00/:00:02.0/:02:00.0/mlx4_port1
./sys/devices/pci:00/:00:02.0/:02:00.0/mlx4_port2
./sys/class/infiniband/mlx4_0
./sys/module/ib_sa/holders/mlx4_ib
./sys/module/compat/holders/mlx4_en
./sys/module/compat/holders/mlx4_ib
./sys/module/compat/holders/mlx4_core
./sys/module/mlx4_en
./sys/module/mlx4_ib
./sys/module/ib_mad/holders/mlx4_ib
./sys/module/ib_core/holders/mlx4_ib
./sys/module/mlx4_core
./sys/module/mlx4_core/holders/mlx4_en
./sys/module/mlx4_core/holders/mlx4_ib
./lib/modules/3.10.0-mlx/extra/mlnx-ofa_kernel/drivers/net/ethernet/mellanox/mlx4
./lib/modules/3.10.0-mlx/extra/mlnx-ofa_kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_en.ko
./lib/modules/3.10.0-mlx/extra/mlnx-ofa_kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_core.ko
./lib/modules/3.10.0-mlx/extra/mlnx-ofa_kernel/drivers/infiniband/hw/mlx4
./lib/modules/3.10.0-mlx/extra/mlnx-ofa_kernel/drivers/infiniband/hw/mlx4/mlx4_ib.ko
./sdd/tmp/mlx4.driver
./sdd/tmp/mlx4
./sdd/tmp/mlx4/mlx4.hw
./sdd/tmp/mlx4/mlx4.config
./sdd/tmp/mlx4/mlx4.img.2.10.700
./sdd/tmp/etc/modprobe.d/mlx4.conf
./etc/libibverbs.d/mlx4.driver
./etc/modprobe.d/mlx4.conf




 -- Original --
  From:  "Olga Shern";;
 Date:  Sun, Apr 26, 2015 03:28 PM
 To:  "Arthas"; "dev"; 

 Subject:  RE: RE: [dpdk-dev] DPDK v2.0 testpmd with Mellanox ConnectX-3problem!




Hi Kang, 



Sorry for the late response. 

Connec