Re: [RFC v2 10/10] eventdev: remove single event enqueue and dequeue

2024-10-16 Thread Jerin Jacob
On Wed, Oct 16, 2024 at 12:14 AM Mattias Rönnblom wrote: > > Remove the single event enqueue and dequeue, since they did not > provide any noticable performance benefits. > > This is a change of the ABI, previously announced as a deprecation > notice. These functions were not directly called by th

Re: [RFC v2 10/10] eventdev: remove single event enqueue and dequeue

2024-10-15 Thread Mattias Rönnblom
On 2024-10-16 06:36, Mattias Rönnblom wrote: On 2024-10-16 00:00, Stephen Hemminger wrote: On Tue, 15 Oct 2024 20:25:35 +0200 Mattias Rönnblom wrote: Remove the single event enqueue and dequeue, since they did not provide any noticable performance benefits. This is a change of the ABI, previ

Re: [RFC v2 10/10] eventdev: remove single event enqueue and dequeue

2024-10-15 Thread Mattias Rönnblom
On 2024-10-16 00:00, Stephen Hemminger wrote: On Tue, 15 Oct 2024 20:25:35 +0200 Mattias Rönnblom wrote: Remove the single event enqueue and dequeue, since they did not provide any noticable performance benefits. This is a change of the ABI, previously announced as a deprecation notice. These

Re: [RFC v2 10/10] eventdev: remove single event enqueue and dequeue

2024-10-15 Thread Stephen Hemminger
On Tue, 15 Oct 2024 20:25:35 +0200 Mattias Rönnblom wrote: > Remove the single event enqueue and dequeue, since they did not > provide any noticable performance benefits. > > This is a change of the ABI, previously announced as a deprecation > notice. These functions were not directly called by

[RFC v2 10/10] eventdev: remove single event enqueue and dequeue

2024-10-15 Thread Mattias Rönnblom
Remove the single event enqueue and dequeue, since they did not provide any noticable performance benefits. This is a change of the ABI, previously announced as a deprecation notice. These functions were not directly called by the application, so the API remains unaffected. Signed-off-by: Mattias