[dpdk-users] error running two instances of pktgen

[dpdk-users] error running two instances of pktgen

[Stefano Salsano]

Hi,

we are trying to run two instances of pktgen-dpdk on the same host, each 
one working on one network interface

we use the following commands to run pktgen:

sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen -l 0-4 -n 3 
--file-prefix pg1 -b 06:00.1 -- -P -m "1.0"

sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen -l 5-8 -n 3 
--file-prefix pg0 -b 06:00.0 -- -P -m "1.0"

each one is working separately, but if we run the second one when the 
first one is running (or vice-versa), we receive this error :

     Create: Default TX  0:0  - Memory used (MBUFs 16384 x (size 2176 + 
Hdr 128)) + 192 =  36865 KB, headroom 128
!PANIC!: Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, 
nb_mbufs 16384, socket_id 0: No such file or directory
PANIC in pktgen_mbuf_pool_create():
Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, nb_mbufs 
16384, socket_id 0: No such file or directory6: 
[./app/x86_64-native-linuxapp-gcc/pktgen(_start+0x29) [0x466139]]
5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) 
[0x7fb458c89830]]
4: [./app/x86_64-native-linuxapp-gcc/pktgen(main+0x598) [0x460388]]
3: [./app/x86_64-native-linuxapp-gcc/pktgen(pktgen_config_ports+0x18ad) 
[0x491aed]]
2: [./app/x86_64-native-linuxapp-gcc/pktgen(__rte_panic+0xc3) [0x45769b]]
1: [./app/x86_64-native-linuxapp-gcc/pktgen(rte_dump_stack+0x2b) [0x50aadb]]

we are using
-- Pktgen Ver: 3.5.1 (DPDK 18.08.0-rc0)  Powered by DPDK
** Version: DPDK 18.08.0-rc0, Command Line Interface with timers

are we doing something wrong?

Stefano

-- 
*******************************************************************
Stefano Salsano
Professore Associato
Dipartimento Ingegneria Elettronica
Universita' di Roma Tor Vergata
Viale Politecnico, 1 - 00133 Roma - ITALY

http://netgroup.uniroma2.it/Stefano_Salsano/

E-mail  : stefano.salsano@uniroma2.it
Cell.   : +39 320 4307310
Office  : (Tel.) +39 06 72597770 (Fax.) +39 06 72597435
*******************************************************************

Re: [dpdk-users] error running two instances of pktgen

[Muhammad Zain-ul-Abideen]

I dont think that there is currently support of multi-instances. You
can make primary and secondary processes, for that you need to change
the memzone and mempool config.
You can launch pktgen with multiple interfaces in same app. if you
want to launch two instances, you may have to change the init(), e.g.
you can see multi_process->client_server_mp in examples.

I hope this helps

Re: [dpdk-users] error running two instances of pktgen

[Stefano Salsano]

Il 2018-06-28 09:05, Muhammad Zain-ul-Abideen ha scritto:
> I dont think that there is currently support of multi-instances. 

Hi Muhammad,

the support for multiple instances is described here

http://pktgen-dpdk.readthedocs.io/en/latest/usage_pktgen.html#multiple-instances-of-pktgen-or-other-application

