Hi, Look at Per flow meters, introduced in OpenFlow 1.3, for an example.
Consider a scenario, where you use meters in table 0 for ingress bandwidth limiting per source, and meters in table 1 for egress bandwidth limiting per destination (with different values for different sources and destinations). If you have incoming traffics from different sources to the same destination, then those traffics would be handled by separate meters in table 0, and the same meter entry in table 1. You cannot convert this to a single-table equivalent, because then you'd only have independent meter entries for each source-destination pair, which cannot express the shared nature of bandwidth limiting per destination. Regards, Zoltan. From: openflow-discuss-boun...@lists.stanford.edu [mailto:openflow-discuss-boun...@lists.stanford.edu] On Behalf Of Mohammed Alsaleh Sent: Monday, July 01, 2013 10:16 PM To: openflow-discuss@lists.stanford.edu Subject: [openflow-discuss] OF Switch Multip Tables Dear All Does anybody knows what is the benefit of having multiple flow tables in the same OF switch from the functional point of view? I have searched online and found that there are some benefits from management, performance and hardware implementation point of view. In other words, if we combine the tables in one table by aggregating the actions that should be performed on every possible flow, does this provide the same functionality as if we have multiple flow tables? If you think the answer is no, I would appreciate if you can provide an example showing the difference. Regards Mohammed
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
