On Wed, Oct 25, 2023 at 09:40:54AM +0200, Mattias Rönnblom wrote:
> Another option would be to have the current RTE_EVENT_DEV_CAP_BURST_MODE
> capable PMDs start using the "impl_opaque" field for the purpose of matching
> in and out events. It would require applications to actually start adhering
On Wed, Oct 25, 2023 at 09:40:54AM +0200, Mattias Rönnblom wrote:
> On 2023-10-24 11:10, Bruce Richardson wrote:
> > On Tue, Oct 24, 2023 at 09:10:30AM +0100, Bruce Richardson wrote:
> > > On Mon, Oct 23, 2023 at 06:10:54PM +0200, Mattias Rönnblom wrote:
> > > > Hi.
> > > >
> > > > Consider an Eve
On 2023-10-24 11:10, Bruce Richardson wrote:
On Tue, Oct 24, 2023 at 09:10:30AM +0100, Bruce Richardson wrote:
On Mon, Oct 23, 2023 at 06:10:54PM +0200, Mattias Rönnblom wrote:
Hi.
Consider an Eventdev app using atomic-type scheduling doing something like:
struct rte_event events[3];
On Tue, Oct 24, 2023 at 09:10:30AM +0100, Bruce Richardson wrote:
> On Mon, Oct 23, 2023 at 06:10:54PM +0200, Mattias Rönnblom wrote:
> > Hi.
> >
> > Consider an Eventdev app using atomic-type scheduling doing something like:
> >
> > struct rte_event events[3];
> >
> > rte_event_dequeue_
On Mon, Oct 23, 2023 at 06:10:54PM +0200, Mattias Rönnblom wrote:
> Hi.
>
> Consider an Eventdev app using atomic-type scheduling doing something like:
>
> struct rte_event events[3];
>
> rte_event_dequeue_burst(dev_id, port_id, events, 3, 0);
>
> /* Assume three events were dequeue
Hi.
Consider an Eventdev app using atomic-type scheduling doing something like:
struct rte_event events[3];
rte_event_dequeue_burst(dev_id, port_id, events, 3, 0);
/* Assume three events were dequeued, and the application decides
* it's best off to processing event 0 and 2 con
6 matches
Mail list logo
