On Mon, 11 Jul 2016 17:13:52 +0900 Shinpei Muraoka <[email protected]> wrote:
> Hi Fujita-San > >> You mean that after I apply >> >> [PATCH v2 0/8] Support some NXAction >> >> then you send a patch to revert >> >> commit 3c3896fd77f274ce953dcb78795aa5cc4fde6c65 >> Author: Shinpei Muraoka <[email protected]> >> Date: Mon Jun 6 09:48:12 2016 +0900 >> >> ofproto/nx_actions: Update arguments to be compatible with ovs-ofctl >> >> >> Do I correctly understand what you mean? > > Yes. I want to do just it. I see. >> Do I correctly understand what you mean? >> >> I'm also concerned about the subject of the following patch in the new >> patchset: >> >> [PATCH v2 3/8] ofproto/nx_actions: Update arguments to be compatible >> with ovs-ofctl >> >> >> You try to add start/end as optional arguments and converts to >> ofs/nbits to keep the compatibility? Or revert the whole start/end >> stuff? > > I will revert the whole start/end stuff. Make sense. > This patch allows to set the string value(reg0 etc) for src or dst. > Does anyone want to aboid this change? Fine by me. I don't think that anyone has strong opinions on it. I've just pushed the series. Please send patches to revert the whole start/end stuff. As a side note, now Ryu OpenFlow code is used by Neutron OVS plugin by default. I guess that it means if you install OpenStack, Ryu is used unless you configure not to do so. So we really need to be conservative to change our APIs. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
