Hi Eelco,
On 12/4/2023 5:01 PM, Eelco Chaudron wrote:
On 3 Dec 2023, at 15:19, miter wrote:
Hi Eelco,
Some comments below.
On 9/19/2023 10:58 PM, Eelco Chaudron wrote:
On 26 Aug 2023, at 8:01, mit...@outlook.com wrote:
From: Lin Huang
OvS has supported packet-per-second policer which
On 3 Dec 2023, at 15:19, miter wrote:
> Hi Eelco,
>
>
> Some comments below.
>
>
> On 9/19/2023 10:58 PM, Eelco Chaudron wrote:
>> On 26 Aug 2023, at 8:01, mit...@outlook.com wrote:
>>
>>> From: Lin Huang
>>>
>>> OvS has supported packet-per-second policer which can be set at ingress
>>> and eg
Hi Eelco,
Some comments below.
On 9/19/2023 10:58 PM, Eelco Chaudron wrote:
On 26 Aug 2023, at 8:01, mit...@outlook.com wrote:
From: Lin Huang
OvS has supported packet-per-second policer which can be set at ingress
and egress side in kernel datapath. But the userspace datapath doesn't
sup
On 26 Aug 2023, at 8:01, mit...@outlook.com wrote:
From: Lin Huang
OvS has supported packet-per-second policer which can be set at
ingress
and egress side in kernel datapath. But the userspace datapath doesn't
support for ingress and egress packet-per-second policing now.
So, this patch add
Bleep bloop. Greetings miter, I am a robot and I have tried out your patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line is 84 characters long (recommended limit is 79)
#84 FILE: NEWS:66:
* Added new Qos t
From: Lin Huang
OvS has supported packet-per-second policer which can be set at ingress
and egress side in kernel datapath. But the userspace datapath doesn't
support for ingress and egress packet-per-second policing now.
So, this patch add support for userspace egress pps policing by using
nati
