DPDK usage discussions
 help / color / Atom feed
* [dpdk-users] DPDK PDUMP Issue
@ 2020-07-14  8:40 Dikshant Chitkara
  2020-07-14 16:29 ` [dpdk-users] [dpdk-dev] " Stephen Hemminger
  0 siblings, 1 reply; 14+ messages in thread
From: Dikshant Chitkara @ 2020-07-14  8:40 UTC (permalink / raw)
  To: users, dev; +Cc: Amir Ilan, Veeresh Patil

Hi Team,

We are facing an issue w.r.t to using DPDK PDUMP utility and want to check if you can help us in this regard.

This issue is specific to DPDK 19.05 version or may  be newer versions and was not found on DPDK 18.08 version.

The issue is that when we built DPDK in shared library mode and try to run PDUMP we get following error on PDUMP console:

EAL: Failed to hotplug add device
EAL: Error - exiting with code: 1
  Cause: vdev creation failed

On Debugging above error message, I found that inside rte_dev_probe() function in the file  lib/librte_eal/common/eal_common_dev.c , req.result = -14 which is non-zero value and points to enum EFAULT (Bad address) value, thus leading to above error.

However, when I ran PDUMP in DPDK 18.08, I did not observe any such issue and it worked fine.

DPDK was built with following flags set in config/common_base file:

CONFIG_RTE_LIBRTE_PMD_PCAP=y
CONFIG_RTE_LIBRTE_PDUMP=y

I ran PDUMP with testpmd as primary application and was trying to send some traffic on the Ethernet dpdk port using testpmd and capture it using pdump.

Attached are the logs for both testpmd and pdump in both DPDK19_05 and DPDK_18_08 version for your reference.

Let us know if you can help in this regard.

Thanks,
Dikshant

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pdump_18_08.txt
URL: <http://mails.dpdk.org/archives/users/attachments/20200714/88363eb9/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: testpmd_18_08.txt
URL: <http://mails.dpdk.org/archives/users/attachments/20200714/88363eb9/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pdump_19_05.txt
URL: <http://mails.dpdk.org/archives/users/attachments/20200714/88363eb9/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: testpmd_19_05.txt
URL: <http://mails.dpdk.org/archives/users/attachments/20200714/88363eb9/attachment-0003.txt>

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-14  8:40 [dpdk-users] DPDK PDUMP Issue Dikshant Chitkara
@ 2020-07-14 16:29 ` " Stephen Hemminger
  2020-07-22  4:08   ` Varghese, Vipin
  0 siblings, 1 reply; 14+ messages in thread
From: Stephen Hemminger @ 2020-07-14 16:29 UTC (permalink / raw)
  To: Dikshant Chitkara; +Cc: users, dev, Amir Ilan, Veeresh Patil

On Tue, 14 Jul 2020 08:40:55 +0000
Dikshant Chitkara <dchitkara@Airspan.com> wrote:

> Hi Team,
> 
> We are facing an issue w.r.t to using DPDK PDUMP utility and want to check if you can help us in this regard.
> 
> This issue is specific to DPDK 19.05 version or may  be newer versions and was not found on DPDK 18.08 version.
> 
> The issue is that when we built DPDK in shared library mode and try to run PDUMP we get following error on PDUMP console:
> 
> EAL: Failed to hotplug add device
> EAL: Error - exiting with code: 1
>   Cause: vdev creation failed
> 
> On Debugging above error message, I found that inside rte_dev_probe() function in the file  lib/librte_eal/common/eal_common_dev.c , req.result = -14 which is non-zero value and points to enum EFAULT (Bad address) value, thus leading to above error.
> 
> However, when I ran PDUMP in DPDK 18.08, I did not observe any such issue and it worked fine.
> 
> DPDK was built with following flags set in config/common_base file:
> 
> CONFIG_RTE_LIBRTE_PMD_PCAP=y
> CONFIG_RTE_LIBRTE_PDUMP=y
> 
> I ran PDUMP with testpmd as primary application and was trying to send some traffic on the Ethernet dpdk port using testpmd and capture it using pdump.
> 
> Attached are the logs for both testpmd and pdump in both DPDK19_05 and DPDK_18_08 version for your reference.
> 
> Let us know if you can help in this regard.
> 
> Thanks,
> Dikshant
> 

Pdump runs as secondary process, what is your primary process.
Is the secondary process using the same exact versions of DPDK and libraries as the primary process?
The secondary process needs access to the same devices and drivers as the primary process to work.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-14 16:29 ` [dpdk-users] [dpdk-dev] " Stephen Hemminger
@ 2020-07-22  4:08   ` Varghese, Vipin
  2020-07-28 14:51     ` Dikshant Chitkara
  0 siblings, 1 reply; 14+ messages in thread
From: Varghese, Vipin @ 2020-07-22  4:08 UTC (permalink / raw)
  To: Stephen Hemminger, Dikshant Chitkara; +Cc: users, dev, Amir Ilan, Veeresh Patil

Snipped

> Dikshant Chitkara <dchitkara@Airspan.com> wrote:
> 
> > Hi Team,
> >
> > We are facing an issue w.r.t to using DPDK PDUMP utility and want to check if
> you can help us in this regard.
> >
> > This issue is specific to DPDK 19.05 version or may  be newer versions and
> was not found on DPDK 18.08 version.
> >
> > The issue is that when we built DPDK in shared library mode and try to run
> PDUMP we get following error on PDUMP console:
> >
> > EAL: Failed to hotplug add device
> > EAL: Error - exiting with code: 1
> >   Cause: vdev creation failed
> >
> > On Debugging above error message, I found that inside rte_dev_probe()
> function in the file  lib/librte_eal/common/eal_common_dev.c , req.result = -
> 14 which is non-zero value and points to enum EFAULT (Bad address) value,
> thus leading to above error.
> >
> > However, when I ran PDUMP in DPDK 18.08, I did not observe any such issue
> and it worked fine.
> >
> > DPDK was built with following flags set in config/common_base file:
> >
> > CONFIG_RTE_LIBRTE_PMD_PCAP=y
> > CONFIG_RTE_LIBRTE_PDUMP=y
> >
> > I ran PDUMP with testpmd as primary application and was trying to send
> some traffic on the Ethernet dpdk port using testpmd and capture it using
> pdump.
> >
> > Attached are the logs for both testpmd and pdump in both DPDK19_05 and
> DPDK_18_08 version for your reference.
> >
> > Let us know if you can help in this regard.
> >
> > Thanks,
> > Dikshant
> >
> 
> Pdump runs as secondary process, what is your primary process.
> Is the secondary process using the same exact versions of DPDK and libraries as
> the primary process?
> The secondary process needs access to the same devices and drivers as the
> primary process to work.

Based on the log files shared, I have made assumptions as

1. Primary: testpmd
2. DPDK version: 19.05
3. SHARED LIB in .config: yes
4. export LD_LIBRARY_PATH: yes

Using arguments passed in primary, I faced error
```
EAL: Error - exiting with code: 1
  Cause: Creation of mbuf pool for socket 0 failed: Invalid argument

  Cause: Mempool creation failed: Invalid argument
```

Hence had to modify with ` -d librte_mempool_ring.so`.  Using arguments passed in secondary, I faced similar error too. 

With these corrections, I am able to get similar error shared as
```
EAL: failed to parse device "vdev:net_pcap_tx_0"
EAL: Failed to hotplug add device on primary
EAL: Error - exiting with code: 1
  Cause: vdev creation failed
```

Checking the testpmd Makefile, it is narrowed down to missing PCAP_PMD build factor. I rebuild testpmd with ` LD_FLAGS="-lrte_pmd_pcap" make` and re-ran the same. With this I can get it working properly. 

Ideally there should had been an entry in Makefile as 
```
ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y)
LDLIBS += -lrte_pmd_pcap
endif
```

reference: This is similar to the error and solution provided in ` https://stackoverflow.com/questions/62795017/dpdk-pdump-failed-to-hotplug-add-device/62869287#62869287`



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-22  4:08   ` Varghese, Vipin
@ 2020-07-28 14:51     ` Dikshant Chitkara
  2020-07-28 16:23       ` Stephen Hemminger
  2020-07-29  0:59       ` Varghese, Vipin
  0 siblings, 2 replies; 14+ messages in thread
From: Dikshant Chitkara @ 2020-07-28 14:51 UTC (permalink / raw)
  To: Varghese, Vipin, Stephen Hemminger; +Cc: users, dev, Amir Ilan, Veeresh Patil

Hi Team,

With fix suggest in prev mail thread at testpmd side, PDUMP works with testpmd.

However when we try to run our own primary app with PDUMP as a secondary process, PDUMP console comes up, however it does not capture any packets.

Changes made at primary app side:
1. PDUMP initialised just after rte eal init:

  ret_pdump = rte_pdump_init();
       if (ret_pdump < 0) {
               printf("rte_pdump_init failed\n");
       }
       else
       {
               printf("rte_pdump_init success\n");
       }

2. Makefile modified to add all relevant files to be linked:

