] ethdev: queue-based flow aged report
On 6/2/22 14:10, Ori Kam wrote:
Hi,
Hello,
-Original Message-
From: Andrew Rybchenko
<mailto:andrew.rybche...@oktetlabs.ru>
Sent: Wednesday, June 1, 2022 9:21 PM
Subject: Re: [RFC v2 2/2] ethdev: queue-based flow aged report
Again, summar
On 6/2/22 14:10, Ori Kam wrote:
Hi,
Hello,
-Original Message-
From: Andrew Rybchenko
Sent: Wednesday, June 1, 2022 9:21 PM
Subject: Re: [RFC v2 2/2] ethdev: queue-based flow aged report
Again, summary must not be a statement.
On 6/1/22 10:39, Xiaoyu Min wrote:
When application use
On 6/2/22 02:21, Andrew Rybchenko wrote:
Again, summary must not be a statement.
I'l re-phrase it.
On 6/1/22 10:39, Xiaoyu Min wrote:
When application use queue-based flow rule management and operate the
same flow rule on the same queue, e.g create/destroy/query, API of
querying aged flow rule
Hi,
> -Original Message-
> From: Andrew Rybchenko
> Sent: Wednesday, June 1, 2022 9:21 PM
> Subject: Re: [RFC v2 2/2] ethdev: queue-based flow aged report
>
> Again, summary must not be a statement.
>
> On 6/1/22 10:39, Xiaoyu Min wrote:
> > When applica
Again, summary must not be a statement.
On 6/1/22 10:39, Xiaoyu Min wrote:
When application use queue-based flow rule management and operate the
same flow rule on the same queue, e.g create/destroy/query, API of
querying aged flow rules should also have queue id parameter just like
other queue-b
When application use queue-based flow rule management and operate the
same flow rule on the same queue, e.g create/destroy/query, API of
querying aged flow rules should also have queue id parameter just like
other queue-based flow APIs.
By this way, PMD can work in more optimized way since resourc
6 matches
Mail list logo
