On Wed, Jun 20, 2012 at 12:49:35PM +0900, FUJITA Tomonori wrote: > On Wed, 20 Jun 2012 09:44:24 +0900 > Simon Horman <[email protected]> wrote: > > > On Tue, Jun 19, 2012 at 10:24:48PM +0900, FUJITA Tomonori wrote: > >> OFPMatch is slightly different from NXMatch so I implemented it > >> slightly differently. > > > > I am interested to know which differences you are thinking about. > > > > On the Open vSwtich side I believe that the only implementation differences > > are: > > * Different header constants > > * Different width of in_port > > An nx_match is a sequence of zero or more "nxm_entry"s, which are > type-length-value (TLV) entries. > > An OpenFlow match is composed of a flow match header and a sequence of > zero or more flow match fields. > > As a result, > > The nx_match code creates one NXMatch objecst per one nxm_entry. > > My oxm code creates one OFPMatch object and put zero or more match > fields.
Thanks, I understand now. Incidently, Open vSwtich does not currently deal with the match header properly, in particular the calculation of the trailing pad when the match header is present.. I have a patch, which is part of my Open Flow 1.2 series, but it is rather horrible. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
