Hi Ilya,
Thanks for reviewing our code.
We have 20+ threads indeed, so taking the same meter lock makes 'now'
not updated timely.
Using lockless meter to police traffic will be a perfect solution. :)
Thanks a lot.
On 6/22/2023 6:35 AM, Ilya Maximets wrote:
On 6/21/23 18:07, Ilya Maximets
On 6/21/23 18:07, Ilya Maximets wrote:
> On 5/31/23 17:41, mit...@outlook.com wrote:
>> From: Lin Huang
>>
>> Currently, a meter's timestamp 'now' is set by 'pmd->ctx.now' which updated
>> by pmd_thread_ctx_time_update().
>>
>> Before processing of the new packet batch:
>> - dpif_netdev_execute()
On 5/31/23 17:41, mit...@outlook.com wrote:
> From: Lin Huang
>
> Currently, a meter's timestamp 'now' is set by 'pmd->ctx.now' which updated
> by pmd_thread_ctx_time_update().
>
> Before processing of the new packet batch:
> - dpif_netdev_execute()
> - dp_netdev_process_rxq_port()
>
> There
Hi/ilya,/
Could you please review my code?
On 5/31/2023 11:41 PM, mit...@outlook.com wrote:
From: Lin Huang
Currently, a meter's timestamp 'now' is set by 'pmd->ctx.now' which updated
by pmd_thread_ctx_time_update().
Before processing of the new packet batch:
- dpif_netdev_execute()
-
From: Lin Huang
Currently, a meter's timestamp 'now' is set by 'pmd->ctx.now' which updated
by pmd_thread_ctx_time_update().
Before processing of the new packet batch:
- dpif_netdev_execute()
- dp_netdev_process_rxq_port()
There is a problem when user want to police the rate to a low pps by