LIB_SO     =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool -lrte_cryptodev -lrte_ethdev -lrte_mbuf -lrte_mempool_ring  -lrte_member  -lrte_eventdev  -lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline  -lrte_table  -lrte_timer  -lrte_hash  -lrte_jobstats  -lrte_lpm  -lrte_power  -lrte_acl  -lrte_meter  -lrte_sch

Even tried to link final DPDK lib so as well:
LIB_SO     =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-archive -L/usr/lib/x86_64-linux-gnu/ -fPIC

It seems both apps are able to connect over mp socket but pdump unable to capture data sent from primary app.

Can you tell us what else we might be missing here.

Note: We are using DPDK 19_05 built in shared lib mode.


Primary app console:

EAL: Probing VFIO support...
EAL: PCI device 0000:41:00.0 on NUMA socket 0
EAL:   probe driver: 8086:37d2 net_i40e
EAL: PCI device 0000:41:00.1 on NUMA socket 0
EAL:   probe driver: 8086:37d2 net_i40e
EAL: PCI device 0000:86:00.0 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.1 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.2 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.3 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:88:00.0 on NUMA socket 1
EAL:   probe driver: 8086:158b net_i40e
EAL: PCI device 0000:88:00.1 on NUMA socket 1
EAL:   probe driver: 8086:158b net_i40e
rte_pdump_init success
pool_create successed
DPDK TX Ethernet device (destination) opened successfully
Before send burst
Packets sent. Count=32
Before send burst
Packets sent. Count=32
Before send burst
Packets sent. Count=32
Before send burst
Packets sent. Count=32
Before send burst
Packets sent. Count=32
Before send burst
Packets sent. Count=32
Before send burst
Packets sent. Count=32
>>>

Pdump console:

[root@flexran3 x86_64-native-linux-icc]# ./app/dpdk-pdump -d librte_pmd_i40e.so -d librte_pmd_pcap.so -- --pdump 'port=0,queue=*,tx-dev=/home/dchitkara/capture.pcap'
EAL: Detected 80 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_45398_5ed780258ea46
EAL: Probing VFIO support...
EAL: PCI device 0000:41:00.0 on NUMA socket 0
EAL:   probe driver: 8086:37d2 net_i40e
EAL: PCI device 0000:41:00.1 on NUMA socket 0
EAL:   probe driver: 8086:37d2 net_i40e
EAL: PCI device 0000:86:00.0 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.1 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.2 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.3 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:88:00.0 on NUMA socket 1
EAL:   probe driver: 8086:158b net_i40e
EAL: PCI device 0000:88:00.1 on NUMA socket 1
EAL:   probe driver: 8086:158b net_i40e
Port 1 MAC: 02 70 63 61 70 00
 core (0), capture for (1) tuples
 - port 0 device ((null)) queue 65535
^C

Signal 2 received, preparing to exit...
##### PDUMP DEBUG STATS #####
 -packets dequeued:                     0
 -packets transmitted to vdev:          0
 -packets freed:                        0
[root@flexran3 x86_64-native-linux-icc]#




-----Original Message-----
From: Varghese, Vipin <vipin.varghese@intel.com> 
Sent: 22 July 2020 09:38
To: Stephen Hemminger <stephen@networkplumber.org>; Dikshant Chitkara <dchitkara@Airspan.com>
Cc: users@dpdk.org; dev@dpdk.org; Amir Ilan <ailan@Airspan.com>; Veeresh Patil <vpatil@Airspan.com>
Subject: RE: [dpdk-dev] DPDK PDUMP Issue

NOT FROM AIRSPAN - Caution - External from: vipin.varghese@intel.com Snipped

> Dikshant Chitkara <dchitkara@Airspan.com> wrote:
> 
> > Hi Team,
> >
> > We are facing an issue w.r.t to using DPDK PDUMP utility and want to 
> > check if
> you can help us in this regard.
> >
> > This issue is specific to DPDK 19.05 version or may  be newer 
> > versions and
> was not found on DPDK 18.08 version.
> >
> > The issue is that when we built DPDK in shared library mode and try 
> > to run
> PDUMP we get following error on PDUMP console:
> >
> > EAL: Failed to hotplug add device
> > EAL: Error - exiting with code: 1
> >   Cause: vdev creation failed
> >
> > On Debugging above error message, I found that inside 
> > rte_dev_probe()
> function in the file  lib/librte_eal/common/eal_common_dev.c , 
> req.result = -
> 14 which is non-zero value and points to enum EFAULT (Bad address) 
> value, thus leading to above error.
> >
> > However, when I ran PDUMP in DPDK 18.08, I did not observe any such 
> > issue
> and it worked fine.
> >
> > DPDK was built with following flags set in config/common_base file:
> >
> > CONFIG_RTE_LIBRTE_PMD_PCAP=y
> > CONFIG_RTE_LIBRTE_PDUMP=y
> >
> > I ran PDUMP with testpmd as primary application and was trying to 
> > send
> some traffic on the Ethernet dpdk port using testpmd and capture it 
> using pdump.
> >
> > Attached are the logs for both testpmd and pdump in both DPDK19_05 
> > and
> DPDK_18_08 version for your reference.
> >
> > Let us know if you can help in this regard.
> >
> > Thanks,
> > Dikshant
> >
> 
> Pdump runs as secondary process, what is your primary process.
> Is the secondary process using the same exact versions of DPDK and 
> libraries as the primary process?
> The secondary process needs access to the same devices and drivers as 
> the primary process to work.

Based on the log files shared, I have made assumptions as

1. Primary: testpmd
2. DPDK version: 19.05
3. SHARED LIB in .config: yes
4. export LD_LIBRARY_PATH: yes

Using arguments passed in primary, I faced error ```
EAL: Error - exiting with code: 1
  Cause: Creation of mbuf pool for socket 0 failed: Invalid argument

  Cause: Mempool creation failed: Invalid argument ```

Hence had to modify with ` -d librte_mempool_ring.so`.  Using arguments passed in secondary, I faced similar error too. 

With these corrections, I am able to get similar error shared as ```
EAL: failed to parse device "vdev:net_pcap_tx_0"
EAL: Failed to hotplug add device on primary
EAL: Error - exiting with code: 1
  Cause: vdev creation failed
```

Checking the testpmd Makefile, it is narrowed down to missing PCAP_PMD build factor. I rebuild testpmd with ` LD_FLAGS="-lrte_pmd_pcap" make` and re-ran the same. With this I can get it working properly. 

Ideally there should had been an entry in Makefile as ``` ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y) LDLIBS += -lrte_pmd_pcap endif ```

reference: This is similar to the error and solution provided in ` https://stackoverflow.com/questions/62795017/dpdk-pdump-failed-to-hotplug-add-device/62869287#62869287`



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-28 14:51     ` Dikshant Chitkara
@ 2020-07-28 16:23       ` Stephen Hemminger
  2020-07-28 16:41         ` Dikshant Chitkara
  2020-07-29  0:59       ` Varghese, Vipin
  1 sibling, 1 reply; 14+ messages in thread
From: Stephen Hemminger @ 2020-07-28 16:23 UTC (permalink / raw)
  To: Dikshant Chitkara; +Cc: Varghese, Vipin, users, dev, Amir Ilan, Veeresh Patil

On Tue, 28 Jul 2020 14:51:58 +0000
Dikshant Chitkara <dchitkara@Airspan.com> wrote:

