* bug in cryptodev enqueue/dequeue callbacks?
@ 2024-11-14 14:41 Konstantin Ananyev
0 siblings, 0 replies; only message in thread
From: Konstantin Ananyev @ 2024-11-14 14:41 UTC (permalink / raw)
To: dev; +Cc: gakhil, abhinandan.gujjar, honnappa.nagarahalli
Hi everyone,
Looking at implementation of cryptodev callbacks
(it uses DPDK RCU), it seems like there is a bug here:
at init time we don't call rte_rcu_qsbr_thread_register().
As I understand without it rte_rcu_qsbr_check() wouldn't
work properly for that thread.
Probably need to add:
static int
cryptodev_cb_init(struct rte_cryptodev *dev)
{
....
if (rte_rcu_qsbr_init(qsbr, max_threads)) {...}
+ rte_rcu_qsbr_thread_register(qsbr, 0);
Unless I am missing something obvious here?
Konstantin
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-11-14 14:41 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-11-14 14:41 bug in cryptodev enqueue/dequeue callbacks? Konstantin Ananyev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).