If the final choice is for not supporting a way to retrieve the
config information on the API, we'll look for a place to keep a copy
of the parameters in our code.
IMO, this is not a performance critical path and it is not a difficult solution
to
store these values in the application. My suggestion is to skip adding the API
and store the values in the application.
Vladimir, what's your opinion?
Agree. Global vars or part of a global configuration could be used here.
Thank you. I think we are fine to go ahead with merging this patch.
Michel, I know it's a bit of churn so not zero effort, but is that
solution workable for you? The change in DPDK would not be backported,
so gatekeeper code would only need an update on updating to use DPDK 20.11.
It's workable.
Thank you for organizing this discussion, Kevin.
P.S. As you are using DPDK 19.08, we should talk about DPDK LTS but
let's leave that for another thread :-)
Sure.
