> > As different hardware has different hash key sizes, querying it (in byte) > > per port was asked by users. Otherwise there is no convenient way to know > > the size of hash key which should be prepared. > > > > v2 changes: > > * Disabled the code changes by default, to avoid breaking ABI compatibility. > > > > v3 changes: > > * Moved the newly added element right after 'uint16_t reta_size', where it > > was a padding. So it will not break any ABI compatibility, and no need to > > disable the code changes by default. > > > > Helin Zhang (6): > > ethdev: add an field for querying hash key size > > e1000: fill the hash key size > > fm10k: fill the hash key size > > i40e: fill the hash key size > > ixgbe: fill the hash key size > > app/testpmd: show the hash key size > > Acked-by: Konstantin Ananyev <konstantin.ananyev at intel.com>
Applied, thanks It is assumed that inserting a new field in a padding alignment won't break the ABI.