> Hi Team,
> 
> With fix suggest in prev mail thread at testpmd side, PDUMP works with testpmd.
> 
> However when we try to run our own primary app with PDUMP as a secondary process, PDUMP console comes up, however it does not capture any packets.
> 
> Changes made at primary app side:
> 1. PDUMP initialised just after rte eal init:
> 
>   ret_pdump = rte_pdump_init();
>        if (ret_pdump < 0) {
>                printf("rte_pdump_init failed\n");
>        }
>        else
>        {
>                printf("rte_pdump_init success\n");
>        }
> 
> 2. Makefile modified to add all relevant files to be linked:
> 
> LIB_SO     =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool -lrte_cryptodev -lrte_ethdev -lrte_mbuf -lrte_mempool_ring  -lrte_member  -lrte_eventdev  -lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline  -lrte_table  -lrte_timer  -lrte_hash  -lrte_jobstats  -lrte_lpm  -lrte_power  -lrte_acl  -lrte_meter  -lrte_sch
> 
> Even tried to link final DPDK lib so as well:
> LIB_SO     =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-archive -L/usr/lib/x86_64-linux-gnu/ -fPIC
> 
> It seems both apps are able to connect over mp socket but pdump unable to capture data sent from primary app.
> 
> Can you tell us what else we might be missing here.
> 
> Note: We are using DPDK 19_05 built in shared lib mode.
> 
> 
> Primary app console:
> 
> EAL: Probing VFIO support...
> EAL: PCI device 0000:41:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:37d2 net_i40e
> EAL: PCI device 0000:41:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:37d2 net_i40e
> EAL: PCI device 0000:86:00.0 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.1 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.2 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.3 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:88:00.0 on NUMA socket 1
> EAL:   probe driver: 8086:158b net_i40e
> EAL: PCI device 0000:88:00.1 on NUMA socket 1
> EAL:   probe driver: 8086:158b net_i40e
> rte_pdump_init success
> pool_create successed
> DPDK TX Ethernet device (destination) opened successfully
> Before send burst
> Packets sent. Count=32
> Before send burst
> Packets sent. Count=32
> Before send burst
> Packets sent. Count=32
> Before send burst
> Packets sent. Count=32
> Before send burst
> Packets sent. Count=32
> Before send burst
> Packets sent. Count=32
> Before send burst
> Packets sent. Count=32
> >>>  
> 
> Pdump console:
> 
> [root@flexran3 x86_64-native-linux-icc]# ./app/dpdk-pdump -d librte_pmd_i40e.so -d librte_pmd_pcap.so -- --pdump 'port=0,queue=*,tx-dev=/home/dchitkara/capture.pcap'
> EAL: Detected 80 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_45398_5ed780258ea46
> EAL: Probing VFIO support...
> EAL: PCI device 0000:41:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:37d2 net_i40e
> EAL: PCI device 0000:41:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:37d2 net_i40e
> EAL: PCI device 0000:86:00.0 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.1 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.2 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.3 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:88:00.0 on NUMA socket 1
> EAL:   probe driver: 8086:158b net_i40e
> EAL: PCI device 0000:88:00.1 on NUMA socket 1
> EAL:   probe driver: 8086:158b net_i40e
> Port 1 MAC: 02 70 63 61 70 00
>  core (0), capture for (1) tuples
>  - port 0 device ((null)) queue 65535
> ^C
> 
> Signal 2 received, preparing to exit...
> ##### PDUMP DEBUG STATS #####
>  -packets dequeued:                     0
>  -packets transmitted to vdev:          0
>  -packets freed:                        0
> [root@flexran3 x86_64-native-linux-icc]#
> 
> 
> 
> 
> -----Original Message-----
> From: Varghese, Vipin <vipin.varghese@intel.com> 
> Sent: 22 July 2020 09:38
> To: Stephen Hemminger <stephen@networkplumber.org>; Dikshant Chitkara <dchitkara@Airspan.com>
> Cc: users@dpdk.org; dev@dpdk.org; Amir Ilan <ailan@Airspan.com>; Veeresh Patil <vpatil@Airspan.com>
> Subject: RE: [dpdk-dev] DPDK PDUMP Issue
> 
> NOT FROM AIRSPAN - Caution - External from: vipin.varghese@intel.com Snipped
> 
> > Dikshant Chitkara <dchitkara@Airspan.com> wrote:
> >   
> > > Hi Team,
> > >
> > > We are facing an issue w.r.t to using DPDK PDUMP utility and want to 
> > > check if  
> > you can help us in this regard.  
> > >
> > > This issue is specific to DPDK 19.05 version or may  be newer 
> > > versions and  
> > was not found on DPDK 18.08 version.  
> > >
> > > The issue is that when we built DPDK in shared library mode and try 
> > > to run  
> > PDUMP we get following error on PDUMP console:  
> > >
> > > EAL: Failed to hotplug add device
> > > EAL: Error - exiting with code: 1
> > >   Cause: vdev creation failed
> > >
> > > On Debugging above error message, I found that inside 
> > > rte_dev_probe()  
> > function in the file  lib/librte_eal/common/eal_common_dev.c , 
> > req.result = -
> > 14 which is non-zero value and points to enum EFAULT (Bad address) 
> > value, thus leading to above error.  
> > >
> > > However, when I ran PDUMP in DPDK 18.08, I did not observe any such 
> > > issue  
> > and it worked fine.  
> > >
> > > DPDK was built with following flags set in config/common_base file:
> > >
> > > CONFIG_RTE_LIBRTE_PMD_PCAP=y
> > > CONFIG_RTE_LIBRTE_PDUMP=y
> > >
> > > I ran PDUMP with testpmd as primary application and was trying to 
> > > send  
> > some traffic on the Ethernet dpdk port using testpmd and capture it 
> > using pdump.  
> > >
> > > Attached are the logs for both testpmd and pdump in both DPDK19_05 
> > > and  
> > DPDK_18_08 version for your reference.  
> > >
> > > Let us know if you can help in this regard.
> > >
> > > Thanks,
> > > Dikshant
> > >  
> > 
> > Pdump runs as secondary process, what is your primary process.
> > Is the secondary process using the same exact versions of DPDK and 
> > libraries as the primary process?
> > The secondary process needs access to the same devices and drivers as 
> > the primary process to work.  
> 
> Based on the log files shared, I have made assumptions as
> 
> 1. Primary: testpmd
> 2. DPDK version: 19.05
> 3. SHARED LIB in .config: yes
> 4. export LD_LIBRARY_PATH: yes
> 
> Using arguments passed in primary, I faced error ```
> EAL: Error - exiting with code: 1
>   Cause: Creation of mbuf pool for socket 0 failed: Invalid argument
> 
>   Cause: Mempool creation failed: Invalid argument ```
> 
> Hence had to modify with ` -d librte_mempool_ring.so`.  Using arguments passed in secondary, I faced similar error too. 
> 
> With these corrections, I am able to get similar error shared as ```
> EAL: failed to parse device "vdev:net_pcap_tx_0"
> EAL: Failed to hotplug add device on primary
> EAL: Error - exiting with code: 1
>   Cause: vdev creation failed
> ```
> 
> Checking the testpmd Makefile, it is narrowed down to missing PCAP_PMD build factor. I rebuild testpmd with ` LD_FLAGS="-lrte_pmd_pcap" make` and re-ran the same. With this I can get it working properly. 
> 
> Ideally there should had been an entry in Makefile as ``` ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y) LDLIBS += -lrte_pmd_pcap endif ```
> 
> reference: This is similar to the error and solution provided in ` https://stackoverflow.com/questions/62795017/dpdk-pdump-failed-to-hotplug-add-device/62869287#62869287`
> 
> 

The primary/secondary work is that both processes have to discover the same memory areas
and devices.

