Passing EAL parameters via grout command line or conf file
Robin Jarry
rjarry at redhat.com
Thu Nov 14 20:47:32 CET 2024
Adel Belkhiri, Nov 14, 2024 at 20:41:
> Hi Robin,
>
> Thank you for the quick response!
>
> I tried adding virtual interfaces to Grout, and it seems to be working
> well—thanks for the tip! I also reviewed main/dpdk.c and noticed that many
> EAL parameters are hardcoded. For now, I’ll add the parameter I need
> (--trace=lib.ethdev.*) directly in the source code.
>
> Actually, I'm analyzing the performance of DPDK applications using the DPDK
> trace library, and I'm planning to present a few use cases at an upcoming
> conference based on Grout. I think a CLI parameter in Grout to pass
> "additional EAL arguments" directly to DPDK would be a useful feature. I'll
> submit a feature suggestion for this on GitHub.
Great to hear that grout will have some coverage :) Please do share the
details of your conference if possible.
That seems like a very useful addition. Actually, what we could do is
append any unrecognized arguments directly to eal_init. So you don't
have to deal with shell escaping.
> Thanks again for your help!
Anytime.
More information about the grout
mailing list