[PATCH v6 0/3] Introduce event link profiles

[Bruce Richardson]

On Tue, Oct 03, 2023 at 04:06:10PM +0530, Jerin Jacob wrote:
> On Tue, Oct 3, 2023 at 3:17 PM <pbhagavatula at marvell.com> wrote:
> >
> > From: Pavan Nikhilesh <pbhagavatula at marvell.com>
> >
> > A collection of event queues linked to an event port can be associated
> > with unique identifier called as a link profile, multiple such profiles
> > can be configured based on the event device capability using the function
> > `rte_event_port_profile_links_set` which takes arguments similar to
> > `rte_event_port_link` in addition to the profile identifier.
> >
> > The maximum link profiles that are supported by an event device is
> > advertised through the structure member
> 
> ...
> 
> >
> > v6 Changes:
> 
> Series applied to dpdk-next-net-eventdev/for-main with following changes. Thanks
> 

I'm doing some investigation work on the software eventdev, using
eventdev_pipeline, and following these patches the eventdev_pipeline sample
no longer is working for me. Error message is as shown below:

    Config:
	ports: 2
	workers: 22
	packets: 33554432
	Queue-prio: 0
	qid0 type: ordered
	Cores available: 48
	Cores used: 24
	Eventdev 0: event_sw
    Stages:
	Stage 0, Type Ordered	Priority = 128

  EVENTDEV: rte_event_port_profile_unlink() line 1092: Invalid profile_id=0
  Error setting up port 0

Parameters used when running the app:
  -l 24-47 --in-memory --vdev=event_sw0 -- \
	-r 1000000 -t 1000000 -e 2000000 -w FFFFFC000000  -c 64 -W 500

Regards,
/Bruce