From patchwork Mon Nov 20 17:25:59 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bruce Richardson X-Patchwork-Id: 134497 X-Patchwork-Delegate: jerinj@marvell.com Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5279843381; Mon, 20 Nov 2023 18:26:35 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3FE9742E38; Mon, 20 Nov 2023 18:26:35 +0100 (CET) Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.31]) by mails.dpdk.org (Postfix) with ESMTP id AA0BF4027A for ; Mon, 20 Nov 2023 18:26:33 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1700501193; x=1732037193; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=HJLtD3LaJoOz2x1qw10fQ3SQbrr8eq8OaBiWov3TnWU=; b=Iatu8py4T4SF3hGeEw6nE8SosCa+Kv9XSRRYfpZrDPl7OGR/+b8auZ+W 99BYbI9cvd9xP79gpsbBgCatasRRvLVEM/zSlm4bSUkiLZywB7alH4wtK fXIiwghWrpxiUoDrhRkJGeBrrGj34S80D8WEPhQMkLOJwwyZd/QBEu6ba VjUKmkVYBeVhxvj14cetNyCa2nla9cks7XSusXTQXKiGR6fLXzi8ojpba 3Nfc2w3HqjAQO5cFU8q2VGoeksqjmAAZNn3KkEIhgFS+FVG3/cSINx8qy Y4Nu6zZ2/hLBdZzKP3HXaV+LYcqPQU3Ii7luZ4DBUD1GYW+JLL/OH3meq w==; X-IronPort-AV: E=McAfee;i="6600,9927,10900"; a="455996523" X-IronPort-AV: E=Sophos;i="6.04,214,1695711600"; d="scan'208";a="455996523" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Nov 2023 09:26:33 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10900"; a="889984517" X-IronPort-AV: E=Sophos;i="6.04,214,1695711600"; d="scan'208";a="889984517" Received: from silpixa00401385.ir.intel.com ([10.237.214.168]) by orsmga004.jf.intel.com with ESMTP; 20 Nov 2023 09:26:31 -0800 From: Bruce Richardson To: dev@dpdk.org Cc: Bruce Richardson , Jerin Jacob Subject: [PATCH 24.03 1/8] eventdev: add capability flags for supported sched types Date: Mon, 20 Nov 2023 17:25:59 +0000 Message-Id: <20231120172606.505579-2-bruce.richardson@intel.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20231120172606.505579-1-bruce.richardson@intel.com> References: <20231120172606.505579-1-bruce.richardson@intel.com> MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Not all eventdev's support all scheduling types, for example, some may only support atomic scheduling or others only support ordered scheduling. There is currently no clear indication for each driver what sched types it supports, so add capability flags to be indicated on return from rte_event_dev_info_get() API. Similarly add the possible scheduling types to the capabilities table in the docs. Signed-off-by: Bruce Richardson --- doc/guides/eventdevs/features/default.ini | 3 +++ lib/eventdev/rte_eventdev.h | 21 +++++++++++++++++++++ 2 files changed, 24 insertions(+) -- 2.39.2 diff --git a/doc/guides/eventdevs/features/default.ini b/doc/guides/eventdevs/features/default.ini index e980ae134a..1cc4303fe5 100644 --- a/doc/guides/eventdevs/features/default.ini +++ b/doc/guides/eventdevs/features/default.ini @@ -6,6 +6,9 @@ ; the features table in the documentation. ; [Scheduling Features] +atomic_scheduling = +ordered_scheduling = +parallel_scheduling = queue_qos = event_qos = distributed_sched = diff --git a/lib/eventdev/rte_eventdev.h b/lib/eventdev/rte_eventdev.h index ec9b02455d..9109de157e 100644 --- a/lib/eventdev/rte_eventdev.h +++ b/lib/eventdev/rte_eventdev.h @@ -326,6 +326,27 @@ struct rte_event; * than one. */ +#define RTE_EVENT_DEV_CAP_ATOMIC (1ULL << 13) +/**< Event device is capable of atomic scheduling. + * When this flag is set, the application can configure queues with scheduling type + * atomic on this event device. + * @see RTE_SCHED_TYPE_ATOMIC + */ + +#define RTE_EVENT_DEV_CAP_ORDERED (1ULL << 13) +/**< Event device is capable of ordered scheduling. + * When this flag is set, the application can configure queues with scheduling type + * ordered on this event device. + * @see RTE_SCHED_TYPE_ORDERED + */ + +#define RTE_EVENT_DEV_CAP_PARALLEL (1ULL << 13) +/**< Event device is capable of parallel scheduling. + * When this flag is set, the application can configure queues with scheduling type + * parallel on this event device. + * @see RTE_SCHED_TYPE_PARALLEL + */ + /* Event device priority levels */ #define RTE_EVENT_DEV_PRIORITY_HIGHEST 0 /**< Highest priority expressed across eventdev subsystem