Depends on the approach. I'm not sure of this, since I never implemented an OF Switch myself but, if I needed to implement one myself, I would implement a table for queries and views and then, an optimized search tree for the pipeline. Each time the table is updated, the search tree would also be updated, but in an optimized way (removing redundant checks and simplifying the packet field comparisons. For me it seems alright but, I don't know if this is the best approach so I hope other people can contribute to this discussion.
On 28 April 2014 09:56, sujinzhao <43183...@qq.com> wrote: > YES，I have already queried the table features of a OF switch. > Suppose that I want to install flow entries, and table structure is > defined like previous cases on an OFS, what is the best practice in > implementation from an OFS vendor perspective? > Many Thanks. > > Carlos Ferreira <carlosmf...@gmail.com>编写： > > > Openflow Tables implementation are vendor-dependent. The OF Specs do not > define how the implementation should be, it only defines how it should > work. This gives space for optimizations depending on the product target. > > In those cases that you presented, are you asking for a OF message to > query the tables of a OF Switch ? > > > On 27 April 2014 15:23, Su <sujz.b...@qq.com> wrote: > >> Hi all, >> >> I am gonna to define a flow table with hybrid match fields, which means >> some match fields may have exact values, while others may be wildcarded, >> just like this: >> >> srcIP >> >> srcPort >> >> dstIP >> >> dstPort >> >> Other Info >> >> 192.168.0.1 >> >> 80 >> >> * >> >> * >> >> Whatever Info >> >> 192.168.0.1 >> >> * >> >> 192.168.0.2 >> >> * >> >> Whatever Info >> >> 192.168.1.100 >> >> 5678 >> >> 192.168.1.200 >> >> 6789 >> >> Whatever Info >> >> I know that Hash algorithm is very high-efficient in searching exact flow >> table, But I don't know how to store this kind of (hybrid) table within >> OpenFlow switch, with promise of still high efficience in finding a >> specific or more flow entries? These two case are further illustrated like >> this: >> Case 1: How to quickly find flow entry >> "srcIP=192.168.1.100,srcPort=5678,dstIP=192.168.1.200,dstPort=6789" ? >> Case 2: How to quickly find flow entries with "srcIP=192.168.0.1" ? >> >> Thank you very much! >> >> >> _______________________________________________ >> openflow-discuss mailing list >> openflow-discuss@lists.stanford.edu >> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >> >> > > > -- > > Carlos Miguel Ferreira > Researcher at Telecommunications Institute > Aveiro - Portugal > Work E-mail - c...@av.it.pt > Skype & GTalk -> carlosmf...@gmail.com > LinkedIn -> http://www.linkedin.com/in/carlosmferreira > -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - c...@av.it.pt Skype & GTalk -> carlosmf...@gmail.com LinkedIn -> http://www.linkedin.com/in/carlosmferreira
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
