[dpdk-users] dpdk-pdump: pdump_create_client_socket fails to run along with kni app

[dpdk-users] dpdk-pdump: pdump_create_client_socket fails to run along with kni app

[gowrishankar muthukrishnan]

Hi,
I am trying to run dpdk-pdump along with KNI app (in current master ie 
17.05
rc2). I find dpdk-pdump crashing as below.

KNI execution:

./examples/kni/build/kni -l 4,5,6,7 --socket-mem 1024 -- -P -p 0x3 
--config="(0,4,5),(1,6,7)"
EAL: Detected 32 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:0e:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
EAL:   using IOMMU type 1 (Type 1)
EAL: Ignore mapping IO port bar(2) addr: 2fc1
EAL: PCI device 0000:0e:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
EAL: Ignore mapping IO port bar(2) addr: 2fe1
APP: Initialising port 0 ...
KNI: pci: 0e:00:00      8086:10fb
APP: Initialising port 1 ...
KNI: pci: 0e:00:01      8086:10fb

Checking link status
.done
Port 0 Link Up - speed 10000 Mbps - full-duplex
Port 1 Link Up - speed 10000 Mbps - full-duplex
APP: Lcore 5 is writing to port 0
APP: Lcore 6 is reading from port 1
APP: Lcore 7 is writing to port 1
APP: Lcore 4 is reading from port 0

dpdk pdump execution:

dpdk-pdump -- --pdump 'port=0,queue=*,rx-dev=/tmp/rx.pcap'
EAL: Detected 32 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
EAL: PCI device 0000:0e:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
EAL: Ignore mapping IO port bar(2) addr: 2fc1
EAL: PCI device 0000:0e:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
EAL: Ignore mapping IO port bar(2) addr: 2fe1
PMD: Initializing pmd_pcap for net_pcap_rx_0
PMD: Creating pcap-backed ethdev on numa socket 4294967295
Port 2 MAC: 00 00 00 01 02 03
PDUMP: failed to send to server:Connection refused, 
pdump_create_client_socket:702
PDUMP: client request for pdump enable/disable failed
PDUMP: failed to send to server:Connection refused, 
pdump_create_client_socket:702
PDUMP: client request for pdump enable/disable failed
EAL: Error - exiting with code: 1
   Cause: Unknown error -1

Has this worked before with KNI  or I am doing something not supported ?.
Before checking further, I just wanted to check with anyone 
trying/fixing it.

Thanks,
Gowrishankar

Re: [dpdk-users] dpdk-pdump: pdump_create_client_socket fails to run along with kni app

[Pattan, Reshma]

Hi Gowrishankar,

> PDUMP: failed to send to server:Connection refused,
> pdump_create_client_socket:702
> PDUMP: client request for pdump enable/disable failed
> PDUMP: failed to send to server:Connection refused,
> pdump_create_client_socket:702
> PDUMP: client request for pdump enable/disable failed

Primary application here kni should initialize packet capture framework using rte_pdump_init(). And uninitialize rte_pdump_uninit() before application terminates.
In DPDK by default only testpmd  has init/uninit changes added. Rest other application that wants to use pdump should do these changes explicitly, make the build and
rerun the primary and dpdk-pdump applications.

Please refer app/test-pmd/testpmd.c for rte_pdump* code changes and make similar change in kni main.c and retest.

Let me know if you stuck.

Thanks,
Reshma


> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of gowrishankar
> muthukrishnan
> Sent: Friday, April 21, 2017 11:11 AM
> To: users@dpdk.org
> Subject: [dpdk-users] dpdk-pdump: pdump_create_client_socket fails to run
> along with kni app
> 
> Hi,
> I am trying to run dpdk-pdump along with KNI app (in current master ie
> 17.05
> rc2). I find dpdk-pdump crashing as below.
> 
> KNI execution:
> 
> ./examples/kni/build/kni -l 4,5,6,7 --socket-mem 1024 -- -P -p 0x3 --
> config="(0,4,5),(1,6,7)"
> EAL: Detected 32 lcore(s)
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: PCI device 0000:0e:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:10fb net_ixgbe
> EAL:   using IOMMU type 1 (Type 1)
> EAL: Ignore mapping IO port bar(2) addr: 2fc1
> EAL: PCI device 0000:0e:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:10fb net_ixgbe
> EAL: Ignore mapping IO port bar(2) addr: 2fe1
> APP: Initialising port 0 ...
> KNI: pci: 0e:00:00      8086:10fb
> APP: Initialising port 1 ...
> KNI: pci: 0e:00:01      8086:10fb
> 
> Checking link status
> .done
> Port 0 Link Up - speed 10000 Mbps - full-duplex Port 1 Link Up - speed 10000
> Mbps - full-duplex
> APP: Lcore 5 is writing to port 0
> APP: Lcore 6 is reading from port 1
> APP: Lcore 7 is writing to port 1
> APP: Lcore 4 is reading from port 0
> 
> dpdk pdump execution:
> 
> dpdk-pdump -- --pdump 'port=0,queue=*,rx-dev=/tmp/rx.pcap'
> EAL: Detected 32 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
> EAL: PCI device 0000:0e:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:10fb net_ixgbe
> EAL: Ignore mapping IO port bar(2) addr: 2fc1
> EAL: PCI device 0000:0e:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:10fb net_ixgbe
> EAL: Ignore mapping IO port bar(2) addr: 2fe1
> PMD: Initializing pmd_pcap for net_pcap_rx_0
> PMD: Creating pcap-backed ethdev on numa socket 4294967295 Port 2 MAC:
> 00 00 00 01 02 03
> PDUMP: failed to send to server:Connection refused,
> pdump_create_client_socket:702
> PDUMP: client request for pdump enable/disable failed
> PDUMP: failed to send to server:Connection refused,
> pdump_create_client_socket:702
> PDUMP: client request for pdump enable/disable failed
> EAL: Error - exiting with code: 1
>    Cause: Unknown error -1
> 
> Has this worked before with KNI  or I am doing something not supported ?.
> Before checking further, I just wanted to check with anyone trying/fixing it.
> 
> Thanks,
> Gowrishankar
> 