The NUMA thing might be related, does your system have multiple cpu sockets.
What does the cpu_layout python script show.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-28 16:23       ` Stephen Hemminger
@ 2020-07-28 16:41         ` Dikshant Chitkara
  2020-07-28 17:03           ` Stephen Hemminger
  0 siblings, 1 reply; 14+ messages in thread
From: Dikshant Chitkara @ 2020-07-28 16:41 UTC (permalink / raw)
  To: Stephen Hemminger; +Cc: Varghese, Vipin, users, dev, Amir Ilan, Veeresh Patil

Hi Stephen,
Our system has 2 sockets as seen from below :

[root@flexran3 dchitkara]# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                80
On-line CPU(s) list:   0-79
Thread(s) per core:    2
Core(s) per socket:    20
Socket(s):             2
NUMA node(s):          2

-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org> 
Sent: 28 July 2020 21:54
To: Dikshant Chitkara <dchitkara@Airspan.com>
Cc: Varghese, Vipin <vipin.varghese@intel.com>; users@dpdk.org; dev@dpdk.org; Amir Ilan <ailan@Airspan.com>; Veeresh Patil <vpatil@Airspan.com>
Subject: Re: [dpdk-dev] DPDK PDUMP Issue

NOT FROM AIRSPAN - Caution - External from: stephen@networkplumber.org On Tue, 28 Jul 2020 14:51:58 +0000 Dikshant Chitkara <dchitkara@Airspan.com> wrote:

> Hi Team,
> 
> With fix suggest in prev mail thread at testpmd side, PDUMP works with testpmd.
> 
> However when we try to run our own primary app with PDUMP as a secondary process, PDUMP console comes up, however it does not capture any packets.
> 
> Changes made at primary app side:
> 1. PDUMP initialised just after rte eal init:
> 
>   ret_pdump = rte_pdump_init();
>        if (ret_pdump < 0) {
>                printf("rte_pdump_init failed\n");
>        }
>        else
>        {
>                printf("rte_pdump_init success\n");
>        }
> 
> 2. Makefile modified to add all relevant files to be linked:
> 
> LIB_SO     =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool -lrte_cryptodev -lrte_ethdev -lrte_mbuf -lrte_mempool_ring  -lrte_member  -lrte_eventdev  -lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline  -lrte_table  -lrte_timer  -lrte_hash  -lrte_jobstats  -lrte_lpm  -lrte_power  -lrte_acl  -lrte_meter  -lrte_sch
> 
> Even tried to link final DPDK lib so as well:
> LIB_SO     =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-archive -L/usr/lib/x86_64-linux-gnu/ -fPIC
> 
> It seems both apps are able to connect over mp socket but pdump unable to capture data sent from primary app.
> 
> Can you tell us what else we might be missing here.
> 
> Note: We are using DPDK 19_05 built in shared lib mode.
> 
> 
> Primary app console:
> 
> EAL: Probing VFIO support...
> EAL: PCI device 0000:41:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:37d2 net_i40e
> EAL: PCI device 0000:41:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:37d2 net_i40e
> EAL: PCI device 0000:86:00.0 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.1 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.2 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.3 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:88:00.0 on NUMA socket 1
> EAL:   probe driver: 8086:158b net_i40e
> EAL: PCI device 0000:88:00.1 on NUMA socket 1
> EAL:   probe driver: 8086:158b net_i40e
> rte_pdump_init success
> pool_create successed
> DPDK TX Ethernet device (destination) opened successfully Before send 
> burst Packets sent. Count=32 Before send burst Packets sent. Count=32 
> Before send burst Packets sent. Count=32 Before send burst Packets 
> sent. Count=32 Before send burst Packets sent. Count=32 Before send 
> burst Packets sent. Count=32 Before send burst Packets sent. Count=32
> >>>  
> 
> Pdump console:
> 
> [root@flexran3 x86_64-native-linux-icc]# ./app/dpdk-pdump -d librte_pmd_i40e.so -d librte_pmd_pcap.so -- --pdump 'port=0,queue=*,tx-dev=/home/dchitkara/capture.pcap'
> EAL: Detected 80 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket 
> /var/run/dpdk/rte/mp_socket_45398_5ed780258ea46
> EAL: Probing VFIO support...
> EAL: PCI device 0000:41:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:37d2 net_i40e
> EAL: PCI device 0000:41:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:37d2 net_i40e
> EAL: PCI device 0000:86:00.0 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.1 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.2 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:86:00.3 on NUMA socket 1
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:88:00.0 on NUMA socket 1
> EAL:   probe driver: 8086:158b net_i40e
> EAL: PCI device 0000:88:00.1 on NUMA socket 1
> EAL:   probe driver: 8086:158b net_i40e
> Port 1 MAC: 02 70 63 61 70 00
>  core (0), capture for (1) tuples
>  - port 0 device ((null)) queue 65535
> ^C
> 
> Signal 2 received, preparing to exit...
> ##### PDUMP DEBUG STATS #####
>  -packets dequeued:                     0
>  -packets transmitted to vdev:          0
>  -packets freed:                        0
> [root@flexran3 x86_64-native-linux-icc]#
> 
> 
> 
> 
> -----Original Message-----
> From: Varghese, Vipin <vipin.varghese@intel.com>
> Sent: 22 July 2020 09:38
> To: Stephen Hemminger <stephen@networkplumber.org>; Dikshant Chitkara 
> <dchitkara@Airspan.com>
> Cc: users@dpdk.org; dev@dpdk.org; Amir Ilan <ailan@Airspan.com>; 
> Veeresh Patil <vpatil@Airspan.com>
> Subject: RE: [dpdk-dev] DPDK PDUMP Issue
> 
> NOT FROM AIRSPAN - Caution - External from: vipin.varghese@intel.com 
> Snipped
> 
> > Dikshant Chitkara <dchitkara@Airspan.com> wrote:
> >   
> > > Hi Team,
> > >
> > > We are facing an issue w.r.t to using DPDK PDUMP utility and want 
> > > to check if
> > you can help us in this regard.  
> > >
> > > This issue is specific to DPDK 19.05 version or may  be newer 
> > > versions and
> > was not found on DPDK 18.08 version.  
> > >
> > > The issue is that when we built DPDK in shared library mode and 
> > > try to run
> > PDUMP we get following error on PDUMP console:  
> > >
> > > EAL: Failed to hotplug add device
> > > EAL: Error - exiting with code: 1
> > >   Cause: vdev creation failed
> > >
> > > On Debugging above error message, I found that inside
> > > rte_dev_probe()
> > function in the file  lib/librte_eal/common/eal_common_dev.c , 
> > req.result = -
> > 14 which is non-zero value and points to enum EFAULT (Bad address) 
> > value, thus leading to above error.
> > >
> > > However, when I ran PDUMP in DPDK 18.08, I did not observe any 
> > > such issue
> > and it worked fine.  
> > >
> > > DPDK was built with following flags set in config/common_base file:
> > >
> > > CONFIG_RTE_LIBRTE_PMD_PCAP=y
> > > CONFIG_RTE_LIBRTE_PDUMP=y
> > >
> > > I ran PDUMP with testpmd as primary application and was trying to 
> > > send
> > some traffic on the Ethernet dpdk port using testpmd and capture it 
> > using pdump.
> > >
> > > Attached are the logs for both testpmd and pdump in both DPDK19_05 
> > > and
> > DPDK_18_08 version for your reference.  
> > >
> > > Let us know if you can help in this regard.
> > >
> > > Thanks,
> > > Dikshant
> > >  
> > 
> > Pdump runs as secondary process, what is your primary process.
> > Is the secondary process using the same exact versions of DPDK and 
> > libraries as the primary process?
> > The secondary process needs access to the same devices and drivers 
> > as the primary process to work.
> 
> Based on the log files shared, I have made assumptions as
> 
> 1. Primary: testpmd
> 2. DPDK version: 19.05
> 3. SHARED LIB in .config: yes
> 4. export LD_LIBRARY_PATH: yes
> 
> Using arguments passed in primary, I faced error ```
> EAL: Error - exiting with code: 1
>   Cause: Creation of mbuf pool for socket 0 failed: Invalid argument
> 
>   Cause: Mempool creation failed: Invalid argument ```
> 
> Hence had to modify with ` -d librte_mempool_ring.so`.  Using arguments passed in secondary, I faced similar error too. 
> 
> With these corrections, I am able to get similar error shared as ```
> EAL: failed to parse device "vdev:net_pcap_tx_0"
> EAL: Failed to hotplug add device on primary
> EAL: Error - exiting with code: 1
>   Cause: vdev creation failed
> ```
> 
> Checking the testpmd Makefile, it is narrowed down to missing PCAP_PMD build factor. I rebuild testpmd with ` LD_FLAGS="-lrte_pmd_pcap" make` and re-ran the same. With this I can get it working properly. 
> 
> Ideally there should had been an entry in Makefile as ``` ifeq 
> ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y) LDLIBS += -lrte_pmd_pcap endif ```
> 
> reference: This is similar to the error and solution provided in ` 
> https://stackoverflow.com/questions/62795017/dpdk-pdump-failed-to-hotp
> lug-add-device/62869287#62869287`
> 
> 

The primary/secondary work is that both processes have to discover the same memory areas and devices.

