> +
> +/**
> + * @internal
> + * The generic data structure associated with each RegEx device.
> + *
> + * Pointers to burst-oriented packet receive and transmit functions are
> + * located at the beginning of the structure, along with the pointer to
> + * where all the data elements for the particular device are stored in
> +shared
> + * memory. This split allows the function pointer and driver data to be
> +per-
> + * process, while the actual configuration data for the device is shared.
> + */
> +struct rte_regexdev {
> + regexdev_enqueue_t enqueue;
> + regexdev_dequeue_t dequeue;
> + const struct rte_regexdev_ops *dev_ops;
> + /**< Functions exported by PMD */
> + struct rte_device *device; /**< Backing device */ }
> +__rte_cache_aligned;
> +
What about a handle for the PMD private data such as
struct rte_eventdev_data *data;
/**< Pointer to device data */
struct rte_cryptodev_data *data;
/**< Pointer to device data */
