[RFC] ethdev: fast path async flow API

[Ivan Malov]

Hi Dariusz,

I appreciate your response. All to the point.

I have to confess my question was inspired by the 23.11 merge commit
in OVS mailing list. I first thought that an obvious consumer for
the async flow API could have been OVS but saw no usage of it in
the current code. It was my impression that there had been some
patches in OVS already, waiting either for approval/testing or
for this particular optimisation to be accepted first.

So far I've been mistaken -- there are no such patches,
hence my question. Do we have real-world examples of
the async flow usage? Should it be tested somehow...

(I apologise in case I'm asking for too many clarifications).

Thank you.

On Wed, 3 Jan 2024, Dariusz Sosnowski wrote:

> Hi Ivan,
>
>> Hi Dariusz,
>>
>> I appreciate the proposal. You say that a reference PMD implementation will
>> be made available for 24.03 release. What about the applications?
>> Is this supposed to go to upstream code of some applications?
> No source code changes are required in applications which already use async flow APIs.
> API signatures are not changed in this proposal.
>
> Only the PMD changes are required.
> To be specific - callbacks for async flow APIs should not be put in rte_flow_ops,
> but registered by calling rte_flow_fp_ops_register().
>
> Best regards,
> Dariusz Sosnowski
>