The NUMA thing might be related, does your system have multiple cpu sockets.
What does the cpu_layout python script show.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-28 16:41         ` Dikshant Chitkara
@ 2020-07-28 17:03           ` Stephen Hemminger
  2020-07-28 17:08             ` Dikshant Chitkara
  0 siblings, 1 reply; 14+ messages in thread
From: Stephen Hemminger @ 2020-07-28 17:03 UTC (permalink / raw)
  To: Dikshant Chitkara; +Cc: Varghese, Vipin, users, dev, Amir Ilan, Veeresh Patil

On Tue, 28 Jul 2020 16:41:38 +0000
Dikshant Chitkara <dchitkara@Airspan.com> wrote:

> Hi Stephen,
> Our system has 2 sockets as seen from below :
> 
> [root@flexran3 dchitkara]# lscpu
> Architecture:          x86_64
> CPU op-mode(s):        32-bit, 64-bit
> Byte Order:            Little Endian
> CPU(s):                80
> On-line CPU(s) list:   0-79
> Thread(s) per core:    2
> Core(s) per socket:    20
> Socket(s):             2
> NUMA node(s):          2

Did you configure hugepages on both NUMA nodes?
You might be able to get away with only doing one node that has the device
attached but probably both need to have dedicated hugepages.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-28 17:03           ` Stephen Hemminger
@ 2020-07-28 17:08             ` Dikshant Chitkara
  0 siblings, 0 replies; 14+ messages in thread
From: Dikshant Chitkara @ 2020-07-28 17:08 UTC (permalink / raw)
  To: Stephen Hemminger; +Cc: Varghese, Vipin, users, dev, Amir Ilan, Veeresh Patil

Hi Stephen,

If that was the case, then how come pdump worked with testpmd?

See below testpmd with pdumg log:

Testpmd:

[root@flexran3 x86_64-native-linux-icc]# ./app/testpmd -c 0xf0 -n 4 -- -i --port-topology=chained
EAL: Detected 80 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Probing VFIO support...
EAL: PCI device 0000:41:00.0 on NUMA socket 0
EAL:   probe driver: 8086:37d2 net_i40e
EAL: PCI device 0000:41:00.1 on NUMA socket 0
EAL:   probe driver: 8086:37d2 net_i40e
EAL: PCI device 0000:86:00.0 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.1 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.2 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.3 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:88:00.0 on NUMA socket 1
EAL:   probe driver: 8086:158b net_i40e
EAL: PCI device 0000:88:00.1 on NUMA socket 1
EAL:   probe driver: 8086:158b net_i40e
Interactive-mode selected
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
testpmd: create a new mbuf pool <mbuf_pool_socket_1>: n=171456, size=2176, socket=1
testpmd: preferred mempool ops selected: ring_mp_mc
Configuring Port 0 (socket 1)
Port 0: 3C:FD:FE:CD:34:A4
Checking link statuses...
Done
testpmd>
Port 0: link state change event

testpmd>
testpmd>
testpmd> start tx_first
io packet forwarding - ports=1 - cores=1 - streams=1 - NUMA support enabled, MP allocation mode: native
Logical Core 5 (socket 0) forwards packets on 1 streams:
  RX P=0/Q=0 (socket 1) -> TX P=0/Q=0 (socket 1) peer=02:00:00:00:00:00

  io packet forwarding packets/burst=32
  nb forwarding cores=1 - nb forwarding ports=1
  port 0: RX queue number: 1 Tx queue number: 1
    Rx offloads=0x0 Tx offloads=0x10000
    RX queue: 0
      RX desc=256 - RX free threshold=32
      RX threshold registers: pthresh=8 hthresh=8  wthresh=0
      RX Offloads=0x0
    TX queue: 0
      TX desc=256 - TX free threshold=32
      TX threshold registers: pthresh=32 hthresh=0  wthresh=0
      TX offloads=0x10000 - TX RS bit threshold=32
  port 1: RX queue number: 1 Tx queue number: 1
    Rx offloads=0x0 Tx offloads=0x0
Invalid RX queue_id=0
    RX queue: 0
      RX desc=0 - RX free threshold=0
      RX threshold registers: pthresh=0 hthresh=0  wthresh=0
      RX Offloads=0x0
    TX queue: 0
      TX desc=0 - TX free threshold=0
      TX threshold registers: pthresh=0 hthresh=0  wthresh=0
      TX offloads=0x0 - TX RS bit threshold=0
testpmd> stop
Telling cores to stop...
Waiting for lcores to finish...

  ---------------------- Forward statistics for port 0  ----------------------
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  TX-packets: 32             TX-dropped: 0             TX-total: 32
  ----------------------------------------------------------------------------

  +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  TX-packets: 32             TX-dropped: 0             TX-total: 32
  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Done.


PDUMP:

[root@flexran3 x86_64-native-linux-icc]# ./app/dpdk-pdump -d librte_pmd_i40e.so -d librte_pmd_pcap.so -- --pdump 'port=0,queue=*,tx-dev=/home/dchitkara/capture.pcap'
EAL: Detected 80 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_120725_2d88411f7f7d4
EAL: Probing VFIO support...
EAL: PCI device 0000:41:00.0 on NUMA socket 0
EAL:   probe driver: 8086:37d2 net_i40e
EAL: PCI device 0000:41:00.1 on NUMA socket 0
EAL:   probe driver: 8086:37d2 net_i40e
EAL: PCI device 0000:86:00.0 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.1 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.2 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:86:00.3 on NUMA socket 1
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:88:00.0 on NUMA socket 1
EAL:   probe driver: 8086:158b net_i40e
EAL: PCI device 0000:88:00.1 on NUMA socket 1
EAL:   probe driver: 8086:158b net_i40e
Port 1 MAC: 02 70 63 61 70 00
 core (0), capture for (1) tuples
 - port 0 device ((null)) queue 65535
^C

Signal 2 received, preparing to exit...
##### PDUMP DEBUG STATS #####
 -packets dequeued:                     32
 -packets transmitted to vdev:          32
 -packets freed:                        0
[root@flexran3 x86_64-native-linux-icc]



-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org> 
Sent: 28 July 2020 22:34
To: Dikshant Chitkara <dchitkara@Airspan.com>
Cc: Varghese, Vipin <vipin.varghese@intel.com>; users@dpdk.org; dev@dpdk.org; Amir Ilan <ailan@Airspan.com>; Veeresh Patil <vpatil@Airspan.com>
Subject: Re: [dpdk-dev] DPDK PDUMP Issue

NOT FROM AIRSPAN - Caution - External from: stephen@networkplumber.org On Tue, 28 Jul 2020 16:41:38 +0000 Dikshant Chitkara <dchitkara@Airspan.com> wrote:

> Hi Stephen,
> Our system has 2 sockets as seen from below :
> 
> [root@flexran3 dchitkara]# lscpu
> Architecture:          x86_64
> CPU op-mode(s):        32-bit, 64-bit
> Byte Order:            Little Endian
> CPU(s):                80
> On-line CPU(s) list:   0-79
> Thread(s) per core:    2
> Core(s) per socket:    20
> Socket(s):             2
> NUMA node(s):          2

Did you configure hugepages on both NUMA nodes?
You might be able to get away with only doing one node that has the device attached but probably both need to have dedicated hugepages.

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-28 14:51     ` Dikshant Chitkara
  2020-07-28 16:23       ` Stephen Hemminger
@ 2020-07-29  0:59       ` Varghese, Vipin
  2020-07-29  9:14         ` Dikshant Chitkara
  1 sibling, 1 reply; 14+ messages in thread
From: Varghese, Vipin @ 2020-07-29  0:59 UTC (permalink / raw)
  To: Dikshant Chitkara, Stephen Hemminger; +Cc: users, dev, Amir Ilan, Veeresh Patil

Snipped

> Hi Team,
> 
> With fix suggest in prev mail thread at testpmd side, PDUMP works with
> testpmd.
> 
> However when we try to run our own primary app with PDUMP as a secondary
> process, PDUMP console comes up, however it does not capture any packets.
> 
> Changes made at primary app side:
> 1. PDUMP initialised just after rte eal init:
> 
>   ret_pdump = rte_pdump_init();
>        if (ret_pdump < 0) {
>                printf("rte_pdump_init failed\n");
>        }
>        else
>        {
>                printf("rte_pdump_init success\n");
>        }
> 
> 2. Makefile modified to add all relevant files to be linked:
> 
> LIB_SO     =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -
> lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool -lrte_cryptodev
> -lrte_ethdev -lrte_mbuf -lrte_mempool_ring  -lrte_member  -lrte_eventdev  -
> lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -
> lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline  -lrte_table  -lrte_timer  -
> lrte_hash  -lrte_jobstats  -lrte_lpm  -lrte_power  -lrte_acl  -lrte_meter  -lrte_sch
> 
> Even tried to link final DPDK lib so as well:
> LIB_SO     =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-archive -
> L/usr/lib/x86_64-linux-gnu/ -fPIC

Ok, I think I have seen similar outcomes in custom Makefiles. Can you execute with `make -n` with the master Makefile and cross the necessary libraries are in bound between `-Wl,--whole-archive` and `-Wl,--no-whole-archive `  (specically for shared libraries). 

snipped


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-29  0:59       ` Varghese, Vipin
@ 2020-07-29  9:14         ` Dikshant Chitkara
  2020-07-29  9:51           ` Varghese, Vipin
  0 siblings, 1 reply; 14+ messages in thread
From: Dikshant Chitkara @ 2020-07-29  9:14 UTC (permalink / raw)
  To: Varghese, Vipin, Stephen Hemminger; +Cc: users, dev, Amir Ilan, Veeresh Patil

Hi Vipin,

I tried using `-Wl,--whole-archive` and `-Wl,--no-whole-archive `  option with my necessary libraries but it does not seem to help as well.

Below is the makefile log for my app:

g++ -shared -Wl,--export-dynamic packet_generator.o  -L/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/lib -Wl,--whole-archive -Wl,-lrte_mempool_ring -Wl,-lrte_member -Wl,-lrte_eventdev -Wl,-lrte_pmd_pcap -Wl,-lrte_pdump -Wl,-lrte_bus_vmbus -Wl,-lrte_pci -Wl,-lrte_bus_pci -Wl,-lrte_bus_vdev -Wl,-lrte_net -Wl,-lrte_distributor -Wl,-lrte_reorder -Wl,-lrte_kni -Wl,-lrte_pipeline -Wl,-lrte_table -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_jobstats -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,-lrte_vhost -Wl,--start-group -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lrte_ethdev -Wl,-lrte_cryptodev -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond -Wl,-lrte_pmd_vmxnet3_uio -Wl,-lrte_pmd_virtio -Wl,-lrte_pmd_cxgbe -Wl,-lrte_pmd_enic -Wl,-lrte_pmd_i40e -Wl,-lrte_pmd_fm10k -Wl,-lrte_pmd_ixgbe -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ring -Wl,-lrte_pmd_af_packet -Wl,-lrte_pmd_null -Wl,-lrt -Wl,-lm -Wl,-ldl -Wl,--end-group -Wl,--no-whole-archive  -o ../../../COMMON/../bin/PACKET_GENERATOR_TEST_MOD.so


Thanks,
Dikshant

-----Original Message-----
From: Varghese, Vipin <vipin.varghese@intel.com> 
Sent: 29 July 2020 06:30
To: Dikshant Chitkara <dchitkara@Airspan.com>; Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org; dev@dpdk.org; Amir Ilan <ailan@Airspan.com>; Veeresh Patil <vpatil@Airspan.com>
Subject: RE: [dpdk-dev] DPDK PDUMP Issue

NOT FROM AIRSPAN - Caution - External from: vipin.varghese@intel.com Snipped

