[ovs-dev] RFC: conntrack Initial Design

[Jesse Gross]

On Thu, May 22, 2014 at 1:39 PM, Justin Pettit <jpettit at nicira.com> wrote:
> Connection Tracking
> -------------------
> The new connection tracking action is defined as follows:
>
>     /* Action structure for NXAST_CONNTRACK.
>      *
>      * Pass traffic to the connection tracker.  If 'flags' is NXACF_RESUBMIT,
>      * traffic is resubmitted back to the flow table with the NXM_NX_CONN_STATE
>      * and NXM_NX_CONN_STATE_W matches set.  A standard "resubmit" action
>      * is not sufficient, since connection tracking occurs outside of the
>      * classifier.  The 'zone' argument specifies a context within which the
>      * tracking is done. */
>     struct nx_action_conntrack {
>         ovs_be16 type;              /* OFPAT_VENDOR. */
>         ovs_be16 len;               /* 16. */
>         ovs_be32 vendor;            /* NX_VENDOR_ID. */
>         ovs_be16 subtype;           /* NXAST_CONNTRACK. */
>         ovs_be16 flags;             /* Either 0 or NXACF_RESUBMIT. */
>         ovs_be16 zone;              /* Connection tracking context. */
>         uint8_t  pad[2];
>     };

Is it possible to make the zone a register or accessible from a
register? I realize that there is a difference in size but it seems
like it has the potential to make the controller's job of allocating
zones significantly easier.