Re: [dpdk-users] dpdk-pdump: pdump_create_client_socket fails to run along with kni app

[gowrishankar muthukrishnan]

On Monday 24 April 2017 02:45 PM, Pattan, Reshma wrote:
> Hi Gowrishankar,
>
>> PDUMP: failed to send to server:Connection refused,
>> pdump_create_client_socket:702
>> PDUMP: client request for pdump enable/disable failed
>> PDUMP: failed to send to server:Connection refused,
>> pdump_create_client_socket:702
>> PDUMP: client request for pdump enable/disable failed
> Primary application here kni should initialize packet capture framework using rte_pdump_init(). And uninitialize rte_pdump_uninit() before application terminates.
> In DPDK by default only testpmd  has init/uninit changes added. Rest other application that wants to use pdump should do these changes explicitly, make the build and
> rerun the primary and dpdk-pdump applications.
>
> Please refer app/test-pmd/testpmd.c for rte_pdump* code changes and make similar change in kni main.c and retest.
>
> Let me know if you stuck.

Thanks Reshma. It works after I call its init.

Regards,
Gowrishankar

>
> Thanks,
> Reshma
>
>
>> -----Original Message-----
>> From: users [mailto:users-bounces@dpdk.org] On Behalf Of gowrishankar
>> muthukrishnan
>> Sent: Friday, April 21, 2017 11:11 AM
>> To: users@dpdk.org
>> Subject: [dpdk-users] dpdk-pdump: pdump_create_client_socket fails to run
>> along with kni app
>>
>> Hi,
>> I am trying to run dpdk-pdump along with KNI app (in current master ie
>> 17.05
>> rc2). I find dpdk-pdump crashing as below.
>>
>> KNI execution:
>>
>> ./examples/kni/build/kni -l 4,5,6,7 --socket-mem 1024 -- -P -p 0x3 --
>> config="(0,4,5),(1,6,7)"
>> EAL: Detected 32 lcore(s)
>> EAL: No free hugepages reported in hugepages-1048576kB
>> EAL: Probing VFIO support...
>> EAL: VFIO support initialized
>> EAL: PCI device 0000:0e:00.0 on NUMA socket 0
>> EAL:   probe driver: 8086:10fb net_ixgbe
>> EAL:   using IOMMU type 1 (Type 1)
>> EAL: Ignore mapping IO port bar(2) addr: 2fc1
>> EAL: PCI device 0000:0e:00.1 on NUMA socket 0
>> EAL:   probe driver: 8086:10fb net_ixgbe
>> EAL: Ignore mapping IO port bar(2) addr: 2fe1
>> APP: Initialising port 0 ...
>> KNI: pci: 0e:00:00      8086:10fb
>> APP: Initialising port 1 ...
>> KNI: pci: 0e:00:01      8086:10fb
>>
>> Checking link status
>> .done
>> Port 0 Link Up - speed 10000 Mbps - full-duplex Port 1 Link Up - speed 10000
>> Mbps - full-duplex
>> APP: Lcore 5 is writing to port 0
>> APP: Lcore 6 is reading from port 1
>> APP: Lcore 7 is writing to port 1
>> APP: Lcore 4 is reading from port 0
>>
>> dpdk pdump execution:
>>
>> dpdk-pdump -- --pdump 'port=0,queue=*,rx-dev=/tmp/rx.pcap'
>> EAL: Detected 32 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
>> EAL: PCI device 0000:0e:00.0 on NUMA socket 0
>> EAL:   probe driver: 8086:10fb net_ixgbe
>> EAL: Ignore mapping IO port bar(2) addr: 2fc1
>> EAL: PCI device 0000:0e:00.1 on NUMA socket 0
>> EAL:   probe driver: 8086:10fb net_ixgbe
>> EAL: Ignore mapping IO port bar(2) addr: 2fe1
>> PMD: Initializing pmd_pcap for net_pcap_rx_0
>> PMD: Creating pcap-backed ethdev on numa socket 4294967295 Port 2 MAC:
>> 00 00 00 01 02 03
>> PDUMP: failed to send to server:Connection refused,
>> pdump_create_client_socket:702
>> PDUMP: client request for pdump enable/disable failed
>> PDUMP: failed to send to server:Connection refused,
>> pdump_create_client_socket:702
>> PDUMP: client request for pdump enable/disable failed
>> EAL: Error - exiting with code: 1
>>     Cause: Unknown error -1
>>
>> Has this worked before with KNI  or I am doing something not supported ?.
>> Before checking further, I just wanted to check with anyone trying/fixing it.
>>
>> Thanks,
>> Gowrishankar
>>