On 29 June 2016 at 21:08, Zong Kai LI <zealo...@gmail.com> wrote: > > > > - Ingress table 3 prepares flows for possible stateful ACL > processing > > - in table 4. It contains a priority-0 flow that simply moves > > - traffic to table 4. If stateful ACLs are used in the logical > > - datapath, a priority-100 flow is added that sends IP packets to > > - the connection tracker before advancing to table 4. > > + This table prepares flows for possible stateful ACL processing in > > + ingress table <code>ACLs</code>. It contains a priority-0 flow > that > > + simply moves traffic to the next table. If stateful ACLs are used > > in the > > + logical datapath, a priority-100 flow is added that sends IP > > packets to > > + the connection tracker before advancing to ingress table > > + <code>ACLs</code>. > > </p> > > > After this changing, shall we also need to update the following line, > remove "<code>from-lport</code>" to make table name simpler and clearer? >
The intention of this patch is to only change table numbers to table names. Changing existing table names, should ideally come in a different patch with proper rationale on why we want to change the name. Currently, 'from-lport' and 'to-lport' acts as qualifiers to make it a little easier to read (I personally find it helpful.). > > > > <h3>Ingress table 4: <code>from-lport</code> ACLs</h3> > > > > > > > - This is similar to ingress table 3 except for > <code>to-lport</code> > > - traffic. > > + This is similar to ingress table <code>Pre-ACLs</code> except for > > + <code>to-lport</code> traffic. > > </p> > > > > <h3>Egress Table 1: <code>to-lport</code> ACLs</h3> > > > > ditto > > thanks. > Zong Kai, LI > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
