On 10/29/14 at 11:46pm, Ben Pfaff wrote:
> A "conjunctive match" allows higher-level matches in the flow table, such
> as set membership matches, without causing a cross-product explosion for
> multidimensional matches. Please refer to the documentation that this
> commit adds to ovs-ofctl(8) for a better explanation, including an example.
High level remark before I dig into the code:
conjunction(id, k/n)
I like n being the number of dimensions. I wonder whether we should
have k start at 1 instead of 0 though. It would read as 1/2 - "1st
dimension out of 2", 2/2 - "2nd dimension out of 2".
> - Fixing reg0 as the field to use for conjunctive match lookup doesn't seem
> too great. We could make it configurable per-flow, or we could add a new
> field specifically for this purpose. I am not sure that it should be
> fixed to 32 bits, either.
I guess we can't go wrong with a separate 64 bits field.
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev
