From patchwork Tue Nov 21 11:54:29 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bruce Richardson X-Patchwork-Id: 134507 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 834174338E; Tue, 21 Nov 2023 12:55:00 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6AE0E42EA8; Tue, 21 Nov 2023 12:54:53 +0100 (CET) Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.31]) by mails.dpdk.org (Postfix) with ESMTP id 8A55F42EA0 for ; Tue, 21 Nov 2023 12:54:51 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1700567691; x=1732103691; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=SkEBk1Zvd8eDirf7/2qSROr4CXyaIIquI4TH+h99/cs=; b=OOtotuZvnbxgERq430Ys9VIpaY8Xy8QEqEDh+3ZF40GrKxUGEbGVOxII hO4/nBi13+N/nuzHE/jGZdIkSdWI/zYQ7BpHAydyJByyUed2mn+pA8cxK MlcOTBPxYbBT0gWEOuJXYWdfMQ/G3XfaKVk6CKjq/Q6r7WOxje7uOlquO 2itoSp9lnkOZudlfruahhLdJKrE1Kiros/t4GU4wWzfeq17CHYbhZDASF nmFexAq+Y2tHL35SQ5FR5fRG9X6q4n/gB6xDcn+Rm+v5KUQQC1LjTgklz ls4UZUq0CSJoa7LbSXnJCNYkt18vScTktV2ed7UYTPqu4gVDKzsZ5K2O2 A==; X-IronPort-AV: E=McAfee;i="6600,9927,10900"; a="456160768" X-IronPort-AV: E=Sophos;i="6.04,215,1695711600"; d="scan'208";a="456160768" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Nov 2023 03:54:51 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10900"; a="801511313" X-IronPort-AV: E=Sophos;i="6.04,215,1695711600"; d="scan'208";a="801511313" Received: from unknown (HELO silpixa00401385.ir.intel.com) ([10.237.214.153]) by orsmga001.jf.intel.com with ESMTP; 21 Nov 2023 03:54:50 -0800 From: Bruce Richardson To: dev@dpdk.org Cc: Bruce Richardson , Jerin Jacob Subject: [PATCH 24.03 v2 1/9] eventdev: add capability flags for supported sched types Date: Tue, 21 Nov 2023 11:54:29 +0000 Message-Id: <20231121115437.96500-2-bruce.richardson@intel.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20231121115437.96500-1-bruce.richardson@intel.com> References: <20231120172606.505579-1-bruce.richardson@intel.com> <20231121115437.96500-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 Acked-by: Jerin Jacob --- doc/guides/eventdevs/features/default.ini | 3 +++ lib/eventdev/rte_eventdev.h | 21 +++++++++++++++++++++ 2 files changed, 24 insertions(+) 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..d48957362c 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 << 14) +/**< 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 << 15) +/**< 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