p4rt performance test application

[satish153]

p4rt_perf_test is a test application designed to assess the performance of a P4Runtime server across various P4 profiles. The application's primary focus is on measuring the time required to program a specified number of entries.

$IPDK_RECIPE/install/bin/p4rt_perf_test -t 1 -o 1 -n 4000000 -p 1
Total num of entries: 4000000
Number of threads: 1
Operation: 1
Test Profile: 1
Thread data - Core: 20 start_index: 0 num_entries: 4000000
count: 4000000
Num of entries added: 4000000
Time taken: 37.4511 seconds
number of entires per second: 106806

Note:
p4rt_perf.cc/h and p4rt_perf_simple_l2_demo.cc/h are new coded. The code in the rest of the files is repurposed from ovs-p4rt module.
Programming with multiple threads doesn't really work as Stratum currently supports 'write' by only the master.

[n-sandeep]

Hi @satish153 , any sample command on how to test this performance will be helpful
There are these options "t : o : n : p :", looks like all testing scale is based on these options.

[satish153]

Hi @satish153 , any sample command on how to test this performance will be helpful There are these options "t : o : n : p :", looks like all testing scale is based on these options.

Updated the description.

[ffoulkes]

I'm going to go ahead and submit this initial review now. I still need to review the code itself.

[ffoulkes]

Nuts. I meant to leave a clarifying comment when I closed my review.

The issues I'm chiefly concerned about (the "blockers") are the latent bugs:

• Missing input validation, especially where out-of-bounds values could lead to array overrun.
• Missing error returns, especially where continuing execution can lead to catastrophic failure.

Plus the compiler warnings.

[ffoulkes]

LGTM

The user guide needs some work, but that can be taken care of in a later commit.

[ffoulkes]

BTW, you need to do git commit -s to sign your commits.

The failed DCO check is because one or more of them are unsigned.

No need to try to fix this PR; I'll bypass the requirement at merge time. Please remember to sign your commits in the future.

[ffoulkes]

Change of plans (and Now for Something Completely Different): I've submitted a PR against your PR to bring the user guide in line with current documentation conventions.

[n-sandeep]

LGTM