but I am not able to run it :-(

Stefano

You
> can make primary and secondary processes, for that you need to change
> the memzone and mempool config.
> You can launch pktgen with multiple interfaces in same app. if you
> want to launch two instances, you may have to change the init(), e.g.
> you can see multi_process->client_server_mp in examples.
> 
> I hope this helps
> 


-- 
*******************************************************************
Stefano Salsano
Professore Associato
Dipartimento Ingegneria Elettronica
Universita' di Roma Tor Vergata
Viale Politecnico, 1 - 00133 Roma - ITALY

http://netgroup.uniroma2.it/Stefano_Salsano/

E-mail  : stefano.salsano@uniroma2.it
Cell.   : +39 320 4307310
Office  : (Tel.) +39 06 72597770 (Fax.) +39 06 72597435
*******************************************************************

Re: [dpdk-users] error running two instances of pktgen

[Muhammad Zain-ul-Abideen]

Dear Stefano,
It clearly states in second para

*"Setup if pktgen and your application you have to startup each one a bit
differently to make sure they share the resources like memory and the
ports. I will use two Pktgen running on the same machine, which just means
you have to setup your application as one of the applications.*"
You can do that use these cli arguments

--proc-type auto

Re: [dpdk-users] error running two instances of pktgen

[Stefano Salsano]

Il 2018-06-28 09:33, Muhammad Zain-ul-Abideen ha scritto:
> Dear Stefano,
> It clearly states in second para
> 
> *"Setup if pktgen and your application you have to startup each one a 
> bit differently to make sure they share the resources like memory and 
> the ports. I will use two Pktgen running on the same machine, which just 
> means you have to setup your application as one of the applications.*"
> You can do that use these cli arguments
> 
> --proc-type auto
> 

Dear Muhammad,
thank you for your help!

I've now tried to run

sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen -l 5-8 -n 3 
--file-prefix pg0 --proc-type auto -b 06:00.0 -- -P -m "1.0"

and then

sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen -l 0-4 -n 3 
--file-prefix pg1 --proc-type auto -b 06:00.1 -- -P -m "1.0"

but I keep receiving the same error (see below)

in the output text I find for both cases:
EAL: Auto-detected process type: PRIMARY

so I tried to set --proc-type secondary in the second command
I first received an error suggesting "It is recommended to disable ASLR 
in the kernel", which I did with  "echo 0 | sudo tee 
/proc/sys/kernel/randomize_va_space"

now I receive the following error in the second command with --proc-type 
secondary

EAL: Detected 32 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/pg1/mp_socket_12222_2a4c8375d5acf8
EAL: failed to send to (/var/run/dpdk/pg1/mp_socket) due to Connection 
refused
EAL: Fail to send request /var/run/dpdk/pg1/mp_socket:bus_vdev_mp
vdev_scan(): Failed to request vdev from primary
EAL: Probing VFIO support...
EAL: Could not map memory from primary process
EAL: FATAL: Cannot init memory

EAL: Cannot init memory

any further suggestion ?

thank you
Stefano



-------------
error with --proc-type auto

Create: Default TX  0:0  - Memory used (MBUFs 16384 x (size 2176 + Hdr 
128)) + 192 =  36865 KB, headroom 128
!PANIC!: Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, 
nb_mbufs 16384, socket_id 0: No such file or directory
PANIC in pktgen_mbuf_pool_create():
Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, nb_mbufs 
16384, socket_id 0: No such file or directory6: 
[./app/x86_64-native-linuxapp-gcc/pktgen(_start+0x29) [0x466139]]
5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) 
[0x7fb5a4913830]]
4: [./app/x86_64-native-linuxapp-gcc/pktgen(main+0x598) [0x460388]]
3: [./app/x86_64-native-linuxapp-gcc/pktgen(pktgen_config_ports+0x18ad) 
[0x491aed]]
2: [./app/x86_64-native-linuxapp-gcc/pktgen(__rte_panic+0xc3) [0x45769b]]
1: [./app/x86_64-native-linuxapp-gcc/pktgen(rte_dump_stack+0x2b) [0x50aadb]]
Aborted




-- 
*******************************************************************
Stefano Salsano
Professore Associato
Dipartimento Ingegneria Elettronica
Universita' di Roma Tor Vergata
Viale Politecnico, 1 - 00133 Roma - ITALY

http://netgroup.uniroma2.it/Stefano_Salsano/

E-mail  : stefano.salsano@uniroma2.it
Cell.   : +39 320 4307310
Office  : (Tel.) +39 06 72597770 (Fax.) +39 06 72597435
*******************************************************************

