On 01.08.2017 18:45, Bodireddy, Bhanuprakash wrote:
>>On 28.07.2017 10:20, Darrell Ball wrote:
>>> I have not tested yet
>>>
>>> However, I would have expected something max latency config. to be
>> specific to netdev-dpdk port types
>>
>>IMHO, if we can make it generic, we must
>On 28.07.2017 10:20, Darrell Ball wrote:
>> I have not tested yet
>>
>> However, I would have expected something max latency config. to be
>specific to netdev-dpdk port types
>
>IMHO, if we can make it generic, we must make it generic.
>
>[Darrell]
>The first question I ask mys
-Original Message-
From: Ilya Maximets
Date: Monday, July 31, 2017 at 8:37 AM
To: Darrell Ball , "ovs-dev@openvswitch.org"
, Bhanuprakash Bodireddy
Cc: Heetae Ahn , Ben Pfaff , Antonio
Fischetti , Eelco Chaudron ,
Ciara Loftus , Kevin Traynor
Subject: Re: [PATCH RFC v2 4/4] dpif-ne
On 28.07.2017 10:20, Darrell Ball wrote:
> I have not tested yet
>
> However, I would have expected something max latency config. to be specific
> to netdev-dpdk port types
IMHO, if we can make it generic, we must make it generic. Making of this
functionality netdev-dpdk specific will brake abil
I have not tested yet
However, I would have expected something max latency config. to be specific to
netdev-dpdk port types
This type of code also seems to intersect with present and future QoS
considerations in netdev-dpdk
-Original Message-
From: Ilya Maximets
Date: Wednesday, Jul
This allows to collect packets from more than one RX burst
and send them together with a configurable maximum latency.
'other_config:output-max-latency' can be used to configure
time that a packet can wait in output batch for sending.
Signed-off-by: Ilya Maximets
---
millisecon granularity is u
