DPDK patches and discussions
 help / color / mirror / Atom feed
From: Victor Detoni <victordetoni@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] ip_reassembly doesn't start
Date: Sun, 10 Apr 2016 23:09:37 -0300	[thread overview]
Message-ID: <CANpwN=tNVp+dESae-XZKT4ETkKxapn_5Lye5N4t7_SdCnovOcg@mail.gmail.com> (raw)

hi,

I'm trying to run ip_reassembly application but it is showing the error
below. please, someone knows what's happing?

The other app like l2fwd/l3fwd works fine.


root@ubuntu:~# cd dpdk-2.1.0/examples/ip_reassembly/
root@ubuntu:~/dpdk-2.1.0/examples/ip_reassembly# ./build/ip_reassembly -c
0xff -n 1 -- -p 0x3 -q 2
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: Support maximum 128 logical core(s) by configuration.
EAL: Detected 8 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f2dfb400000 (size = 0x200000)
EAL: Ask a virtual area of 0x3f800000 bytes
EAL: Virtual area found at 0x7f2dbba00000 (size = 0x3f800000)
EAL: Ask a virtual area of 0x40400000 bytes
EAL: Virtual area found at 0x7f2d7b400000 (size = 0x40400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f2d7b000000 (size = 0x200000)
EAL: Requesting 1024 pages of size 2MB from socket 0
EAL: TSC frequency is ~2194711 KHz
EAL: Master lcore 0 is ready (tid=fd578940;cpuset=[0])
EAL: lcore 3 is ready (tid=79ffd700;cpuset=[3])
EAL: lcore 6 is ready (tid=787fa700;cpuset=[6])
EAL: lcore 1 is ready (tid=7afff700;cpuset=[1])
EAL: lcore 4 is ready (tid=797fc700;cpuset=[4])
EAL: lcore 7 is ready (tid=77ff9700;cpuset=[7])
EAL: lcore 5 is ready (tid=78ffb700;cpuset=[5])
EAL: lcore 2 is ready (tid=7a7fe700;cpuset=[2])
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   probe driver: 15ad:7b0 rte_vmxnet3_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:0b:00.0 on NUMA socket -1
EAL:   probe driver: 15ad:7b0 rte_vmxnet3_pmd
EAL:   PCI memory mapped at 0x7f2dfb600000
EAL:   PCI memory mapped at 0x7f2dfb601000
EAL:   PCI memory mapped at 0x7f2dfb602000
EAL: PCI device 0000:13:00.0 on NUMA socket -1
EAL:   probe driver: 15ad:7b0 rte_vmxnet3_pmd
EAL:   PCI memory mapped at 0x7f2dfb604000
EAL:   PCI memory mapped at 0x7f2dfb605000
EAL:   PCI memory mapped at 0x7f2dfb606000
0x7ffc7122d8af
IP_RSMBL: Creating LPM table on socket 0
IP_RSMBL: Creating LPM6 table on socket 0
USER1: rte_ip_frag_table_create: allocated of 25165952 bytes at socket 0
Initializing port 0 ...
EAL: Error - exiting with code: 1
  Cause: rte_eth_rx_queue_setup: err=-22, port=0

                 reply	other threads:[~2016-04-11  2:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CANpwN=tNVp+dESae-XZKT4ETkKxapn_5Lye5N4t7_SdCnovOcg@mail.gmail.com' \
    --to=victordetoni@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).