Re: [dpdk-users] error running two instances of pktgen

[Muhammad Zain-ul-Abideen]

 I think it is some sort of cli command issue now, like socket-mem or
blacklisting the port.

Adding Keith Wiles, the father of pktgen

Re: [dpdk-users] error running two instances of pktgen

[Stefano Salsano]

Il 2018-06-28 10:32, Muhammad Zain-ul-Abideen ha scritto:
> I think it is some sort of cli command issue now, like socket-mem or 
> blacklisting the port.
> 
> Adding Keith Wiles, the father of pktgen

thank you Muhammad, here is the commands that we run now and the overall 
recap of the problems

sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen  -l 5-8 -n 3 
--file-prefix pg0 --proc-type auto -b 06:00.0 -- -P -m "6.0"

it works, then we have the error in the second instance:

sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen -l 0-4 -n 3 
--file-prefix pg1 --proc-type secondary -b 06:00.1 -- -P -m "1.0"

EAL: Detected 32 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/pg1/mp_socket_12381_2a519caf5992b0
EAL: failed to send to (/var/run/dpdk/pg1/mp_socket) due to Connection 
refused
EAL: Fail to send request /var/run/dpdk/pg1/mp_socket:bus_vdev_mp
vdev_scan(): Failed to request vdev from primary
EAL: Probing VFIO support...
EAL: Could not map memory from primary process
EAL: FATAL: Cannot init memory

EAL: Cannot init memory

I don't know if it is relevant, but when running the first command I get 
a warning about hugepages (and then the pktgen works well)
EAL: Detected 32 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Auto-detected process type: PRIMARY
EAL: Multi-process socket /var/run/dpdk/pg0/mp_socket
EAL: No free hugepages reported in hugepages-1048576kB


if I run both instances with --port-type auto it detects primary mode 
for both
EAL: Detected 32 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Auto-detected process type: PRIMARY
EAL: Multi-process socket /var/run/dpdk/pg1/mp_socket
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...

and then the second instance fails like this
     Create: Default TX  0:0  - Memory used (MBUFs 16384 x (size 2176 + 
Hdr 128)) + 192 =  36865 KB, headroom 128
!PANIC!: Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, 
nb_mbufs 16384, socket_id 0: No such file or directory
PANIC in pktgen_mbuf_pool_create():
Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, nb_mbufs 
16384, socket_id 0: No such file or directory6: 
[./app/x86_64-native-linuxapp-gcc/pktgen(_start+0x29) [0x466139]]
5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) 
[0x7ffff6cae830]]
4: [./app/x86_64-native-linuxapp-gcc/pktgen(main+0x598) [0x460388]]
3: [./app/x86_64-native-linuxapp-gcc/pktgen(pktgen_config_ports+0x18ad) 
[0x491aed]]
2: [./app/x86_64-native-linuxapp-gcc/pktgen(__rte_panic+0xc3) [0x45769b]]
1: [./app/x86_64-native-linuxapp-gcc/pktgen(rte_dump_stack+0x2b) [0x50aadb]]
Aborted


-- 
*******************************************************************
Stefano Salsano
Professore Associato
Dipartimento Ingegneria Elettronica
Universita' di Roma Tor Vergata
Viale Politecnico, 1 - 00133 Roma - ITALY

http://netgroup.uniroma2.it/Stefano_Salsano/

E-mail  : stefano.salsano@uniroma2.it
Cell.   : +39 320 4307310
Office  : (Tel.) +39 06 72597770 (Fax.) +39 06 72597435
*******************************************************************

Re: [dpdk-users] error running two instances of pktgen

[Wiles, Keith]

