On Thu, Dec 16, 2010 at 04:11:16PM +, Haris Rotsos wrote:
> Following your answer, the insertion of exact match rules in the
> classifier table doesn't have an impact on the switching performance
> and is the default behaviour expected from openvswitch?
(Is that what you were really asking abo
On Dec 16, 2010, at 8:11 AM, Haris Rotsos wrote:
> Following your answer, the insertion of exact match rules in the
> classifier table doesn't have an impact on the switching performance
> and is the default behaviour expected from openvswitch?
Correct. Plus, the kernel module only stores exact-
Dear Ben,
thanks a lot for your quick answer.
Following your answer, the insertion of exact match rules in the
classifier table doesn't have an impact on the switching performance
and is the default behaviour expected from openvswitch?
The linear search mode for the classifier table, was only a
On Thu, Dec 16, 2010 at 8:00 AM, Haris Rotsos wrote:
> I noticed using ovs-ofctl that openvswitch has 2 tables : hash with
> wildcard 0x00 and classifier with wildcard 0x3f. My
> understanding is that the first table is used for exact matches flows,
> while the second is used for wilcarded
Hello everybody,
I am currently using openvswitch as an openflow switch and nox as the
controller, within which which I am writting a test module in python.
The module inserts a few exact match flows in the openflow switch.
I noticed using ovs-ofctl that openvswitch has 2 tables : hash with
wildc