This looks good, just one small thing inlined.
> -----Original Message----- > From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- > boun...@openvswitch.org] On Behalf Of Anand Kumar > Sent: Friday, March 24, 2017 10:51 PM > To: d...@openvswitch.org > Subject: [ovs-dev] [PATCH v6 3/5] datapath-windows: Retain MRU value in > the _OVS_BUFFER_CONTEXT. > > This patch introduces a new field MRU(Maximum Recieved Unit) in the > _OVS_BUFFER_CONTEXT and it is used only for Ip Fragments to retain MRU > for the reassembled IP datagram when the packet is forwarded to > userspace. > > Signed-off-by: Anand Kumar <kumaran...@vmware.com> > --- > v5->v6: No Change > v4->v5: > - Refactored the patch as MRU field is removed form > ovsForwardingContext. > - Added MRU field in _OVS_BUFFER_CONTEXT. > - Updated commit message. > v3->v4: No Change > v2->v3: No change > v1->v2: No change > --- a/datapath-windows/ovsext/BufferMgmt.h > +++ b/datapath-windows/ovsext/BufferMgmt.h > @@ -58,6 +58,7 @@ typedef union _OVS_BUFFER_CONTEXT { > UINT32 origDataLength; > UINT32 dataOffsetDelta; > }; > + UINT16 mru; > }; > > UINT64 value[MEM_ALIGN_SIZE(16) >> 3]; [Alin Serdean] Please increase the size of value to adjust for the new value (`mru`) diff --git a/datapath- _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
