On Wed, Nov 2, 2022 at 11:58 AM Akhil Goyal <gak...@marvell.com> wrote: > > This is being flagged as an ABI break for 21.11.3 [1]. I don't see it > > mentioned in the commit message or discussed, is it ok for main branch? > > Ok, we can keep it to main only. > But it will be an issue on 21.11. > > > > > Thanks to Ali for reporting. I will revert on 21.11 branch. > > > > [1] > > 1 Changed variable: > > > > [C] 'const char* rte_crypto_auth_algorithm_strings[]' was changed at > > rte_crypto_sym.h:372:1: > > size of symbol changed from 168 to 232
My two cents. We have a algo "string to num" helper (rte_cryptodev_get_auth_algo_enum). This code is not performance sensitive, is it? If we add the, opposite, "num to string" helper, we can hide the rte_crypto_auth_algorithm_strings symbol from the public ABI and avoid this kind of issues in the future. And looking at lib/crypto map, there are other arrays (*_strings symbols) that are subject to similar "extending" issues. We are late in the release for adding new API though such helpers would be really simple. Hiding such symbols is something to consider before entering ABI freeze. -- David Marchand
