> >> On 11/17/20 10:18 PM, Gregory Etelson wrote:
> >>> There is a discrepancy between RTE ETHDEV API and flow rules guide
> >>> regarding flow rules maintenance after port stop. RTE ETHDEV API in
> >>> librte_ethdev.h declares that flow rules will not be stored in PMD
> >>> after port stop:
> >>>
On 11/18/20 11:59 AM, Gregory Etelson wrote:
> Hello Andrew,
>
>> On 11/17/20 10:18 PM, Gregory Etelson wrote:
>>> There is a discrepancy between RTE ETHDEV API and flow rules guide
>>> regarding flow rules maintenance after port stop. RTE ETHDEV API in
>>> librte_ethdev.h declares that flow rule
Hello Andrew,
> On 11/17/20 10:18 PM, Gregory Etelson wrote:
> > There is a discrepancy between RTE ETHDEV API and flow rules guide
> > regarding flow rules maintenance after port stop. RTE ETHDEV API in
> > librte_ethdev.h declares that flow rules will not be stored in PMD
> > after port stop:
>
On 11/17/20 10:18 PM, Gregory Etelson wrote:
There is a discrepancy between RTE ETHDEV API and flow rules guide
regarding flow rules maintenance after port stop. RTE ETHDEV API in
librte_ethdev.h declares that flow rules will not be stored in PMD
after port stop:
> Quite start
Please not
There is a discrepancy between RTE ETHDEV API and flow rules guide
regarding flow rules maintenance after port stop. RTE ETHDEV API in
librte_ethdev.h declares that flow rules will not be stored in PMD
after port stop:
> Quite start
Please note that some configuration is not stored between c
There is a discrepancy between RTE ETHDEV API and flow rules guide
regarding flow rules maintenance after port stop. RTE ETHDEV API in
librte_ethdev.h declares that flow rules will not be stored in PMD
after port stop:
> Quite start
Please note that some configuration is not stored between c
6 matches
Mail list logo