On Fri, 08 Jul 2016 11:04:46 +0900 IWAMOTO Toshihiro <[email protected]> wrote:
> At Thu, 7 Jul 2016 15:51:10 +0900, > Takashi YAMAMOTO wrote: >> >> [1 <multipart/alternative (7bit)>] >> [1.1 <text/plain; UTF-8 (7bit)>] >> this change broke dragonflow. >> https://bugs.launchpad.net/dragonflow/+bug/1599367 >> >> i thought we aimed to align with on-wire fields rather than ovs-ofctl etc. >> was the policy changed? > > Sorry I haven't noticed earlier, but we need to revert this IMO. > This ofs_nbits API has been there for a while, these numbers are on > wire (as yamamoto said), and OFPActionCopyField has a similar API. We should have really good reason to break the API compatibility with the older versions. I don't think that this is the case. Seems that better to revert this. Can we cleanly revert this? Any other side effect? ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
