DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	Jerin Jacob <jerinj@marvell.com>
Subject: [PATCH 24.03 6/8] event/octeontx: add schedule-type capability flags
Date: Mon, 20 Nov 2023 17:26:04 +0000	[thread overview]
Message-ID: <20231120172606.505579-7-bruce.richardson@intel.com> (raw)
In-Reply-To: <20231120172606.505579-1-bruce.richardson@intel.com>

Document explicitly the scheduling types supported by this driver, both
via info_get() function, and via table in the documentation.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
 doc/guides/eventdevs/features/octeontx.ini | 3 +++
 drivers/event/octeontx/ssovf_evdev.c       | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/doc/guides/eventdevs/features/octeontx.ini b/doc/guides/eventdevs/features/octeontx.ini
index ec044e6289..06efae767a 100644
--- a/doc/guides/eventdevs/features/octeontx.ini
+++ b/doc/guides/eventdevs/features/octeontx.ini
@@ -4,6 +4,9 @@
 ; Refer to default.ini for the full list of available PMD features.
 ;
 [Scheduling Features]
+atomic_scheduling          = Y
+ordered_scheduling         = Y
+parallel_scheduling        = Y
 queue_qos                  = Y
 distributed_sched          = Y
 queue_all_types            = Y
diff --git a/drivers/event/octeontx/ssovf_evdev.c b/drivers/event/octeontx/ssovf_evdev.c
index a16f24e088..3a933b1db7 100644
--- a/drivers/event/octeontx/ssovf_evdev.c
+++ b/drivers/event/octeontx/ssovf_evdev.c
@@ -151,6 +151,9 @@ ssovf_info_get(struct rte_eventdev *dev, struct rte_event_dev_info *dev_info)
 	dev_info->max_event_port_enqueue_depth = 1;
 	dev_info->max_num_events =  edev->max_num_events;
 	dev_info->event_dev_cap = RTE_EVENT_DEV_CAP_QUEUE_QOS |
+					RTE_EVENT_DEV_CAP_ATOMIC |
+					RTE_EVENT_DEV_CAP_ORDERED |
+					RTE_EVENT_DEV_CAP_PARALLEL |
 					RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED |
 					RTE_EVENT_DEV_CAP_QUEUE_ALL_TYPES|
 					RTE_EVENT_DEV_CAP_RUNTIME_PORT_LINK |
--
2.39.2


  parent reply	other threads:[~2023-11-20 17:27 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 17:25 [PATCH 24.03 0/8] document scheduling types for eventdev drivers 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 ` Bruce Richardson [this message]
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 ` [PATCH 24.03 v2 0/9] document scheduling types for eventdev drivers Bruce Richardson
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=20231120172606.505579-7-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    /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).