> Hi Team,
> 
> With fix suggest in prev mail thread at testpmd side, PDUMP works with 
> testpmd.
> 
> However when we try to run our own primary app with PDUMP as a 
> secondary process, PDUMP console comes up, however it does not capture any packets.
> 
> Changes made at primary app side:
> 1. PDUMP initialised just after rte eal init:
> 
>   ret_pdump = rte_pdump_init();
>        if (ret_pdump < 0) {
>                printf("rte_pdump_init failed\n");
>        }
>        else
>        {
>                printf("rte_pdump_init success\n");
>        }
> 
> 2. Makefile modified to add all relevant files to be linked:
> 
> LIB_SO     =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -
> lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool 
> -lrte_cryptodev -lrte_ethdev -lrte_mbuf -lrte_mempool_ring  -lrte_member  -lrte_eventdev  -
> lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -
> lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline  
> -lrte_table  -lrte_timer  - lrte_hash  -lrte_jobstats  -lrte_lpm  
> -lrte_power  -lrte_acl  -lrte_meter  -lrte_sch
> 
> Even tried to link final DPDK lib so as well:
> LIB_SO     =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-archive -
> L/usr/lib/x86_64-linux-gnu/ -fPIC

Ok, I think I have seen similar outcomes in custom Makefiles. Can you execute with `make -n` with the master Makefile and cross the necessary libraries are in bound between `-Wl,--whole-archive` and `-Wl,--no-whole-archive `  (specically for shared libraries). 

snipped


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-29  9:14         ` Dikshant Chitkara
@ 2020-07-29  9:51           ` Varghese, Vipin
  2020-07-29  9:56             ` Varghese, Vipin
  2020-07-29 14:08             ` Dikshant Chitkara
  0 siblings, 2 replies; 14+ messages in thread
From: Varghese, Vipin @ 2020-07-29  9:51 UTC (permalink / raw)
  To: Dikshant Chitkara, Stephen Hemminger; +Cc: users, dev, Amir Ilan, Veeresh Patil

Hi Dikshant,

Looks like the custom Makefile log is quite different in passing DPDK CFLAGS and LDFLAGS. Also here are couple of surprises for me 

1. Unable to find `make -n` logs

2. presence of g++ is present in each line

3. unable to find include option

4. request was to run `make -n` and cross the relevant libraries are bound within the `-Wl,--whole-archive` and `-Wl,--no-whole-archive `. 

5. Unable to find `-Wl,-lpcap` passed for `-Wl,-lrte_pmd_pcap -Wl,-lrte_pdump`

Hint: I normally take up sample like example/l2fwd and work towards to removing unwanted libraries while keeping the content and format intact for my custom makefile. 

