Hanoh Haim

@MaciejWachowski this is expected, Intel is looking into this issue. To elaborate more, TRex has a hardware filter that redirect latency packet (packets with TOS&0x01==0x01) to Rx core, this filter...

The solution should be backward compatible

We have a few setups (~40). every setup is with different distro/NICs/firmware/ The documents is a bit old and we can't track all the distro/firmware/hardware combination We observed that Mellanox...

need to check if ```bool Reschedule() {``` is called from CP->Rx() in the CP() context

@adam-kulagowski i think this is a good idea. Should be optional using a new field. Do you have a PR?

@jayakumarramisetty this is a design issue. You don't need to add more **flows** to the trex_cfg. For a single profile we need a single long operation to compile (because we...

@jayakumarramisetty for generating 1M flows it is better to use Field Engine that can scale better (with one stream you can do it)

@RainyBow this is not supported in current version

@tbarbette TRex works with specific DPDK and specific OFED version and specific distro Have a look into Mellanox appendix one the main manual

Hi @tmonjalo We wanted to provide to our user a unified tested source code and package. When we started there were a few patchs in DPDK (e.g. mlx5 driver )...