Hello Ferruh,
I have two more clarification requests, can you please check them below? If one ore more flow failed to update, for any reason, should user retry the update (in that case we need a retry error maybe) and can user still call 'rte_flow_template_table_resize_complete()' (for possible next table resize operation)? Can you please clarify this in your document.
Please see my comment below.
When user calls update() with a flow from new table, API should ignore it and return success, you mentioned this is what mlx implementation is doing, what do you think to make this as default API behavior and document it in above API documentation?
I'll update the patch.
If 'rte_flow_template_table_resize_complete()' fails, can application call another resize()? Is this managed in the application level or driver level (by returning error to next resize if complete() is not successful)? Is it something to clarify in your document?
PMD failures in `rte_flow_async_update_resized()` and `rte_flow_template_table_resize_complete()` are not recoverable.