> -----Original Message-----
> From: Dikshant Chitkara <dchitkara@Airspan.com>
> Sent: Wednesday, July 29, 2020 2:44 PM
> To: Varghese, Vipin <vipin.varghese@intel.com>; Stephen Hemminger
> <stephen@networkplumber.org>
> Cc: users@dpdk.org; dev@dpdk.org; Amir Ilan <ailan@Airspan.com>; Veeresh
> Patil <vpatil@Airspan.com>
> Subject: RE: [dpdk-dev] DPDK PDUMP Issue
> 
> Hi Vipin,
> 
> I tried using `-Wl,--whole-archive` and `-Wl,--no-whole-archive `  option with
> my necessary libraries but it does not seem to help as well.
> 
> Below is the makefile log for my app:
> 
> g++ -shared -Wl,--export-dynamic packet_generator.o
> g++ -L/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/li
> g++ b -Wl,--whole-archive -Wl,-lrte_mempool_ring -Wl,-lrte_member
> g++ -Wl,-lrte_eventdev -Wl,-lrte_pmd_pcap -Wl,-lrte_pdump
> g++ -Wl,-lrte_bus_vmbus -Wl,-lrte_pci -Wl,-lrte_bus_pci
> g++ -Wl,-lrte_bus_vdev -Wl,-lrte_net -Wl,-lrte_distributor
> g++ -Wl,-lrte_reorder -Wl,-lrte_kni -Wl,-lrte_pipeline -Wl,-lrte_table
> g++ -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_jobstats
> g++ -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter
> g++ -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,-lrte_vhost -Wl,--start-group
> g++ -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lrte_ethdev
> g++ -Wl,-lrte_cryptodev -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal
> g++ -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond
> g++ -Wl,-lrte_pmd_vmxnet3_uio -Wl,-lrte_pmd_virtio -Wl,-lrte_pmd_cxgbe
> g++ -Wl,-lrte_pmd_enic -Wl,-lrte_pmd_i40e -Wl,-lrte_pmd_fm10k
> g++ -Wl,-lrte_pmd_ixgbe -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ring
> g++ -Wl,-lrte_pmd_af_packet -Wl,-lrte_pmd_null -Wl,-lrt -Wl,-lm -Wl,-ldl
> g++ -Wl,--end-group -Wl,--no-whole-archive  -o
> g++ ../../../COMMON/../bin/PACKET_GENERATOR_TEST_MOD.so
> 
> 
> Thanks,
> Dikshant
> 
> Snipped
> 
> > Hi Team,
> >
> > With fix suggest in prev mail thread at testpmd side, PDUMP works with
> > testpmd.
> >
> > However when we try to run our own primary app with PDUMP as a
> > secondary process, PDUMP console comes up, however it does not capture
> any packets.
> >
> > Changes made at primary app side:
> > 1. PDUMP initialised just after rte eal init:
> >
> >   ret_pdump = rte_pdump_init();
> >        if (ret_pdump < 0) {
> >                printf("rte_pdump_init failed\n");
> >        }
> >        else
> >        {
> >                printf("rte_pdump_init success\n");
> >        }
> >
> > 2. Makefile modified to add all relevant files to be linked:
> >
> > LIB_SO     =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -
> > lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool
> > -lrte_cryptodev -lrte_ethdev -lrte_mbuf -lrte_mempool_ring  -lrte_member  -
> lrte_eventdev  -
> > lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -
> > lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline -lrte_table
> > -lrte_timer  - lrte_hash  -lrte_jobstats  -lrte_lpm -lrte_power
> > -lrte_acl  -lrte_meter  -lrte_sch
> >
> > Even tried to link final DPDK lib so as well:
> > LIB_SO     =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-archive -
> > L/usr/lib/x86_64-linux-gnu/ -fPIC
> 
> Ok, I think I have seen similar outcomes in custom Makefiles. Can you execute
> with `make -n` with the master Makefile and cross the necessary libraries are
> in bound between `-Wl,--whole-archive` and `-Wl,--no-whole-archive `
> (specically for shared libraries).
> 
> snipped


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-29  9:51           ` Varghese, Vipin
@ 2020-07-29  9:56             ` Varghese, Vipin
  2020-07-29 14:08             ` Dikshant Chitkara
  1 sibling, 0 replies; 14+ messages in thread
From: Varghese, Vipin @ 2020-07-29  9:56 UTC (permalink / raw)
  To: Varghese, Vipin, Dikshant Chitkara, Stephen Hemminger
  Cc: users, dev, Amir Ilan, Veeresh Patil

Couple more request, 

1. please avoid ` NOT FROM AIRSPAN - Caution - External ` headers & banners.

2. If possible, use `snip` or `snipped` to remove clutter and bring foucs

Snipped

> Hi Dikshant,
> 
> Looks like the custom Makefile log is quite different in passing DPDK CFLAGS
> and LDFLAGS. Also here are couple of surprises for me
> 
> 1. Unable to find `make -n` logs
> 
> 2. presence of g++ is present in each line
> 
> 3. unable to find include option
> 
> 4. request was to run `make -n` and cross the relevant libraries are bound
> within the `-Wl,--whole-archive` and `-Wl,--no-whole-archive `.
> 
> 5. Unable to find `-Wl,-lpcap` passed for `-Wl,-lrte_pmd_pcap -Wl,-
> lrte_pdump`
> 
> Hint: I normally take up sample like example/l2fwd and work towards to
> removing unwanted libraries while keeping the content and format intact for
> my custom makefile.
> 
snipped
> >
> > Hi Vipin,
> >
> > I tried using `-Wl,--whole-archive` and `-Wl,--no-whole-archive `
> > option with my necessary libraries but it does not seem to help as well.
> >
> > Below is the makefile log for my app:
> >
> > g++ -shared -Wl,--export-dynamic packet_generator.o
> > g++ -L/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/
> > g++ li b -Wl,--whole-archive -Wl,-lrte_mempool_ring -Wl,-lrte_member
> > g++ -Wl,-lrte_eventdev -Wl,-lrte_pmd_pcap -Wl,-lrte_pdump
> > g++ -Wl,-lrte_bus_vmbus -Wl,-lrte_pci -Wl,-lrte_bus_pci
> > g++ -Wl,-lrte_bus_vdev -Wl,-lrte_net -Wl,-lrte_distributor
> > g++ -Wl,-lrte_reorder -Wl,-lrte_kni -Wl,-lrte_pipeline -Wl,-lrte_table
> > g++ -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_jobstats
> > g++ -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter
> > g++ -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,-lrte_vhost -Wl,--start-group
> > g++ -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lrte_ethdev
> > g++ -Wl,-lrte_cryptodev -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal
> > g++ -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond
> > g++ -Wl,-lrte_pmd_vmxnet3_uio -Wl,-lrte_pmd_virtio -Wl,-lrte_pmd_cxgbe
> > g++ -Wl,-lrte_pmd_enic -Wl,-lrte_pmd_i40e -Wl,-lrte_pmd_fm10k
> > g++ -Wl,-lrte_pmd_ixgbe -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ring
> > g++ -Wl,-lrte_pmd_af_packet -Wl,-lrte_pmd_null -Wl,-lrt -Wl,-lm
> > g++ -Wl,-ldl -Wl,--end-group -Wl,--no-whole-archive  -o
> > g++ ../../../COMMON/../bin/PACKET_GENERATOR_TEST_MOD.so
> >
> >
snipped
> >
> > > Hi Team,
> > >
> > > With fix suggest in prev mail thread at testpmd side, PDUMP works
> > > with testpmd.
> > >
> > > However when we try to run our own primary app with PDUMP as a
> > > secondary process, PDUMP console comes up, however it does not
> > > capture
> > any packets.
> > >
> > > Changes made at primary app side:
> > > 1. PDUMP initialised just after rte eal init:
> > >
> > >   ret_pdump = rte_pdump_init();
> > >        if (ret_pdump < 0) {
> > >                printf("rte_pdump_init failed\n");
> > >        }
> > >        else
> > >        {
> > >                printf("rte_pdump_init success\n");
> > >        }
> > >
> > > 2. Makefile modified to add all relevant files to be linked:
> > >
> > > LIB_SO     =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -
> > > lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool
> > > -lrte_cryptodev -lrte_ethdev -lrte_mbuf -lrte_mempool_ring
> > > -lrte_member  -
> > lrte_eventdev  -
> > > lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -
> > > lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline
> > > -lrte_table -lrte_timer  - lrte_hash  -lrte_jobstats  -lrte_lpm
> > > -lrte_power -lrte_acl  -lrte_meter  -lrte_sch
> > >
> > > Even tried to link final DPDK lib so as well:
> > > LIB_SO     =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-
> archive -
> > > L/usr/lib/x86_64-linux-gnu/ -fPIC
> >
> > Ok, I think I have seen similar outcomes in custom Makefiles. Can you
> > execute with `make -n` with the master Makefile and cross the
> > necessary libraries are in bound between `-Wl,--whole-archive` and
> > `-Wl,--no-whole-archive ` (specically for shared libraries).
> >
> > snipped


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-29  9:51           ` Varghese, Vipin
  2020-07-29  9:56             ` Varghese, Vipin
@ 2020-07-29 14:08             ` Dikshant Chitkara
  2020-07-30  2:35               ` Varghese, Vipin
  1 sibling, 1 reply; 14+ messages in thread
From: Dikshant Chitkara @ 2020-07-29 14:08 UTC (permalink / raw)
  To: Varghese, Vipin, Stephen Hemminger
  Cc: users, dev, Amir Ilan, Veeresh Patil, Igor Shoihet

Hi Vipin,

Here is full log with include option and build with make -n option from master makefile as well:

make[2]: Entering directory `/mnt/data/dchitkara/PHY5G/Prototype/NR_5G_SIM/Tests/COMMON/PACKET_GENERATOR'
echo ./packet_generator.cc  -msse4.1  -I../../../COMMON/Sys_API/Math_API/  -I../../../COMMON/Sys_API/Math_API/  -I../../../COMMON/Sys_API/Module_API/    -I../../../COMMON/Sys_API/common_intel/ 
echo packet_generator.o
test -d  || mkdir -p  
g++  -msse4.1  -I../../../COMMON/Sys_API/Math_API/  -I../../../COMMON/Sys_API/Math_API/  -I../../../COMMON/Sys_API/Module_API -I./ -DTIME_DATE=\"DATE:29/07/20_TIME:09:57:19\" -DMOD_NAME=\"PACKET_GENERATOR_TEST_MOD\"  -DARCH_X86 -I/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/include -I -DAS_INFRA_NULL=0 -DEMULATOR_MODE  -DINTEL -std=c++11  -D_4x4_ -O3 -g -DDEBUG   -fPIC -c ./packet_generator.cc
echo /usr/local/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/pstl/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/ipp/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/mkl/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/ipp/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/mkl/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/pstl/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/daal/include
echo packet_generator.o 
test -d ../../../COMMON/../bin || mkdir -p ../../../COMMON/../bin 
g++ -shared -Wl,--export-dynamic packet_generator.o  -L/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/lib -Wl,--whole-archive -Wl,-lrte_mempool_ring -Wl,-lrte_member -Wl,-lrte_eventdev -Wl,-lpcap -Wl,-lrte_pmd_pcap -Wl,-lrte_pdump -Wl,-lrte_bus_vmbus -Wl,-lrte_pci -Wl,-lrte_bus_pci -Wl,-lrte_bus_vdev -Wl,-lrte_net -Wl,-lrte_distributor -Wl,-lrte_reorder -Wl,-lrte_kni -Wl,-lrte_pipeline -Wl,-lrte_table -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_jobstats -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,-lrte_vhost -Wl,--start-group -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lrte_ethdev -Wl,-lrte_cryptodev -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond -Wl,-lrte_pmd_vmxnet3_uio -Wl,-lrte_pmd_virtio -Wl,-lrte_pmd_cxgbe -Wl,-lrte_pmd_enic -Wl,-lrte_pmd_i40e -Wl,-lrte_pmd_fm10k -Wl,-lrte_pmd_ixgbe -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ring -Wl,-lrte_pmd_af_packet -Wl,-lrte_pmd_null -Wl,-lrt -Wl,-lm -Wl,-ldl -Wl,--end-group -Wl,--no-whole-archive  -o ../../../COMMON/../bin/PACKET_GENERATOR_TEST_MOD.so
make[2]: Leaving directory `/mnt/data/dchitkara/PHY5G/Prototype/NR_5G_SIM/Tests/COMMON/PACKET_GENERATOR'

Please have a note that module we are running is just one part of our CPP project treated as a separate test module.

Thanks,
Dikshant

-----Original Message-----
From: Varghese, Vipin <vipin.varghese@intel.com> 
Sent: 29 July 2020 15:21
To: Dikshant Chitkara <dchitkara@Airspan.com>; Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org; dev@dpdk.org; Amir Ilan <ailan@Airspan.com>; Veeresh Patil <vpatil@Airspan.com>
Subject: RE: [dpdk-dev] DPDK PDUMP Issue

Hi Dikshant,

Looks like the custom Makefile log is quite different in passing DPDK CFLAGS and LDFLAGS. Also here are couple of surprises for me 

1. Unable to find `make -n` logs

2. presence of g++ is present in each line

3. unable to find include option

4. request was to run `make -n` and cross the relevant libraries are bound within the `-Wl,--whole-archive` and `-Wl,--no-whole-archive `. 

5. Unable to find `-Wl,-lpcap` passed for `-Wl,-lrte_pmd_pcap -Wl,-lrte_pdump`

Hint: I normally take up sample like example/l2fwd and work towards to removing unwanted libraries while keeping the content and format intact for my custom makefile. 

> -----Original Message-----
> From: Dikshant Chitkara <dchitkara@Airspan.com>
> Sent: Wednesday, July 29, 2020 2:44 PM
> To: Varghese, Vipin <vipin.varghese@intel.com>; Stephen Hemminger 
> <stephen@networkplumber.org>
> Cc: users@dpdk.org; dev@dpdk.org; Amir Ilan <ailan@Airspan.com>; 
> Veeresh Patil <vpatil@Airspan.com>
> Subject: RE: [dpdk-dev] DPDK PDUMP Issue
> 
> Hi Vipin,
> 
> I tried using `-Wl,--whole-archive` and `-Wl,--no-whole-archive `  
> option with my necessary libraries but it does not seem to help as well.
> 
> Below is the makefile log for my app:
> 
> g++ -shared -Wl,--export-dynamic packet_generator.o 
> g++ -L/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/
> g++ li b -Wl,--whole-archive -Wl,-lrte_mempool_ring -Wl,-lrte_member 
> g++ -Wl,-lrte_eventdev -Wl,-lrte_pmd_pcap -Wl,-lrte_pdump 
> g++ -Wl,-lrte_bus_vmbus -Wl,-lrte_pci -Wl,-lrte_bus_pci 
> g++ -Wl,-lrte_bus_vdev -Wl,-lrte_net -Wl,-lrte_distributor 
> g++ -Wl,-lrte_reorder -Wl,-lrte_kni -Wl,-lrte_pipeline -Wl,-lrte_table 
> g++ -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_jobstats 
> g++ -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter 
> g++ -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,-lrte_vhost -Wl,--start-group 
> g++ -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lrte_ethdev 
> g++ -Wl,-lrte_cryptodev -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal 
> g++ -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond 
> g++ -Wl,-lrte_pmd_vmxnet3_uio -Wl,-lrte_pmd_virtio -Wl,-lrte_pmd_cxgbe 
> g++ -Wl,-lrte_pmd_enic -Wl,-lrte_pmd_i40e -Wl,-lrte_pmd_fm10k 
> g++ -Wl,-lrte_pmd_ixgbe -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ring 
> g++ -Wl,-lrte_pmd_af_packet -Wl,-lrte_pmd_null -Wl,-lrt -Wl,-lm 
> g++ -Wl,-ldl -Wl,--end-group -Wl,--no-whole-archive  -o 
> g++ ../../../COMMON/../bin/PACKET_GENERATOR_TEST_MOD.so
> 
> 
> Thanks,
> Dikshant
> 
> Snipped
> 
> > Hi Team,
> >
> > With fix suggest in prev mail thread at testpmd side, PDUMP works 
> > with testpmd.
> >
> > However when we try to run our own primary app with PDUMP as a 
> > secondary process, PDUMP console comes up, however it does not 
> > capture
> any packets.
> >
> > Changes made at primary app side:
> > 1. PDUMP initialised just after rte eal init:
> >
> >   ret_pdump = rte_pdump_init();
> >        if (ret_pdump < 0) {
> >                printf("rte_pdump_init failed\n");
> >        }
> >        else
> >        {
> >                printf("rte_pdump_init success\n");
> >        }
> >
> > 2. Makefile modified to add all relevant files to be linked:
> >
> > LIB_SO     =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -
> > lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool 
> > -lrte_cryptodev -lrte_ethdev -lrte_mbuf -lrte_mempool_ring  
> > -lrte_member  -
> lrte_eventdev  -
> > lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -
> > lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline 
> > -lrte_table -lrte_timer  - lrte_hash  -lrte_jobstats  -lrte_lpm 
> > -lrte_power -lrte_acl  -lrte_meter  -lrte_sch
> >
> > Even tried to link final DPDK lib so as well:
> > LIB_SO     =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-archive -
> > L/usr/lib/x86_64-linux-gnu/ -fPIC
> 
> Ok, I think I have seen similar outcomes in custom Makefiles. Can you 
> execute with `make -n` with the master Makefile and cross the 
> necessary libraries are in bound between `-Wl,--whole-archive` and 
> `-Wl,--no-whole-archive ` (specically for shared libraries).
> 
> snipped

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue
  2020-07-29 14:08             ` Dikshant Chitkara