> On Jun 28, 2018, at 3:53 AM, Stefano Salsano <stefano.salsano@uniroma2.it> wrote:
> 
> Il 2018-06-28 10:32, Muhammad Zain-ul-Abideen ha scritto:
>> I think it is some sort of cli command issue now, like socket-mem or blacklisting the port.
>> Adding Keith Wiles, the father of pktgen
> 
> thank you Muhammad, here is the commands that we run now and the overall recap of the problems
> 
> sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen  -l 5-8 -n 3 --file-prefix pg0 --proc-type auto -b 06:00.0 -- -P -m "6.0"
> 
> it works, then we have the error in the second instance:
> 
> sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen -l 0-4 -n 3 --file-prefix pg1 --proc-type secondary -b 06:00.1 -- -P -m “1.0"

Pktgen does support two or more pktgen instances but only as primary processes, which means pktgen can not be run in secondary mode so using —proc-type auto will not work.

I run pktgen as two primary processes all of the time, but I do not use the option —proc-type at all.

The problem you above looks good until you get to the ‘-m 1.0’ option. The 1 in this case denotes the lcore to use. In the above command you seemed to have corrected the problem as you were using 1.0 for both commands. Now you are using 6 and 1.

Try removing the —proc-type options and give that a try.

> 
> EAL: Detected 32 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/pg1/mp_socket_12381_2a519caf5992b0
> EAL: failed to send to (/var/run/dpdk/pg1/mp_socket) due to Connection refused
> EAL: Fail to send request /var/run/dpdk/pg1/mp_socket:bus_vdev_mp
> vdev_scan(): Failed to request vdev from primary
> EAL: Probing VFIO support...
> EAL: Could not map memory from primary process
> EAL: FATAL: Cannot init memory
> 
> EAL: Cannot init memory
> 
> I don't know if it is relevant, but when running the first command I get a warning about hugepages (and then the pktgen works well)
> EAL: Detected 32 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Auto-detected process type: PRIMARY
> EAL: Multi-process socket /var/run/dpdk/pg0/mp_socket
> EAL: No free hugepages reported in hugepages-1048576kB
> 
> 
> if I run both instances with --port-type auto it detects primary mode for both
> EAL: Detected 32 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Auto-detected process type: PRIMARY
> EAL: Multi-process socket /var/run/dpdk/pg1/mp_socket
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> 
> and then the second instance fails like this
>    Create: Default TX  0:0  - Memory used (MBUFs 16384 x (size 2176 + Hdr 128)) + 192 =  36865 KB, headroom 128
> !PANIC!: Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, nb_mbufs 16384, socket_id 0: No such file or directory
> PANIC in pktgen_mbuf_pool_create():
> Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, nb_mbufs 16384, socket_id 0: No such file or directory6: [./app/x86_64-native-linuxapp-gcc/pktgen(_start+0x29) [0x466139]]
> 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7ffff6cae830]]
> 4: [./app/x86_64-native-linuxapp-gcc/pktgen(main+0x598) [0x460388]]
> 3: [./app/x86_64-native-linuxapp-gcc/pktgen(pktgen_config_ports+0x18ad) [0x491aed]]
> 2: [./app/x86_64-native-linuxapp-gcc/pktgen(__rte_panic+0xc3) [0x45769b]]
> 1: [./app/x86_64-native-linuxapp-gcc/pktgen(rte_dump_stack+0x2b) [0x50aadb]]
> Aborted
> 
> 
> -- 
> *******************************************************************
> Stefano Salsano
> Professore Associato
> Dipartimento Ingegneria Elettronica
> Universita' di Roma Tor Vergata
> Viale Politecnico, 1 - 00133 Roma - ITALY
> 
> http://netgroup.uniroma2.it/Stefano_Salsano/
> 
> E-mail  : stefano.salsano@uniroma2.it
> Cell.   : +39 320 4307310
> Office  : (Tel.) +39 06 72597770 (Fax.) +39 06 72597435
> *******************************************************************
> 

Regards,
Keith

Re: [dpdk-users] error running two instances of pktgen

[Wiles, Keith]

