6] dpif-netdev: Avoid reordering of packets in
>a batch with same megaflow
>
>master.
>
>Hi, Ian, everyone.
>It's ok to merge. I still don't like the change, but I'll get along with it.
>P.S. Current version can not be applied cleanly, minor rebase requ
On 22.08.2018 15:30, Stokes, Ian wrote:
>> On 7/27/2018 7:26 PM, Vishal Deep Ajmera wrote:
>>> OVS reads packets in batches from a given port and packets in the
>>> batch are subjected to potentially 3 levels of lookups to identify the
>>> datapath megaflow entry (or flow) associated with the packe
> On 7/27/2018 7:26 PM, Vishal Deep Ajmera wrote:
> > OVS reads packets in batches from a given port and packets in the
> > batch are subjected to potentially 3 levels of lookups to identify the
> > datapath megaflow entry (or flow) associated with the packet.
> > Each megaflow entry has a dedicate
On 08.08.2018 12:06, Ian Stokes wrote:
> On 7/27/2018 7:26 PM, Vishal Deep Ajmera wrote:
>> OVS reads packets in batches from a given port and packets in the
>> batch are subjected to potentially 3 levels of lookups to identify
>> the datapath megaflow entry (or flow) associated with the packet.
>>
On 7/27/2018 7:26 PM, Vishal Deep Ajmera wrote:
OVS reads packets in batches from a given port and packets in the
batch are subjected to potentially 3 levels of lookups to identify
the datapath megaflow entry (or flow) associated with the packet.
Each megaflow entry has a dedicated buffer in whic
OVS reads packets in batches from a given port and packets in the
batch are subjected to potentially 3 levels of lookups to identify
the datapath megaflow entry (or flow) associated with the packet.
Each megaflow entry has a dedicated buffer in which packets that match
the flow classification crite