@ 2020-07-30  2:35               ` Varghese, Vipin
  0 siblings, 0 replies; 14+ messages in thread
From: Varghese, Vipin @ 2020-07-30  2:35 UTC (permalink / raw)
  To: Dikshant Chitkara, Stephen Hemminger
  Cc: users, dev, Amir Ilan, Veeresh Patil, Igor Shoihet

Hi Dikshant,

Summarizing the contents from earlier mails below

1. Issue-1 shared with PDUMP not working with testpmd - solution shared and suggested what needs to be added to fix the same.

2. Issue-2 shared for custom Makefile for application not working - pointed out possible cause and missing order of libraries in CFLAGS and LDFLAGS. Suggested to use an existing working DPDK/example content for custom Makefile. 

Please note I do not have the project or Makefile for use case to try it locally, hence please try

```
5. Unable to find `-Wl,-lpcap` passed for `-Wl,-lrte_pmd_pcap -Wl,-lrte_pdump`

Hint: I normally take up sample like example/l2fwd and work towards to removing unwanted libraries while keeping the content and format intact for my custom makefile.
```

Snipped

> 
> Hi Vipin,
> 
> Here is full log with include option and build with make -n option from master
> makefile as well:
> 
> make[2]: Entering directory
> `/mnt/data/dchitkara/PHY5G/Prototype/NR_5G_SIM/Tests/COMMON/PACKE
> T_GENERATOR'
> echo ./packet_generator.cc  -msse4.1  -I../../../COMMON/Sys_API/Math_API/  -
> I../../../COMMON/Sys_API/Math_API/  -
> I../../../COMMON/Sys_API/Module_API/    -
> I../../../COMMON/Sys_API/common_intel/
> echo packet_generator.o
> test -d  || mkdir -p
> g++  -msse4.1  -I../../../COMMON/Sys_API/Math_API/  -
> I../../../COMMON/Sys_API/Math_API/  -
> I../../../COMMON/Sys_API/Module_API -I./ -
> DTIME_DATE=\"DATE:29/07/20_TIME:09:57:19\" -
> DMOD_NAME=\"PACKET_GENERATOR_TEST_MOD\"  -DARCH_X86 -
> I/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/include
> -I -DAS_INFRA_NULL=0 -DEMULATOR_MODE  -DINTEL -std=c++11  -D_4x4_ -O3
> -g -DDEBUG   -fPIC -c ./packet_generator.cc
> echo
> /usr/local/include:/opt/intel/system_studio_2019/compilers_and_libraries_20
> 19.2.187/linux/pstl/include:/opt/intel/system_studio_2019/compilers_and_lib
> raries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compiler
> s_and_libraries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019
> /compilers_and_libraries_2019.2.187/linux/ipp/include:/opt/intel/system_stu
> dio_2019/compilers_and_libraries_2019.2.187/linux/mkl/include:/opt/intel/s
> ystem_studio_2019/compilers_and_libraries_2019.2.187/linux/ipp/include:/o
> pt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/mkl/i
> nclude:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/li
> nux/pstl/include:/opt/intel/system_studio_2019/compilers_and_libraries_201
> 9.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compilers_and_libr
> aries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compilers
> _and_libraries_2019.2.187/linux/daal/include
> echo packet_generator.o
> test -d ../../../COMMON/../bin || mkdir -p ../../../COMMON/../bin
> g++ -shared -Wl,--export-dynamic packet_generator.o
> g++ -L/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/li
> g++ b -Wl,--whole-archive -Wl,-lrte_mempool_ring -Wl,-lrte_member
> g++ -Wl,-lrte_eventdev -Wl,-lpcap -Wl,-lrte_pmd_pcap -Wl,-lrte_pdump
> g++ -Wl,-lrte_bus_vmbus -Wl,-lrte_pci -Wl,-lrte_bus_pci
> g++ -Wl,-lrte_bus_vdev -Wl,-lrte_net -Wl,-lrte_distributor
> g++ -Wl,-lrte_reorder -Wl,-lrte_kni -Wl,-lrte_pipeline -Wl,-lrte_table
> g++ -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_jobstats
> g++ -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter
> g++ -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,-lrte_vhost -Wl,--start-group
> g++ -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lrte_ethdev
> g++ -Wl,-lrte_cryptodev -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal
> g++ -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond
> g++ -Wl,-lrte_pmd_vmxnet3_uio -Wl,-lrte_pmd_virtio -Wl,-lrte_pmd_cxgbe
> g++ -Wl,-lrte_pmd_enic -Wl,-lrte_pmd_i40e -Wl,-lrte_pmd_fm10k
> g++ -Wl,-lrte_pmd_ixgbe -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ring
> g++ -Wl,-lrte_pmd_af_packet -Wl,-lrte_pmd_null -Wl,-lrt -Wl,-lm -Wl,-ldl
> g++ -Wl,--end-group -Wl,--no-whole-archive  -o
> g++ ../../../COMMON/../bin/PACKET_GENERATOR_TEST_MOD.so
> make[2]: Leaving directory
> `/mnt/data/dchitkara/PHY5G/Prototype/NR_5G_SIM/Tests/COMMON/PACKE
> T_GENERATOR'
> 
> Please have a note that module we are running is just one part of our CPP
> project treated as a separate test module.

snipped
> 
> Hi Dikshant,
> 
> Looks like the custom Makefile log is quite different in passing DPDK CFLAGS
> and LDFLAGS. Also here are couple of surprises for me
> 
> 1. Unable to find `make -n` logs
> 
> 2. presence of g++ is present in each line
> 
> 3. unable to find include option
> 
> 4. request was to run `make -n` and cross the relevant libraries are bound
> within the `-Wl,--whole-archive` and `-Wl,--no-whole-archive `.
> 
> 5. Unable to find `-Wl,-lpcap` passed for `-Wl,-lrte_pmd_pcap -Wl,-
> lrte_pdump`
> 
> Hint: I normally take up sample like example/l2fwd and work towards to
> removing unwanted libraries while keeping the content and format intact for
> my custom makefile.
> 
snipped

^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, back to index

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-14  8:40 [dpdk-users] DPDK PDUMP Issue Dikshant Chitkara
2020-07-14 16:29 ` [dpdk-users] [dpdk-dev] " Stephen Hemminger
2020-07-22  4:08   ` Varghese, Vipin
2020-07-28 14:51     ` Dikshant Chitkara
2020-07-28 16:23       ` Stephen Hemminger
2020-07-28 16:41         ` Dikshant Chitkara
2020-07-28 17:03           ` Stephen Hemminger
2020-07-28 17:08             ` Dikshant Chitkara
2020-07-29  0:59       ` Varghese, Vipin
2020-07-29  9:14         ` Dikshant Chitkara
2020-07-29  9:51           ` Varghese, Vipin
2020-07-29  9:56             ` Varghese, Vipin
2020-07-29 14:08             ` Dikshant Chitkara
2020-07-30  2:35               ` Varghese, Vipin

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox