After trial and error, I found it's because I only enable one port, so once
the packet  fills up all my rx descriptor, the rest of incoming packet
becomes RX-errors.
If I set the rxd to 2048, then the RX-packets will be 2047.
./testpmd  -c 0xff -n2 -v -m 128M -- --burst=128 -i --rxq 2 --txq 2 --rxd
2048 --txd 2048
(Please correct me if I'm wrong)

So I think this is the right behaviour. Thanks.




On Fri, Mar 28, 2014 at 3:26 PM, William Tu <u9012063 at gmail.com> wrote:

> Hi folks,
>
> I'm using two servers connected back to back using 2 Intel 82599 10G NICs
> to test the dpdk. At the sender side, I use dpdk Pktgen to generate UDP
> packet.  I program the destination mac statically to make sure no ARP is
> necessary.
>
> My first experiments using Pktgen on both sender and receiver shows around
> 6M pkt/sec, with each packet having 128 byte. Then I replace the receiver
> side with testpmd
> " x86_64-default-linuxapp-gcc/app/testpmd -c ff -n 4 -- -i "
> and the sender side remains the same setting using Pktgen.
>
> As shown below, once my testpmd receives 127 packets, the rest of all
> packets becomes RX-errors.  I try lower down the sender's rate to only 10%
> but still the same.
>   ######################## NIC statistics for port 0
> ########################
>   RX-packets: 127        RX-errors: 145675959 RX-bytes: 16256
>   TX-packets: 0          TX-errors: 0         TX-bytes: 0
>
> ############################################################################
>
> Can anyone gives me some comments?
> Thank you.
>
> William (Cheng-Chun Tu)
>
>
>
> My system does not have numa, below is a full log at rx side:
> bitmask: ff
> Launching app
> 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 0 on socket 0
> EAL: Detected lcore 5 as core 1 on socket 0
> EAL: Detected lcore 6 as core 2 on socket 0
> EAL: Detected lcore 7 as core 3 on socket 0
> EAL: Setting up hugepage memory...
> EAL: Ask a virtual area of 0x2097152 bytes
> EAL: Virtual area found at 0x7f577ea00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x2097152 bytes
> EAL: Virtual area found at 0x7f577e600000 (size = 0x200000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f577e000000 (size = 0x400000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f577da00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x8388608 bytes
> EAL: Virtual area found at 0x7f577d000000 (size = 0x800000)
> EAL: Ask a virtual area of 0x8388608 bytes
> EAL: Virtual area found at 0x7f577c600000 (size = 0x800000)
> EAL: Ask a virtual area of 0x12582912 bytes
> EAL: Virtual area found at 0x7f577b800000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f577b200000 (size = 0x400000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f577ac00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x12582912 bytes
> EAL: Virtual area found at 0x7f5779e00000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f5779800000 (size = 0x400000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f5779200000 (size = 0x400000)
> EAL: Ask a virtual area of 0x12582912 bytes
> EAL: Virtual area found at 0x7f5778400000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f5777e00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x12582912 bytes
> EAL: Virtual area found at 0x7f5777000000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f5776a00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f5776400000 (size = 0x400000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f5775e00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x138412032 bytes
> EAL: Virtual area found at 0x7f576d800000 (size = 0x8400000)
> EAL: Ask a virtual area of 0x12582912 bytes
> EAL: Virtual area found at 0x7f576ca00000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x4194304 bytes
> EAL: Virtual area found at 0x7f576c400000 (size = 0x400000)
> EAL: Requesting 128 pages of size 2MB from socket 0
> EAL: TSC frequency is ~3400025 KHz
> EAL: Master core 0 is ready (tid=7ecef820)
> EAL: Core 3 is ready (tid=6abfc700)
> EAL: Core 6 is ready (tid=63fff700)
> EAL: Core 4 is ready (tid=6a3fb700)
> EAL: Core 7 is ready (tid=693f9700)
> EAL: Core 5 is ready (tid=69bfa700)
> EAL: Core 1 is ready (tid=6bbfe700)
> EAL: Core 2 is ready (tid=6b3fd700)
> EAL: PCI device 0000:01:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
> EAL:   PCI memory mapped at 0x7f577ec3c000
> EAL:   PCI memory mapped at 0x7f577ed02000
> EAL: PCI device 0000:01:00.1 on NUMA socket -1
> EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
> EAL:   PCI memory mapped at 0x7f577e8fe000
> EAL:   PCI memory mapped at 0x7f577e8fa000
> EAL: PCI device 0000:02:10.0 on NUMA socket -1
> EAL:   probe driver: 8086:10ed rte_ixgbevf_pmd
> EAL:   0000:02:10.0 not managed by UIO driver, skipping
> EAL: PCI device 0000:02:10.2 on NUMA socket -1
> EAL:   probe driver: 8086:10ed rte_ixgbevf_pmd
> EAL:   0000:02:10.2 not managed by UIO driver, skipping
> EAL: PCI device 0000:04:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:10d3 rte_em_pmd
> EAL:   0000:04:00.0 not managed by UIO driver, skipping
> EAL: PCI device 0000:05:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:10d3 rte_em_pmd
> EAL:   0000:05:00.0 not managed by UIO driver, skipping
> Interactive-mode selected
> Configuring Port 0 (socket -1)
> Configuring Port 1 (socket -1)
> Checking link statuses...
> Port 0 Link Up - speed 10000 Mbps - full-duplex
> Port 1 Link Down
> Done
> testpmd> show port stats all
>
>   ######################## NIC statistics for port 0
> ########################
>   RX-packets: 127        RX-errors: 764471    RX-bytes: 16256
>   TX-packets: 0          TX-errors: 0         TX-bytes: 0
>
> ############################################################################
>
>

Reply via email to