Re: [ovs-dev] [PATCH 09/17] ovs-ofctl: Encode cookies in OXM-compliant manner.

2014-09-29 Thread Ben Pfaff
On Wed, Sep 24, 2014 at 10:37:45AM +0900, YAMAMOTO Takashi wrote: > > NXM/OXM are only supposed to put 1-bits in a value if the corresponding bit > > in the mask is a 1-bit, but in the case of cookie matching, e.g. > > ovs-ofctl del-flows br0 cookie=0x3/0x1 > > ovs-ofctl would encode a bad OXM.

Re: [ovs-dev] [PATCH 09/17] ovs-ofctl: Encode cookies in OXM-compliant manner.

2014-09-23 Thread YAMAMOTO Takashi
> NXM/OXM are only supposed to put 1-bits in a value if the corresponding bit > in the mask is a 1-bit, but in the case of cookie matching, e.g. > ovs-ofctl del-flows br0 cookie=0x3/0x1 > ovs-ofctl would encode a bad OXM. This fixes the problem. > > (The test "ofproto - del flows based on coo

[ovs-dev] [PATCH 09/17] ovs-ofctl: Encode cookies in OXM-compliant manner.

2014-09-16 Thread Ben Pfaff
NXM/OXM are only supposed to put 1-bits in a value if the corresponding bit in the mask is a 1-bit, but in the case of cookie matching, e.g. ovs-ofctl del-flows br0 cookie=0x3/0x1 ovs-ofctl would encode a bad OXM. This fixes the problem. (The test "ofproto - del flows based on cookie mask" in