From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 982404558A; Wed, 10 Jul 2024 08:33:45 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 499AA427E5; Wed, 10 Jul 2024 08:33:33 +0200 (CEST) Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.14]) by mails.dpdk.org (Postfix) with ESMTP id 0B30940A75 for ; Wed, 10 Jul 2024 08:33:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1720593211; x=1752129211; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=7BB2yK5me0leFgk/LID5dOPk7Xh0kotIKR0AaMnlD50=; b=ME0UH05vsQ31ktjvBrpCal1eFbywpTFoPcDrr58fbOL6L5jMhH6C+4sY 2NzlWRvWXb6XofeS6VfrST09vDcYZAlbOEsiTgqmUHw2xc7wTraSN2w6f qm/oOkDJUUHmNwL3r7V0wa/OSoHN9l/bCjQsI29wzLjgmr+dwflOplKub fh40BemeiRe6G0WH1I3cRDGnrKZQTTEMs5rD279ElSi5IQiCpJVhgXY1m ndytIKJz0h6Cj/YXAZChXC2+O49hbjHygtSkmrdgd4owjjthYFeTpOJrN Y7gLrg3SZdAz++KxckQjAiyB2GXPPm7CxsuW+biJYrxicUAmJsHTzWlPB Q==; X-CSE-ConnectionGUID: NYi0wpvqQGShDjXXP5o1aw== X-CSE-MsgGUID: U4nrYjWERISCBCBS3OFaJA== X-IronPort-AV: E=McAfee;i="6700,10204,11128"; a="21706712" X-IronPort-AV: E=Sophos;i="6.09,197,1716274800"; d="scan'208";a="21706712" Received: from orviesa007.jf.intel.com ([10.64.159.147]) by orvoesa106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Jul 2024 23:33:31 -0700 X-CSE-ConnectionGUID: N3x8icDHROWMdw9GQMYA2Q== X-CSE-MsgGUID: HwTJM7g7R2O1LfifA67GEQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.09,197,1716274800"; d="scan'208";a="48767992" Received: from txanpdk02.an.intel.com ([10.123.117.76]) by orviesa007.jf.intel.com with ESMTP; 09 Jul 2024 23:33:30 -0700 From: Abdullah Sevincer To: dev@dpdk.org Cc: jerinj@marvell.com, bruce.richardson@intel.com, pravin.pathak@intel.com, mattias.ronnblom@ericsson.com, manish.aggarwal@intel.com, Abdullah Sevincer Subject: [PATCH v5 2/3] eventdev: add support for independent enqueue Date: Wed, 10 Jul 2024 01:33:22 -0500 Message-Id: <20240710063323.2533952-3-abdullah.sevincer@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20240710063323.2533952-1-abdullah.sevincer@intel.com> References: <20240621222408.583464-3-abdullah.sevincer@intel.com> <20240710063323.2533952-1-abdullah.sevincer@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 This commit adds support for independent enqueue feature and updates Event Device and PMD feature list. A new capability RTE_EVENT_DEV_CAP_INDEPENDENT_ENQ is introduced to support independent enqueue to support PMD to enqueue in any order even the underlined hardware device needs enqueues in a strict dequeue order. To use this capability applications need to set flag RTE_EVENT_PORT_CFG_INDEPENDENT_ENQ during port setup only if the capability RTE_EVENT_DEV_CAP_INDEPENDENT_ENQ exists. Signed-off-by: Abdullah Sevincer --- doc/guides/eventdevs/features/default.ini | 1 + doc/guides/eventdevs/features/dlb2.ini | 1 + doc/guides/rel_notes/release_24_07.rst | 5 +++++ lib/eventdev/rte_eventdev.h | 21 +++++++++++++++++++++ 4 files changed, 28 insertions(+) diff --git a/doc/guides/eventdevs/features/default.ini b/doc/guides/eventdevs/features/default.ini index 1cc4303fe5..7c4ee99238 100644 --- a/doc/guides/eventdevs/features/default.ini +++ b/doc/guides/eventdevs/features/default.ini @@ -22,6 +22,7 @@ carry_flow_id = maintenance_free = runtime_queue_attr = profile_links = +independent_enq = ; ; Features of a default Ethernet Rx adapter. diff --git a/doc/guides/eventdevs/features/dlb2.ini b/doc/guides/eventdevs/features/dlb2.ini index 7b80286927..c7193b47c1 100644 --- a/doc/guides/eventdevs/features/dlb2.ini +++ b/doc/guides/eventdevs/features/dlb2.ini @@ -15,6 +15,7 @@ implicit_release_disable = Y runtime_port_link = Y multiple_queue_port = Y maintenance_free = Y +independent_enq = Y [Eth Rx adapter Features] diff --git a/doc/guides/rel_notes/release_24_07.rst b/doc/guides/rel_notes/release_24_07.rst index 76a79093d1..d8564b19f0 100644 --- a/doc/guides/rel_notes/release_24_07.rst +++ b/doc/guides/rel_notes/release_24_07.rst @@ -162,6 +162,11 @@ New Features ``RTE_EVENT_PORT_CFG_INDEPENDENT_ENQ`` to enable the feature if the capability ``RTE_EVENT_DEV_CAP_INDEPENDENT_ENQ`` exists. +* **Updated Event Device Library for independent enqueue feature** + + * Added support for independent enqueue feature. Updated Event Device and + PMD feature list. + Removed Items ------------- diff --git a/lib/eventdev/rte_eventdev.h b/lib/eventdev/rte_eventdev.h index 08e5f9320b..106b18fe28 100644 --- a/lib/eventdev/rte_eventdev.h +++ b/lib/eventdev/rte_eventdev.h @@ -446,6 +446,17 @@ struct rte_event; * @see RTE_SCHED_TYPE_PARALLEL */ +#define RTE_EVENT_DEV_CAP_INDEPENDENT_ENQ (1ULL << 16) +/**< Event device is capable of independent enqueue. + * When this flag is set, the application can enqueue to PMD in any order even + * the underlined hardware device needs enqueues in a strict dequeue order. + * PMD will reorder enqueued events based on their dequeue order when the feature + * is enabled on an Eventdev port. The capability supports applications that sort + * received bursts based on criteria like flow-id or receive QID and process them + * in smaller groups. Each processed group is enqueued separately, changing the + * dequeue order. + */ + /* Event device priority levels */ #define RTE_EVENT_DEV_PRIORITY_HIGHEST 0 /**< Highest priority level for events and queues. @@ -1072,6 +1083,16 @@ rte_event_queue_attr_set(uint8_t dev_id, uint8_t queue_id, uint32_t attr_id, * * @see rte_event_port_setup() */ + #define RTE_EVENT_PORT_CFG_INDEPENDENT_ENQ (1ULL << 5) +/**< Flag to enable independent enqueue. Must not be set if the device + * is not RTE_EVENT_DEV_CAP_INDEPENDENT_ENQ capable. This feature + * allows an application to enqueue RTE_EVENT_OP_FORWARD or + * RTE_EVENT_OP_RELEASE in an order different than the order the + * events were dequeued from the event device, while maintaining + * RTE_SCHED_TYPE_ATOMIC or RTE_SCHED_TYPE_ORDERED semantics. + * + * @see rte_event_port_setup() + */ /** Event port configuration structure */ struct rte_event_port_conf { -- 2.25.1