> On Jun 28, 2018, at 3:53 AM, Stefano Salsano <stefano.salsano@uniroma2.it> wrote:
> 
> Il 2018-06-28 10:32, Muhammad Zain-ul-Abideen ha scritto:
>> I think it is some sort of cli command issue now, like socket-mem or blacklisting the port.
>> Adding Keith Wiles, the father of pktgen
> 
> thank you Muhammad, here is the commands that we run now and the overall recap of the problems
> 
> sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen  -l 5-8 -n 3 --file-prefix pg0 --proc-type auto -b 06:00.0 -- -P -m "6.0"
> 
> it works, then we have the error in the second instance:
> 
> sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen -l 0-4 -n 3 --file-prefix pg1 --proc-type secondary -b 06:00.1 -- -P -m “1.0"

I read a bit more the of email :-)

If you do use —proc-type auto it fine as the —file-prefix being different will make them both primary processes.

Make sure you have enough memory allocated to support both instances of pktgen. I normally use the —socket-mem 512,512 in both commands, but this means I must have 2048 amount of huge pages allocated.

BTW, which version of pktgen and dpdk are you using, plus what OS.

> 
> EAL: Detected 32 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/pg1/mp_socket_12381_2a519caf5992b0
> EAL: failed to send to (/var/run/dpdk/pg1/mp_socket) due to Connection refused
> EAL: Fail to send request /var/run/dpdk/pg1/mp_socket:bus_vdev_mp
> vdev_scan(): Failed to request vdev from primary
> EAL: Probing VFIO support...
> EAL: Could not map memory from primary process
> EAL: FATAL: Cannot init memory
> 
> EAL: Cannot init memory
> 
> I don't know if it is relevant, but when running the first command I get a warning about hugepages (and then the pktgen works well)
> EAL: Detected 32 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Auto-detected process type: PRIMARY
> EAL: Multi-process socket /var/run/dpdk/pg0/mp_socket
> EAL: No free hugepages reported in hugepages-1048576kB
> 
> 
> if I run both instances with --port-type auto it detects primary mode for both
> EAL: Detected 32 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Auto-detected process type: PRIMARY
> EAL: Multi-process socket /var/run/dpdk/pg1/mp_socket
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> 
> and then the second instance fails like this
>    Create: Default TX  0:0  - Memory used (MBUFs 16384 x (size 2176 + Hdr 128)) + 192 =  36865 KB, headroom 128
> !PANIC!: Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, nb_mbufs 16384, socket_id 0: No such file or directory
> PANIC in pktgen_mbuf_pool_create():
> Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, nb_mbufs 16384, socket_id 0: No such file or directory6: [./app/x86_64-native-linuxapp-gcc/pktgen(_start+0x29) [0x466139]]
> 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7ffff6cae830]]
> 4: [./app/x86_64-native-linuxapp-gcc/pktgen(main+0x598) [0x460388]]
> 3: [./app/x86_64-native-linuxapp-gcc/pktgen(pktgen_config_ports+0x18ad) [0x491aed]]
> 2: [./app/x86_64-native-linuxapp-gcc/pktgen(__rte_panic+0xc3) [0x45769b]]
> 1: [./app/x86_64-native-linuxapp-gcc/pktgen(rte_dump_stack+0x2b) [0x50aadb]]
> Aborted
> 
> 
> -- 
> *******************************************************************
> Stefano Salsano
> Professore Associato
> Dipartimento Ingegneria Elettronica
> Universita' di Roma Tor Vergata
> Viale Politecnico, 1 - 00133 Roma - ITALY
> 
> http://netgroup.uniroma2.it/Stefano_Salsano/
> 
> E-mail  : stefano.salsano@uniroma2.it
> Cell.   : +39 320 4307310
> Office  : (Tel.) +39 06 72597770 (Fax.) +39 06 72597435
> *******************************************************************
> 

Regards,
Keith

Re: [dpdk-users] error running two instances of pktgen

[Muhammad Zain-ul-Abideen]

