DPDK patches and discussions
 help / color / mirror / Atom feed
From: Keunhong Lee <dlrmsghd@gmail.com>
To: Jakub Mazur <jakub.mazur103@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Receive errors on all packets with multi-queues
Date: Mon, 29 Jun 2015 09:23:43 +0900	[thread overview]
Message-ID: <CAKBXKmBkhecAudNUgNKdhoTs-0OK1f0oex_5jZZccfh9faMX6A@mail.gmail.com> (raw)
In-Reply-To: <CAOthqY0jd_uZQ3szKmtxC5VW4PKVqc8gcDBTb1sBVryAQYCjpg@mail.gmail.com>

Did you set RSS mode?
Multi-queue RX won't work unless you have set RSS(Receive Side Scaling).

Keunhong.


2015-06-22 14:34 GMT+09:00 Jakub Mazur <jakub.mazur103@gmail.com>:

> Hi
>
> I'm having problems with packets received when running 2 receive queues (on
> seperate lcores) on the same port but when I run 1 queue everything works
> correctly. The queues are using 32 bursts and are using the same mempool
> which is allocated on the same socket as the NIC, as are the queues. When
> checking the stats of the port using rte_eth_stats_get nearly all of the
> received packets are errors. I'm generating packets using Pktgen with 64
> byte frames and using ranges on the src ip for rss filtering.
>
> Heres the output:
>
> $ sudo -E ./build/app/newapp -c 0xb -n 3 -d
> ../../../dpdk-2.0.0/x86_64-native-linuxapp-gcc/lib/librte_pmd_ixgbe.so
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 0 on socket 1
> EAL: Detected lcore 2 as core 1 on socket 0
> EAL: Detected lcore 3 as core 1 on socket 1
> EAL: Detected lcore 4 as core 2 on socket 0
> EAL: Detected lcore 5 as core 2 on socket 1
> EAL: Detected lcore 6 as core 3 on socket 0
> EAL: Detected lcore 7 as core 3 on socket 1
> EAL: Detected lcore 8 as core 4 on socket 0
> EAL: Detected lcore 9 as core 4 on socket 1
> EAL: Detected lcore 10 as core 5 on socket 0
> EAL: Detected lcore 11 as core 5 on socket 1
> EAL: Detected lcore 12 as core 6 on socket 0
> EAL: Detected lcore 13 as core 6 on socket 1
> EAL: Detected lcore 14 as core 7 on socket 0
> EAL: Detected lcore 15 as core 7 on socket 1
> EAL: Detected lcore 16 as core 0 on socket 0
> EAL: Detected lcore 17 as core 0 on socket 1
> EAL: Detected lcore 18 as core 1 on socket 0
> EAL: Detected lcore 19 as core 1 on socket 1
> EAL: Detected lcore 20 as core 2 on socket 0
> EAL: Detected lcore 21 as core 2 on socket 1
> EAL: Detected lcore 22 as core 3 on socket 0
> EAL: Detected lcore 23 as core 3 on socket 1
> EAL: Detected lcore 24 as core 4 on socket 0
> EAL: Detected lcore 25 as core 4 on socket 1
> EAL: Detected lcore 26 as core 5 on socket 0
> EAL: Detected lcore 27 as core 5 on socket 1
> EAL: Detected lcore 28 as core 6 on socket 0
> EAL: Detected lcore 29 as core 6 on socket 1
> EAL: Detected lcore 30 as core 7 on socket 0
> EAL: Detected lcore 31 as core 7 on socket 1
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 32 lcore(s)
> EAL: Setting up memory...
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7fc98fe00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x3fc00000 bytes
> EAL: Virtual area found at 0x7fc950000000 (size = 0x3fc00000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7fc94fc00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x3f600000 bytes
> EAL: Virtual area found at 0x7fc910400000 (size = 0x3f600000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7fc90fe00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7fc90f800000 (size = 0x400000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7fc90f400000 (size = 0x200000)
> EAL: Requesting 512 pages of size 2MB from socket 0
> EAL: Requesting 512 pages of size 2MB from socket 1
> EAL: TSC frequency is ~2900000 KHz
> EAL: open shared lib
> ../../../dpdk-2.0.0/x86_64-native-linuxapp-gcc/lib/librte_pmd_ixgbe.so
> EAL: Master lcore 0 is ready (tid=94769900;cpuset=[0])
> EAL: lcore 3 is ready (tid=dff1700;cpuset=[3])
> EAL: lcore 1 is ready (tid=e7f2700;cpuset=[1])
> EAL: PCI device 0000:05:00.1 on NUMA socket 1
> EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
> EAL:   PCI memory mapped at 0x7fc990000000
> EAL:   PCI memory mapped at 0x7fc990080000
> # of eth ports = 1
> rte_eth_dev_configure() for port 0 done
> rte_eth_rx_queue_setup() for port 0 queue 0 done
> rte_eth_rx_queue_setup() for port 0 queue 1 done
> rte_eth_tx_queue_setup() for port 0 queue 0 done
> rte_eth_tx_queue_setup() for port 0 queue 1 done
> rte_eth_dev_start() for port 0 done
> Core 1 starting
> Core 3 starting
> Bytes: 2048
> Packets: 32
> Missed: 13255672
> Sent: 64
>
> Any help would be appreciated.
>

      reply	other threads:[~2015-06-29  0:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22  5:34 Jakub Mazur
2015-06-29  0:23 ` Keunhong Lee [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=CAKBXKmBkhecAudNUgNKdhoTs-0OK1f0oex_5jZZccfh9faMX6A@mail.gmail.com \
    --to=dlrmsghd@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jakub.mazur103@gmail.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).