-
- /*
- * DPDK sets vtag action on per interface basis, not
- * per flow basis. It is a matter of how we decide to support
- * this pmd specific behavior. There are two ways:
- * 1. Inherit the vtag action from the one configured
- * for this interface. This can be read from the
- * vtag_action configured for default mcam entry of
- * this pf_func.
- * 2. Do not support vtag action with rte_flow.
- *
- * Second approach is used now.
- */
- req->entry_data.vtag_action = 0ULL;