On Thu, Jun 28, 2018 at 1:12 PM Stefano Salsano <stefano.salsano@uniroma2.it>
wrote:

> Il 2018-06-28 09:33, Muhammad Zain-ul-Abideen ha scritto:
> > Dear Stefano,
> > It clearly states in second para
> >
> > *"Setup if pktgen and your application you have to startup each one a
> > bit differently to make sure they share the resources like memory and
> > the ports. I will use two Pktgen running on the same machine, which just
> > means you have to setup your application as one of the applications.*"
> > You can do that use these cli arguments
> >
> > --proc-type auto
> >
>
> Dear Muhammad,
> thank you for your help!
>
> I've now tried to run
>
> sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen -l 5-8 -n 3
> --file-prefix pg0 --proc-type auto -b 06:00.0 -- -P -m "1.0"
>
> and then
>
> sudo -E ./app/x86_64-native-linuxapp-gcc/pktgen -l 0-4 -n 3
> --file-prefix pg1 --proc-type auto -b 06:00.1 -- -P -m "1.0"
>
> but I keep receiving the same error (see below)
>
> in the output text I find for both cases:
> EAL: Auto-detected process type: PRIMARY
>
> so I tried to set --proc-type secondary in the second command
> I first received an error suggesting "It is recommended to disable ASLR
> in the kernel", which I did with  "echo 0 | sudo tee
> /proc/sys/kernel/randomize_va_space"
>
> now I receive the following error in the second command with --proc-type
> secondary
>
> EAL: Detected 32 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/pg1/mp_socket_12222_2a4c8375d5acf8
> EAL: failed to send to (/var/run/dpdk/pg1/mp_socket) due to Connection
> refused
> EAL: Fail to send request /var/run/dpdk/pg1/mp_socket:bus_vdev_mp
> vdev_scan(): Failed to request vdev from primary
> EAL: Probing VFIO support...
> EAL: Could not map memory from primary process
> EAL: FATAL: Cannot init memory
>
> EAL: Cannot init memory
>
> any further suggestion ?
>
> thank you
> Stefano
>
>
>
> -------------
> error with --proc-type auto
>
> Create: Default TX  0:0  - Memory used (MBUFs 16384 x (size 2176 + Hdr
> 128)) + 192 =  36865 KB, headroom 128
> !PANIC!: Cannot create mbuf pool (Default TX  0:0) port 0, queue 0,
> nb_mbufs 16384, socket_id 0: No such file or directory
> PANIC in pktgen_mbuf_pool_create():
> Cannot create mbuf pool (Default TX  0:0) port 0, queue 0, nb_mbufs
> 16384, socket_id 0: No such file or directory6:
> [./app/x86_64-native-linuxapp-gcc/pktgen(_start+0x29) [0x466139]]
> 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)
> [0x7fb5a4913830]]
> 4: [./app/x86_64-native-linuxapp-gcc/pktgen(main+0x598) [0x460388]]
> 3: [./app/x86_64-native-linuxapp-gcc/pktgen(pktgen_config_ports+0x18ad)
> [0x491aed]]
> 2: [./app/x86_64-native-linuxapp-gcc/pktgen(__rte_panic+0xc3) [0x45769b]]
> 1: [./app/x86_64-native-linuxapp-gcc/pktgen(rte_dump_stack+0x2b)
> [0x50aadb]]
> Aborted
>
>
>
>
> --
> *******************************************************************
> Stefano Salsano
> Professore Associato
> Dipartimento Ingegneria Elettronica
> Universita' di Roma Tor Vergata
> Viale Politecnico, 1 - 00133 Roma - ITALY
>
> http://netgroup.uniroma2.it/Stefano_Salsano/
>
> E-mail  : stefano.salsano@uniroma2.it
> Cell.   : +39 320 4307310
> Office  : (Tel.) +39 06 72597770 (Fax.) +39 06 72597435
> *******************************************************************
>
>