Hi Erik,
A quick question.
> -----Original Message-----
> From: dev <[email protected]> On Behalf Of Erik Gabriel Carrillo
> Sent: Friday, April 26, 2019 10:14 AM
> To: [email protected]
> Cc: [email protected]; [email protected];
> [email protected]
> Subject: [dpdk-dev] [PATCH v6 1/1] eventdev: add new software event timer
> adapter
>
> This patch introduces a new version of the event timer adapter software PMD.
> In the original design, timer event producer lcores in the primary and
> secondary processes enqueued event timers into a ring, and a service core in
> the primary process dequeued them and processed them further. To improve
> performance, this version does away with the ring and lets lcores in both
> primary and secondary processes insert timers directly into timer skiplist
> data
> structures; the service core directly accesses the lists as well, when
> looking for
> timers that have expired.
How do you ensure concurrent access to the timer skiplist? Are you using any
locks or is it a lock-free data structure?
<snip>
