macro ?APP_METADATA_OFFSET? was not used to initialize ?signature_offset? and ?key_offset? part of struct rte_table_hash_lru_params. Instead integer offset values were directly used.
with this fix 'hash-8-lru', 'hash-16-lru', 'hash-32-lru' table types are able to forward traffic as expected. Fixes: 48f31ca50cc4 ("app/pipeline: packet framework benchmark") Signed-off-by: Sankar Chokkalingam <sankarx.chokkalingam at intel.com> Signed-off-by: Guruprasad Rao <guruprasadx.rao at intel.com> --- app/test-pipeline/pipeline_hash.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/app/test-pipeline/pipeline_hash.c b/app/test-pipeline/pipeline_hash.c index f8aac0d..0e369a2 100644 --- a/app/test-pipeline/pipeline_hash.c +++ b/app/test-pipeline/pipeline_hash.c @@ -190,8 +190,8 @@ app_main_loop_worker_pipeline_hash(void) { .n_buckets = 1 << 22, .f_hash = test_hash, .seed = 0, - .signature_offset = 0, - .key_offset = 32, + .signature_offset = APP_METADATA_OFFSET(0), + .key_offset = APP_METADATA_OFFSET(32), }; struct rte_pipeline_table_params table_params = { -- 2.5.0