[ovs-dev] [PATCH] don't bother to ask dpif class delete ODPP_NONE.

Ben Pfaff blp at nicira.com
Wed Aug 28 04:38:56 UTC 2013


On Wed, Aug 28, 2013 at 10:38:06AM +0900, YAMAMOTO Takashi wrote:
> > On Tue, Aug 27, 2013 at 04:10:03PM +0900, YAMAMOTO Takashi wrote:
> >> this fixes ofp_port_status delivery on a patch port removal.
> > 
> > Can you explain further?  I don't see any problems with patch port
> > removal.  Example:
> > 
> > blp at sigsegv:~/ovs/_clang$ make sandbox
> > ...
> > ----------------------------------------------------------------------
> > You are running in a dummy Open vSwitch environment.  You can use
> > ovs-vsctl, ovs-ofctl, ovs-appctl, and other tools to work with the
> > dummy switch.  
> > 
> > Log files, pidfiles, and the configuration database are in the
> > "sandbox" subdirectory.
> > 
> > Exit the shell to kill the running daemons.
> > blp at sigsegv:~/ovs/tutorial$ ovs-vsctl add-br br0
> 
> i'm using datapath_type=netdev.
> 
> kuma% ovs-vsctl add-br br0 -- set bridge br0 datapath_type=netdev
> kuma% ovs-ofctl monitor br0 128&
> [1] 17027
> kuma% ovs-vsctl add-port br0 patch1 -- set interface patch1 type=patch options:peer=patch1 -- add-port br0 patch2 -- set interface patch2 type=patch options:peer=patch2
> OFPT_PORT_STATUS (xid=0x0): ADD: 1(patch1): addr:aa:55:aa:55:00:02
>      config:     PORT_DOWN
>      state:      LINK_DOWN
>      speed: 0 Mbps now, 0 Mbps max
> OFPT_PORT_STATUS (xid=0x0): ADD: 2(patch2): addr:aa:55:aa:55:00:03
>      config:     PORT_DOWN
>      state:      LINK_DOWN
>      speed: 0 Mbps now, 0 Mbps max
> kuma% 

I don't understand yet.  If it is important to show me the output here,
then I guess your patch must change the output.  What change does your
patch make in the output?



More information about the dev mailing list