From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f172.google.com (mail-qt0-f172.google.com [209.85.216.172]) by dpdk.org (Postfix) with ESMTP id 8EA1A568E for ; Mon, 25 Jul 2016 21:30:56 +0200 (CEST) Received: by mail-qt0-f172.google.com with SMTP id u25so103261196qtb.1 for ; Mon, 25 Jul 2016 12:30:56 -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 :cc; bh=ZhBSAAz/hugz14VWajM0KByHFZ7efYj27rgmUoX4MYs=; b=Vg33OFZHzWX9LCt5n6sIEPAK0lNxnDsvqI7+o1ZOe3acdWWUvLRKqQI9mb2OhPrOlN Bk8LbUg5NUXO0SshdGcDUCQowobHuyMOeBceMPna1GyFfHzDGCca73PXf5QCmXHUqtxi lDozAa9G9NBOOwkxIagF5itGiBEBwRHZpik7HazjhPOvcXvfqALMvp4Fipw/O+vZmSyo szmw+PNf8gS5oS1APZaeQjcijP6mKNcFjHFYTmn8O+3V1Lk7nUs/Pi/GbbRLkMJ12ts9 /UPwSzHGRmAzhq6XOF6K9AVf/hQH/lbF75RhW3vsaAa4/YqtpLlTOqk9a63IKKwjbX85 ZFKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZhBSAAz/hugz14VWajM0KByHFZ7efYj27rgmUoX4MYs=; b=UopbthTtOxup5Ivp9Hy4seGeEzf1KUNryMhKzLEiPFHUQBBV/L9id+ToJMmyG+xkRx MoAINdRtJWodeRHvp27UwreMuRoaweU85bNbdo95Tdw/Swl7FJcdtZcDf98+RvwROqbi gO+gLA+VZy4S66ZFvHZVzXz0ZMychPeX33MY1PN13vTC3U4Cd2orsUhPnD79uO2wgZma GJTABEiqcLjpi7dmb6AzNbvG7hD3twQbDSpVNj7lV52nv79vMwzJYNplmfmjdTAI93F/ AYSLacZpwxwvUMVvDpueOrsxpmCJ/Im7GmQgljudlOXpsApWeQKNh6s0i4Om9ff0TscX Ey4g== X-Gm-Message-State: AEkooutAoYO+Ei0TL/rAdWrVATjDe3oU9TIvWpKQ0W+CM9M7BPxosnF+c/00WYfAlux3JjnG9EdLwq7w1YuoZw== X-Received: by 10.31.80.196 with SMTP id e187mr9198007vkb.29.1469475054869; Mon, 25 Jul 2016 12:30:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.148.18 with HTTP; Mon, 25 Jul 2016 12:30:53 -0700 (PDT) In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F0106D319@IRSMSX109.ger.corp.intel.com> References: <3AEA2BF9852C6F48A459DA490692831F0105B3E9@IRSMSX109.ger.corp.intel.com> <3AEA2BF9852C6F48A459DA490692831F01068AAC@IRSMSX109.ger.corp.intel.com> <3AEA2BF9852C6F48A459DA490692831F0106D03B@IRSMSX109.ger.corp.intel.com> <3AEA2BF9852C6F48A459DA490692831F0106D319@IRSMSX109.ger.corp.intel.com> From: Nishant Verma Date: Mon, 25 Jul 2016 15:30:53 -0400 Message-ID: To: "Pattan, Reshma" Cc: "users@dpdk.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] pdump help X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2016 19:30:57 -0000 Hi Reshma, 1. Not sure what exactly is the issue behind this. But as of now i did 2 things, in place of running setup.sh, i tried to give make command, with DESTDIR. Now i got exe. So if i execute the dpdk_pdump from this folder(destination directory that i gave at the time of building DPDK), it is working fine. But if i go in ./dpdk/app/pdump, build app here and then try to run it is not working. 2. Even their is no packet to capture, it showing error "insufficient data_len of mbuf" this is how i run and end pdump execution. " root@ubuntu:/home/oneweb/dpdk/install/bin# *./dpdk_pdump --file-prefix l3f -- --pdump 'port=3D0,queue=3D*,rx-dev=3D/tmp/rx-file.pcap,tx-dev=3D/tmp/tx-file.pcap,r= ing-size=3D1024,mbuf-size=3D20,total-num-mbufs=3D1025'* EAL: Detected 16 lcore(s) EAL: Probing VFIO support... EAL: VFIO support initialized EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the kernel. EAL: This may cause issues with mapping memory into secondary processes PMD: bnxt_rte_pmd_init() called for (null) EAL: PCI device 0000:03:00.0 on NUMA socket 0 EAL: probe driver: 8086:15ad rte_ixgbe_pmd EAL: PCI device 0000:03:00.1 on NUMA socket 0 EAL: probe driver: 8086:15ad rte_ixgbe_pmd PMD: eth_ixgbe_dev_init(): No TX queues configured yet. Using default TX function. EAL: PCI device 0000:05:00.0 on NUMA socket 0 EAL: probe driver: 8086:1521 rte_igb_pmd EAL: PCI device 0000:05:00.1 on NUMA socket 0 EAL: probe driver: 8086:1521 rte_igb_pmd PMD: Initializing pmd_pcap for eth_pcap_rx_0 PMD: Creating pcap-backed ethdev on numa socket 0 Port 2 MAC: 00 00 00 01 02 03 PMD: Initializing pmd_pcap for eth_pcap_tx_0 PMD: Creating pcap-backed ethdev on numa socket 0 Port 3 MAC: 00 00 00 01 02 03 ^C Signal 2 received, preparing to exit... ##### PDUMP DEBUG STATS ##### -packets dequeued: 0 -packets transmitted to vdev: 0 -packets freed: 0 " Here is what i get on *l3fwd *side.. " PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf PDUMP: User mempool: insufficient data_len of mbuf " Atlast it seems to be working, thanks for the much needed help. Rgds, Nishant On Mon, Jul 25, 2016 at 12:21 PM, Pattan, Reshma wrote: > Hi Nishant, > > > > The possible reasons for below error are > > > > 1) Either below falg is set to =E2=80=9Cn=E2=80=9D in config/common= _base file, > please set it to =E2=80=9Cy=E2=80=9D and compile again. > > If this falg is not in the config/comman_base for you, just check other > config files where this flag is there and make necessary change. > > # Compile software PMD backed by PCAP files > > # > > CONFIG_RTE_LIBRTE_PMD_PCAP=3Dn > > > > 2) (Or) you might be having dpdk code which don=E2=80=99t have below= fix. If > you don=E2=80=99t have this fix, please add this fix , compile and check = again. > > > > http://dpdk.org/dev/patchwork/patch/14709/ > > *diff --git a/drivers/net/pcap/rte_eth_pcap.c b/drivers/net/pcap/rte_eth_= pcap.c* > > *index b341f93..7125823 100644* > > *--- a/drivers/net/pcap/rte_eth_pcap.c* > > *+++ b/drivers/net/pcap/rte_eth_pcap.c* > > *@@ -1090,6 +1090,6 @@* static struct rte_driver pmd_pcap_drv =3D { > > .uninit =3D rte_pmd_pcap_devuninit, > > }; > > -PMD_REGISTER_DRIVER(pmd_pcap_drv, pcap); > > -DRIVER_REGISTER_PARAM_STRING(pcap, "rx_pcap=3D tx_pcap=3D " > > +PMD_REGISTER_DRIVER(pmd_pcap_drv, eth_pcap); > > +DRIVER_REGISTER_PARAM_STRING(eth_pcap, "rx_pcap=3D tx_pcap=3D " > > > > > > Please check these 2 items and make the necessary changes and let me know > how do you proceed. > > > > Thanks, > > Reshma > > > > *From:* Pattan, Reshma > *Sent:* Monday, July 25, 2016 5:01 PM > *To:* 'Nishant Verma' > *Cc:* users@dpdk.org > *Subject:* RE: pdump help > > > > Hi, > > > Can you paste me file config/common_base content output > > > > Thanks, > > Reshma > > > > *From:* Nishant Verma [mailto:vnish11@gmail.com ] > *Sent:* Monday, July 25, 2016 4:58 PM > > *To:* Pattan, Reshma > *Cc:* users@dpdk.org > *Subject:* Re: pdump help > > > > Hi Reshma, > > Error cause is still same, but i think their is some progress what i see > in error log as of now. > > Don't know what exact ican share that will help you in debug the issue, s= o > as of now sharing HugePage output, l3fwd log & pdump error log. > > If you need anything else, please let me know. > > > Option: 29 > > AnonHugePages: 2048 kB > HugePages_Total: 8192 > HugePages_Free: 7680 > HugePages_Rsvd: 0 > HugePages_Surp: 0 > Hugepagesize: 2048 kB > > > > > -- > > root@ubuntu:/home/oneweb/dpdk/examples/l3fwd/build/app# *./l3fwd -c 606 > -n 4 --proc-type=3Dprimary --socket-mem=3D1024 --file-prefix l3f -- -p 0= x1 > --config=3D"(0,0,1),(0,1,2)"* > EAL: Detected 16 lcore(s) > EAL: Probing VFIO support... > EAL: VFIO support initialized > PMD: bnxt_rte_pmd_init() called for (null) > EAL: PCI device 0000:03:00.0 on NUMA socket 0 > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > EAL: PCI device 0000:03:00.1 on NUMA socket 0 > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > EAL: PCI device 0000:05:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1521 rte_igb_pmd > EAL: PCI device 0000:05:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1521 rte_igb_pmd > L3FWD: LPM or EM none selected, default LPM on > Initializing port 0 ... Creating queues: nb_rxq=3D2 nb_txq=3D4... > Address:0C:C4:7A:73:EF:14, Destination:02:00:00:00:00:00, Allocated mbuf > pool on socket 0 > LPM: Adding route 0x01010100 / 24 (0) > LPM: Adding route IPV6 / 48 (0) > *=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3DInitialized PDUMP* > txq=3D1,0,0 txq=3D2,1,0 txq=3D9,2,0 txq=3D10,3,0 > > Skipping disabled port 1 > > Initializing rx queues on lcore 1 ... rxq=3D0,0,0 > Initializing rx queues on lcore 2 ... rxq=3D0,1,0 > Initializing rx queues on lcore 9 ... > Initializing rx queues on lcore 10 ... > > > Checking link status..................................................don= e > Port 0 Link Up - speed 10000 Mbps - full-duplex > L3FWD: entering main loop on lcore 2 > L3FWD: -- lcoreid=3D2 portid=3D0 rxqueueid=3D1 > L3FWD: lcore 9 has nothing to do > L3FWD: entering main loop on lcore 1 > L3FWD: -- lcoreid=3D1 portid=3D0 rxqueueid=3D0 > L3FWD: lcore 10 has nothing to do > > ------- > > > > root@ubuntu:/home/oneweb/dpdk/app/pdump# *./dpdk_pdump --file-prefix l3f > -- --pdump > 'port=3D0,queue=3D*,rx-dev=3D/tmp/rx-file.pcap,tx-dev=3D/tmp/tx-file.pcap= ,ring-size=3D1024,mbuf-size=3D20,total-num-mbufs=3D1025'* > EAL: Detected 16 lcore(s) > EAL: Probing VFIO support... > EAL: VFIO support initialized > EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the > kernel. > EAL: This may cause issues with mapping memory into secondary processe= s > PMD: bnxt_rte_pmd_init() called for (null) > EAL: PCI device 0000:03:00.0 on NUMA socket 0 > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > EAL: PCI device 0000:03:00.1 on NUMA socket 0 > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > PMD: eth_ixgbe_dev_init(): No TX queues configured yet. Using default TX > function. > EAL: PCI device 0000:05:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1521 rte_igb_pmd > EAL: PCI device 0000:05:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1521 rte_igb_pmd > EAL: no driver found for eth_pcap_rx_0 > EAL: Driver, cannot attach the device > *EAL: Error - exiting with code: 1* > Cause: vdev creation failed:create_mp_ring_vdev:669 > > rgds, > > Nishant > > > > On Mon, Jul 25, 2016 at 4:57 AM, Pattan, Reshma > wrote: > > Hi Nishant, > > > > 1)Since you are using *--file-prefix l3f* in l3fwd command, you need to > use same file prefix in dpdk_pdump command also. This solves below report= ed > issue. > > > > 2)And also make sure l3fwd application initializes packet capture > framework by calling rte_pdump_init () api from its main(). > > Also should call uninitialize api rte_pdump_uninit() before exiting > l3fwd application. Please refer app/test-pmd/testpmd.c file to see how > these apis are used. > > > > Ex: > > int > > main(int argc, char** argv) > > { > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7int diag; > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7uint8_t port_id; > > > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7signal(SIGINT, signal_han= dler); > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7signal(SIGTERM, signal_ha= ndler); > > > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7diag =3D rte_eal_init(arg= c, argv); > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7if (diag < 0) > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=BB=C2=B7=C2=B7=C2=B7= =C2=B7=C2=B7=C2=B7=C2=B7rte_panic("Cannot init EAL\n"); > > *#ifdef RTE_LIBRTE_PDUMP* > > *=C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7/* initialize packet cap= ture framework */* > > *=C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7rte_pdump_init(NULL);* > > > > static void > > signal_handler(int signum) > > { > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7if (signum =3D=3D SIGINT = || signum =3D=3D SIGTERM) { > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=BB=C2=B7=C2=B7=C2=B7= =C2=B7=C2=B7=C2=B7=C2=B7printf("\nSignal %d received, preparing to exit...\= n", > > =C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=BB=C2=B7=C2=B7=C2=B7= =C2=B7=C2=B7=C2=B7=C2=B7=C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2= =BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7signum); > > *#ifdef RTE_LIBRTE_PDUMP* > > *=C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=BB=C2=B7=C2=B7=C2=B7= =C2=B7=C2=B7=C2=B7=C2=B7/* uninitialize packet capture framework */* > > *=C2=BB=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=BB=C2=B7=C2=B7=C2=B7= =C2=B7=C2=B7=C2=B7=C2=B7rte_pdump_uninit();* > > #endif > > > > 3)As of now initializing and un initializing of the packet capture > framework is done only in testpmd, for other applications this is not don= e. > We left users to do this for now. > > > > > > Please feel free to ping me if you see some more issues. > > > > Thanks, > > Reshma > > *From:* Nishant Verma [mailto:vnish11@gmail.com] > *Sent:* Friday, July 22, 2016 10:42 PM > > > *To:* Pattan, Reshma > *Cc:* users@dpdk.org > *Subject:* Re: pdump help > > > > Hi, > > Something is still creating the problem. just can't figure out. > > Here is the scenario.... > > Just inserted IGB UIO module, attached one 10G NIC to DPDK & > > 4096 hugepage. > > > --- > > trying to run l3fwd as primary and pducp as secondary to capture packet > dump. > > Earlier dpdk_pdump is crashing on either create_mp_ring_vdev:649 or > create_mp_ring_vdev:669. > > Now i changed some parameters of pdump and l3fwd, change hugepages to 819= 2 > and tried to run like this.. > *./l3fwd -c 606 -n 4 --proc-type=3Dprimary --socket-mem=3D1024 --file-pr= efix > l3f -- -p 0x1 --config=3D"(0,0,1),(0,1,2)"* > > Here is the log of app > " > EAL: Detected 16 lcore(s) > EAL: Probing VFIO support... > EAL: VFIO support initialized > PMD: bnxt_rte_pmd_init() called for (null) > EAL: PCI device 0000:03:00.0 on NUMA socket 0 > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > EAL: PCI device 0000:03:00.1 on NUMA socket 0 > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > EAL: PCI device 0000:05:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1521 rte_igb_pmd > EAL: PCI device 0000:05:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1521 rte_igb_pmd > L3FWD: LPM or EM none selected, default LPM on > Initializing port 0 ... Creating queues: nb_rxq=3D2 nb_txq=3D4... > Address:0C:C4:7A:73:EF:14, Destination:02:00:00:00:00:00, Allocated mbuf > pool on socket 0 > LPM: Adding route 0x01010100 / 24 (0) > LPM: Adding route IPV6 / 48 (0) > txq=3D1,0,0 txq=3D2,1,0 txq=3D9,2,0 txq=3D10,3,0 > > Skipping disabled port 1 > > Initializing rx queues on lcore 1 ... rxq=3D0,0,0 > Initializing rx queues on lcore 2 ... rxq=3D0,1,0 > Initializing rx queues on lcore 9 ... > Initializing rx queues on lcore 10 ... > > " > > It seems everything is good in this. So I tried to run pdump like > > * ./dpdk_pdump -- --pdump > 'port=3D0,queue=3D*,rx-dev=3D/tmp/rx-file.pcap,tx-dev=3D/tmp/tx-file.pcap= ,ring-size=3D1024,mbuf-size=3D20,total-num-mbufs=3D1025'* > > Here is log for pdump > > " > EAL: Detected 16 lcore(s) > EAL: Probing VFIO support... > EAL: cannot connect to primary process! > EAL: VFIO support could not be initialized > EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the > kernel. > EAL: This may cause issues with mapping memory into secondary processe= s > EAL: Could not open /dev/hugepages/rtemap_510 > PANIC in rte_eal_init(): > Cannot init memory > 6: [./dpdk_pdump(_start+0x29) [0x4289b9]] > 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) > [0x7fa22219aa40]] > 4: [./dpdk_pdump(main+0x155) [0x42c417]] > 3: [./dpdk_pdump(rte_eal_init+0xf14) [0x4603b4]] > 2: [./dpdk_pdump(__rte_panic+0xc9) [0x424b59]] > 1: [./dpdk_pdump(rte_dump_stack+0x2b) [0x4677fb]] > Aborted (core dumped) > > " > > > > It seems from log that their is some issue in memory between primary and > secondary, but when i tried to run one l2fwd as primary and one l3fwd as > secondary it works fine. > > > > On Fri, Jul 22, 2016 at 7:21 AM, Pattan, Reshma > wrote: > > Hi, > > > > I see some cleanup related bug in the dpdk_pdump tool, so until I publish > fix for that, > > You need to restart both primary and secondary process( work around) > after you see any RING/VDEV failure issues. > > > > Thanks, > > Reshma > > > > > > *From:* Pattan, Reshma > *Sent:* Friday, July 22, 2016 10:31 AM > *To:* 'Nishant Verma' > *Cc:* users@dpdk.org > *Subject:* RE: pdump help > > > > Hi, > > > > As I see =E2=80=9CRING: Cannot reserve memory=E2=80=9D. Please allocate e= nough huge page > memory and see what happens. > > > > Also once you encounter such error please restart both primary and > secondary process. > > > > Please paste me the full error log, if you still face the issue. > > > > Thanks, > > Reshma > > > > > > *From:* Nishant Verma [mailto:vnish11@gmail.com ] > *Sent:* Thursday, July 21, 2016 9:10 PM > *To:* Pattan, Reshma > *Cc:* users@dpdk.org > *Subject:* Re: pdump help > > > > Hi Reshma, > > > > Tried things pointed by you(libpcap Installed & config parameter is set). > > But still things are not working. > > > > " > > root@ubuntu:/home/oneweb/dpdk/app/pdump# ./dpdk_pdump > --proc-type=3Dsecondary -- --pdump > 'device_id=3D03:00.0,queue=3D*,rx-dev=3D/tmp/rx-file.pcap,tx-dev=3D/tmp/t= x-file.pcap' > > EAL: Detected 16 lcore(s) > > EAL: Probing VFIO support... > > EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the > kernel. > > EAL: This may cause issues with mapping memory into secondary processe= s > > PMD: bnxt_rte_pmd_init() called for (null) > > EAL: PCI device 0000:03:00.0 on NUMA socket 0 > > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > > EAL: PCI device 0000:03:00.1 on NUMA socket 0 > > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > > PMD: eth_ixgbe_dev_init(): No TX queues configured yet. Using default TX > function. > > EAL: PCI device 0000:05:00.0 on NUMA socket 0 > > EAL: probe driver: 8086:1521 rte_igb_pmd > > EAL: PCI device 0000:05:00.1 on NUMA socket 0 > > EAL: probe driver: 8086:1521 rte_igb_pmd > > RING: Cannot reserve memory > > EAL: Error - exiting with code: 1 > > Cause: File exists:create_mp_ring_vdev:649 > > " > > > > > > Rgds, > > Nishant > > > > > > On Thu, Jul 21, 2016 at 5:16 AM, Pattan, Reshma > wrote: > > Hi, > > > > Pdump tool is designed based on PCAP PMD. So you need to install libpcap > package and set CONFIG_RTE_LIBRTE_PMD_PCAP flag to =E2=80=9Cy=E2=80=9D > > in config/common_base file and recompile the DPDK and run pdump tool. > Please let me know if that fix the issue. > > > > This dependency is mentioned in the document > *=E2=80=9Cdoc/guides/sample_app_ug/pdump.rst.=E2=80=9D* > > > > Thanks, > > Reshma > > > > *From:* Nishant Verma [mailto:vnish11@gmail.com] > *Sent:* Wednesday, July 20, 2016 8:08 PM > *To:* Pattan, Reshma > *Subject:* pdump help > > > > Hi Reshma, > > > > i am facing some issue in executing pdump. I have seen in logs that you > recently updated the code. Please let me know if i am doing anything wron= g. > > > > > > *app/pdump# ./dpdk_pdump -- --pdump > 'device_id=3D03:00.0,queue=3D*,rx-dev=3D/tmp/rx-1-file.pcap,tx-dev=3Dtx-1= -file.pcap'* > > > > This is the error i am getting. > > *Cause: File exists:create_mp_ring_vdev:649* > > > > =E2=80=8BThanks a lot.=E2=80=8B > > > > -- > > Rgds, > > Nishant > > > > > > > > > > > > -- > > Rgds, > > Nishant > > > > > > > > > > > -- > > Rgds, > > Nishant > > > > > > > > > > > -- > > Rgds, > > Nishant > > > > > > > --=20 Rgds, Nishant