From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 24.03 v2 0/9] document scheduling types for eventdev drivers
Date: Tue, 21 Nov 2023 11:54:28 +0000 [thread overview]
Message-ID: <20231121115437.96500-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20231120172606.505579-1-bruce.richardson@intel.com>
The various eventdev drivers, while fitting under a common API, do not
all support all scheduling types. The eventdev API is missing some way
to query the particular scheduling support for a driver, a key piece of
information for application developers. This patchset adds the necessary
capability flags, and documentation feature rows, then, driver-by-driver
adds the necessary flags to both code and docs.
V2:
* Fix flag values to be unique
* Fix missing PARALLEL flag on DSW
* Add patch adjusting definition of the ALL_TYPES flag
Bruce Richardson (9):
eventdev: add capability flags for supported sched types
eventdev: increase flexibility of all-types flag
event/cnxk: add schedule-type capability flags
event/dlb2: add schedule-type capability flags
event/dpaa*: add schedule-type capability flags
event/dsw: add schedule-type capability flags
event/octeontx: add schedule-type capability flags
event/opdl: add schedule-type capability flags
event/sw: add schedule-type capability flags
doc/guides/eventdevs/features/cnxk.ini | 3 ++
doc/guides/eventdevs/features/default.ini | 3 ++
doc/guides/eventdevs/features/dlb2.ini | 3 ++
doc/guides/eventdevs/features/dpaa.ini | 2 ++
doc/guides/eventdevs/features/dpaa2.ini | 2 ++
doc/guides/eventdevs/features/dsw.ini | 2 ++
doc/guides/eventdevs/features/octeontx.ini | 3 ++
doc/guides/eventdevs/features/opdl.ini | 2 ++
doc/guides/eventdevs/features/sw.ini | 3 ++
drivers/event/cnxk/cnxk_eventdev.c | 5 ++-
drivers/event/dlb2/dlb2.c | 5 ++-
drivers/event/dpaa/dpaa_eventdev.c | 2 ++
drivers/event/dpaa2/dpaa2_eventdev.c | 2 ++
drivers/event/dsw/dsw_evdev.c | 2 ++
drivers/event/octeontx/ssovf_evdev.c | 3 ++
drivers/event/opdl/opdl_evdev.c | 3 ++
drivers/event/sw/sw_evdev.c | 3 ++
lib/eventdev/rte_eventdev.h | 36 ++++++++++++++++++++--
18 files changed, 79 insertions(+), 5 deletions(-)
--
2.39.2
next prev parent reply other threads:[~2023-11-21 11:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 17:25 [PATCH 24.03 0/8] " Bruce Richardson
2023-11-20 17:25 ` [PATCH 24.03 1/8] eventdev: add capability flags for supported sched types Bruce Richardson
2023-11-20 17:48 ` Jerin Jacob
2023-11-20 17:52 ` Bruce Richardson
2023-11-21 9:30 ` Mattias Rönnblom
2023-11-21 9:46 ` Bruce Richardson
2023-11-21 11:12 ` Bruce Richardson
2023-11-21 17:08 ` Pathak, Pravin
2023-11-20 17:26 ` [PATCH 24.03 2/8] event/cnxk: add schedule-type capability flags Bruce Richardson
2023-11-20 17:26 ` [PATCH 24.03 3/8] event/dlb2: " Bruce Richardson
2023-11-20 22:45 ` Sevincer, Abdullah
2023-11-20 17:26 ` [PATCH 24.03 4/8] event/dpaa*: " Bruce Richardson
2023-11-21 10:51 ` Hemant Agrawal
2023-11-20 17:26 ` [PATCH 24.03 5/8] event/dsw: " Bruce Richardson
2023-11-21 9:30 ` Mattias Rönnblom
2023-11-21 9:32 ` Mattias Rönnblom
2023-11-21 9:44 ` Bruce Richardson
2023-11-21 9:47 ` Bruce Richardson
2023-11-20 17:26 ` [PATCH 24.03 6/8] event/octeontx: " Bruce Richardson
2023-11-20 17:26 ` [PATCH 24.03 7/8] event/opdl: " Bruce Richardson
2023-11-20 17:26 ` [PATCH 24.03 8/8] event/sw: " Bruce Richardson
2023-11-21 11:54 ` Bruce Richardson [this message]
2023-11-21 11:54 ` [PATCH 24.03 v2 1/9] eventdev: add capability flags for supported sched types Bruce Richardson
2023-11-23 3:59 ` Jerin Jacob
2023-11-21 11:54 ` [PATCH 24.03 v2 2/9] eventdev: increase flexibility of all-types flag Bruce Richardson
2023-11-23 4:07 ` Jerin Jacob
2023-12-12 11:28 ` Bruce Richardson
2023-12-12 12:47 ` Jerin Jacob
2023-11-21 11:54 ` [PATCH 24.03 v2 3/9] event/cnxk: add schedule-type capability flags Bruce Richardson
2023-11-21 11:54 ` [PATCH 24.03 v2 4/9] event/dlb2: " Bruce Richardson
2023-11-21 11:54 ` [PATCH 24.03 v2 5/9] event/dpaa*: " Bruce Richardson
2023-11-21 11:54 ` [PATCH 24.03 v2 6/9] event/dsw: " Bruce Richardson
2023-11-21 11:54 ` [PATCH 24.03 v2 7/9] event/octeontx: " Bruce Richardson
2023-11-21 11:54 ` [PATCH 24.03 v2 8/9] event/opdl: " Bruce Richardson
2023-11-23 4:10 ` Jerin Jacob
2023-11-23 9:19 ` Bruce Richardson
2023-11-23 9:38 ` Jerin Jacob
2023-11-21 11:54 ` [PATCH 24.03 v2 9/9] event/sw: " Bruce Richardson
2023-12-12 11:32 ` [PATCH v3 0/9] document scheduling types for eventdev drivers Bruce Richardson
2023-12-12 11:32 ` [PATCH v3 1/9] eventdev: add capability flags for supported sched types Bruce Richardson
2023-12-12 11:32 ` [PATCH v3 2/9] eventdev: clarify all-types flag documentation Bruce Richardson
2023-12-13 12:50 ` Jerin Jacob
2023-12-13 13:20 ` Mattias Rönnblom
2023-12-12 11:32 ` [PATCH v3 3/9] event/cnxk: add schedule-type capability flags Bruce Richardson
2023-12-12 11:32 ` [PATCH v3 4/9] event/dlb2: " Bruce Richardson
2023-12-12 11:32 ` [PATCH v3 5/9] event/dpaa*: " Bruce Richardson
2023-12-12 11:32 ` [PATCH v3 6/9] event/dsw: " Bruce Richardson
2023-12-12 11:32 ` [PATCH v3 7/9] event/octeontx: " Bruce Richardson
2023-12-12 11:32 ` [PATCH v3 8/9] event/opdl: " Bruce Richardson
2023-12-12 11:32 ` [PATCH v3 9/9] event/sw: " Bruce Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231121115437.96500-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).