+/** Enable Shared TCAM Management
+ *
+ * This feature allows for management of high and low pools within
+ * the WC TCAM. These pools are only valid when this feature is enabled.
+ *
+ * For normal OVS-DPDK operation, this feature is not required and can
+ * be disabled by commenting out TF_TCAM_SHARED in this header file.
+ *
+ * Operation:
+ *
+ * When a shared session is created with WC TCAM entries allocated during
+ * tf_open_session(), the TF_TCAM_TBL_TYPE_WC_TCAM pool entries will be divided
+ * into 2 equal pools - TF_TCAM_TBL_TYPE_WC_TCAM_HIGH and
+ * TF_TCAM_TBL_TYPE_WC_TCAM_LOW.
+ *
+ * The user will allocate and free entries from either of these pools to obtain
+ * WC_TCAM entry offsets. For the WC_TCAM_HI/LO management, alloc/free is done
+ * using the tf_alloc_tcam_entry()/tf_free_tcam_entry() APIs for the shared
+ * session.
+ *
+ * The use case for this feature is so that applications can have a shared
+ * session and use the TF core to allocate/set/free entries within a given
+ * region of the WC_TCAM within the shared session. Application A only writes
+ * to the LOW region for example and Application B only writes to the HIGH
+ * region during normal operation. After Application A goes down, Application
+ * B may decide to overwrite the LOW region with the HIGH region's entries
+ * and switch to the low region.
+ *
+ * For other TCAM types in the shared session, no alloc/free operations are
+ * permitted. Only set should be used for other TCAM table types after getting
+ * the range as provided by the tf_get_resource_info() API.
+ *
+ */
+#define TF_TCAM_SHARED 1
+