Re: [RFC 2/2] eventdev: add default software vector adapter

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

Re: [EXTERNAL] Re: [RFC 2/2] eventdev: add default software vector adapter

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

RE: [EXTERNAL] Re: [RFC 2/2] eventdev: add default software vector adapter

> 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

Re: [RFC 2/2] eventdev: add default software vector adapter

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