[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openvswitch-dev
Subject:    [ovs-dev] [PATCH 1/3] datapath-windows: Update Recirculation to use portId instead of portNo
From:       nithin () vmware ! com (Nithin Raju)
Date:       2016-03-31 23:20:22
Message-ID: D322FEEF.357C0%nithin () vmware ! com
[Download RAW message or body]

Acked-by: Nithin Raju <nithin at vmware.com>

-----Original Message-----
From: Sairam Venugopal <vsairam at vmware.com>
Date: Tuesday, March 29, 2016 at 5:43 PM
To: <dev at openvswitch.org>
Cc: Sairam Venugopal <vsairam at vmware.com>
Subject: [PATCH 1/3] datapath-windows: Update Recirculation to use portId
instead of portNo

>Fix OvsDoRecirc to use the right PortId when there is a flow miss. This is
>used to determine if a packet is received or transmitted by comparing
>against the virtualExternalPortId.
>
>Signed-off-by: Sairam Venugopal <vsairam at vmware.com>
>---
> datapath-windows/ovsext/Actions.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/datapath-windows/ovsext/Actions.c
>b/datapath-windows/ovsext/Actions.c
>index a91454d..3e5dac9 100644
>--- a/datapath-windows/ovsext/Actions.c
>+++ b/datapath-windows/ovsext/Actions.c
>@@ -2015,7 +2015,7 @@ OvsDoRecirc(POVS_SWITCH_CONTEXT switchContext,
>         }
>         status = OvsCreateAndAddPackets(NULL, 0, OVS_PACKET_CMD_MISS,
>                                         vport, key, ovsFwdCtx.curNbl,
>-                                        srcPortNo ==
>+                                        vport->portId ==
>                  
>switchContext->virtualExternalPortId,
>                                         &ovsFwdCtx.layers,
>                                         ovsFwdCtx.switchContext,
>-- 
>2.5.0.windows.1
>
>
>


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic