On Wed, 26 Mar 2025 18:44:36 +0530
wrote:
> +struct sw_vector_adapter_service_data {
> + uint32_t service_id;
> + RTE_ATOMIC(rte_mcslock_t *) lock;
> + RTE_TAILQ_HEAD(, sw_vector_adapter_data) adapter_list;
> +};
Why the indirect pointer to the lock? rather than embedding it in
the s
On Wed, 26 Mar 2025 17:25:32 +
Pavan Nikhilesh Bhagavatula wrote:
> > On Wed, 26 Mar 2025 18:44:36 +0530
> > wrote:
> >
> > > +struct sw_vector_adapter_service_data {
> > > + uint32_t service_id;
> > > + RTE_ATOMIC(rte_mcslock_t *) lock;
> > > + RTE_TAILQ_HEAD(, sw_vector_adapter_data) ad
> On Wed, 26 Mar 2025 18:44:36 +0530
> wrote:
>
> > +struct sw_vector_adapter_service_data {
> > + uint32_t service_id;
> > + RTE_ATOMIC(rte_mcslock_t *) lock;
> > + RTE_TAILQ_HEAD(, sw_vector_adapter_data) adapter_list;
> > +};
>
> Why the indirect pointer to the lock? rather than embeddi
On Wed, 26 Mar 2025 18:44:36 +0530
wrote:
> +
> +struct sw_vector_adapter_service_data {
> + uint32_t service_id;
> + RTE_ATOMIC(rte_mcslock_t *) lock;
> + RTE_TAILQ_HEAD(, sw_vector_adapter_data) adapter_list;
> +};
Do you really need mcslock here?
mcslock is for locks where there i
From: Pavan Nikhilesh
When event device PMD doesn't support vector adapter,
the library will fallback to software implementation
which relies on service core to check for timeouts
and vectorizes the objects on enqueue.
Signed-off-by: Pavan Nikhilesh
---
lib/eventdev/eventdev_pmd.h
5 matches
Mail list logo
