On Wed, May 25, 2016 at 09:27:31AM -0500, Ryan Moats wrote: > As I understand it, Table 0 identifies the logical port and logical > flow. I'm worried that this means we'll end up with separate bucket > rules for each ingress port of the port pairs that make up a port > group, leading to a cardinality product in the number of rules. > I'm trying to think of a way where Table 0 could identify the packet > as being part of a particular port group, and then I'd only need one > set of bucket rules to figure out the egress side. However, the > amount of free metadata space is limited and so before we go down > this path, I'm going to pull Justin, Ben and Russell in to see if > they buy into this idea or if they can think of an alternative.
I've barely been following the discussion, so a recap of the question here would help a lot. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev