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 4B59A46555; Thu, 10 Apr 2025 20:01:10 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2A51B40677; Thu, 10 Apr 2025 20:01:10 +0200 (CEST) Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by mails.dpdk.org (Postfix) with ESMTP id 9A303402ED for ; Thu, 10 Apr 2025 20:01:08 +0200 (CEST) Received: from pps.filterd (m0431384.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 53AFujAu008879; Thu, 10 Apr 2025 11:01:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=pfpt0220; bh=1 lPiE3FrIVpP18QyPArrp3hcjPYXtgpdwgHWQBcQL7k=; b=RHZP8VE4sLh3XSa/4 gReduK8Ej4tI522EiCvVJQSBaJltyAk9UajTCFeBaRE/oo9uwfCTjMrRP31DyPQ1 EZ+CEU97ixiOu3PvQIl2BSolRsk7wL4SE6xq67M3hGdmVOaz6Q/+91xxkNnd06Un IrDs50yHWBK0JcAKghmyEkZFMlT2iHreUy0wI0TNyoEAd9I/CfwmkYbG3HHDdPhD PyPCmswXtH3n1LHQpI3QK8yBXAU3Q7ukDXcnEOGBDr/aIZ4L+GQLdqTHOaw0BDmK 5LRp4XHMYE2MnoRl7YJGJfS4p6TkTfQDn8z5Yp3BwKvYXSp0iYiKH2EZxfvsmtUo JFCIA== Received: from dc6wp-exch02.marvell.com ([4.21.29.225]) by mx0a-0016f401.pphosted.com (PPS) with ESMTPS id 45wp0c44s7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 10 Apr 2025 11:01:07 -0700 (PDT) Received: from DC6WP-EXCH02.marvell.com (10.76.176.209) by DC6WP-EXCH02.marvell.com (10.76.176.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.4; Thu, 10 Apr 2025 11:01:06 -0700 Received: from maili.marvell.com (10.69.176.80) by DC6WP-EXCH02.marvell.com (10.76.176.209) with Microsoft SMTP Server id 15.2.1544.4 via Frontend Transport; Thu, 10 Apr 2025 11:01:06 -0700 Received: from MININT-80QBFE8.corp.innovium.com (unknown [10.28.164.118]) by maili.marvell.com (Postfix) with ESMTP id 45AB23F7073; Thu, 10 Apr 2025 11:01:01 -0700 (PDT) From: To: , , , , , , , , , , , , CC: , Pavan Nikhilesh Subject: [PATCH 0/3] introduce event vector adapter Date: Thu, 10 Apr 2025 23:30:38 +0530 Message-ID: <20250410180056.10368-1-pbhagavatula@marvell.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20250326131441.5965-2-pbhagavatula@marvell.com> References: <20250326131441.5965-2-pbhagavatula@marvell.com> MIME-Version: 1.0 Content-Type: text/plain; charset="y" Content-Transfer-Encoding: 8bit X-Proofpoint-GUID: P_rX7FT1oor31G88uhG6UdPvJ80QgXUW X-Proofpoint-ORIG-GUID: P_rX7FT1oor31G88uhG6UdPvJ80QgXUW X-Authority-Analysis: v=2.4 cv=H47bw/Yi c=1 sm=1 tr=0 ts=67f80763 cx=c_pps a=gIfcoYsirJbf48DBMSPrZA==:117 a=gIfcoYsirJbf48DBMSPrZA==:17 a=qf4gfuq51q0A:10 a=XR8D0OoHHMoA:10 a=M5GUcnROAAAA:8 a=JXciUlWNcDX0_0edI6gA:9 a=3ZKOabzyN94A:10 a=k40Crp0UdiQA:10 a=OBjm3rFKGHvpk9ecZwUJ:22 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1095,Hydra:6.0.680,FMLib:17.12.68.34 definitions=2025-04-10_05,2025-04-10_01,2024-11-22_01 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 From: Pavan Nikhilesh The event vector adapter supports offloading the creation of event vectors by vectorizing objects (mbufs/ptrs/u64s). An event vector adapter has the following working model: ┌──────────┐ │ Vector ├─┐ │ adapter0 │ │ └──────────┘ │ ┌──────────┐ │ ┌──────────┐ │ Vector ├─┼──►│ Event │ │ adapter1 │ │ │ Queue0 │ └──────────┘ │ └──────────┘ ┌──────────┐ │ │ Vector ├─┘ │ adapter2 │ └──────────┘ ┌──────────┐ │ Vector ├─┐ │ adapter0 │ │ ┌──────────┐ └──────────┘ ├──►│ Event │ ┌──────────┐ │ │ Queue1 │ │ Vector ├─┘ └──────────┘ │ adapter1 │ └──────────┘ - A vector adapter can be seen as an extension to event queue. It helps in aggregating objects and generating a vector event which is enqueued to the event queue. - Multiple vector adapters can be created on an event queue, each with its own unique properties such as event properties, vector size, and timeout. Note: If the target event queue doesn't support RTE_EVENT_QUEUE_CFG_ALL_TYPES then the vector adapter should use the same schedule type as the event queue. - Each vector adapter aggregates objects, generates a vector event and enqueues it to the event queue with the event properties mentioned in rte_event_vector_adapter_conf::ev. - After configuring the vector adapter, the Application needs to use the rte_event_vector_adapter_enqueue() function to enqueue objects i.e., mbufs/ptrs/u64s to the vector adapter. On reaching the configured vector size or timeout, the vector adapter enqueues the event vector to the event queue. Note: Application should use the event_type and sub_event_type properly identifying the contents of vector event on dequeue. - If the vector adapter advertises the RTE_EVENT_VECTOR_ADAPTER_CAP_SOV_EOV capability, application can use the RTE_EVENT_VECTOR_ENQ_[S|E]OV flags to indicate the start and end of a vector event. * When RTE_EVENT_VECTOR_ENQ_SOV is set, the vector adapter will flush any aggregation in progress and start aggregating a new vector event with the enqueued objects. * When RTE_EVENT_VECTOR_ENQ_EOV is set, the vector adapter will add the objects enqueued to in-progress aggregation and enqueue the vector event to the event queue, even if configured vector size or timeout is not reached. * If both flags are set, the vector adapter will flush any aggregation in progress and enqueue the objects as a new vector event to the event queue. - If the vector adapter reaches the configured vector size, it will enqueue the aggregated vector event to the event queue. - If the vector adapter reaches the configured vector timeout, it will flush the aggregated objects as a vector event if the minimum vector size is reached, if not it will enqueue the objects as single events with fallback event properties mentioned in rte_event_vector_adapter_conf::ev_fallback. - If the vector adapter is unable to aggregate the objects into a vector event, it will enqueue the objects as single events to the event queue with the event properties mentioned in rte_event_vector_adapter_conf::ev_fallback. Before using the vector adapter, the application has to create and configure an event device and based on the event device capability it might require creating an additional event port. When the application creates the vector adapter using the ``rte_event_vector_adapter_create()`` function, the event device driver capabilities are checked. If an in-built port is absent, the application uses the default function to create a new event port. For finer control over event port creation, the application should use the ``rte_event_vector_adapter_create_ext()`` function. The application can enqueue one or more objects to the vector adapter using the ``rte_event_vector_adapter_enqueue()`` function and control the aggregation using the flags. Vector adapters report stats using the ``rte_event_vector_adapter_stats_get()`` function and reset the stats using the ``rte_event_vector_adapter_stats_reset()``. The application can destroy the vector adapter using the ``rte_event_vector_adapter_destroy()`` function. Pavan Nikhilesh (3): eventdev: introduce event vector adapter eventdev: add default software vector adapter app/eventdev: add vector adapter performance test app/test-eventdev/evt_common.h | 9 +- app/test-eventdev/evt_options.c | 14 + app/test-eventdev/evt_options.h | 1 + app/test-eventdev/test_perf_atq.c | 61 +- app/test-eventdev/test_perf_common.c | 281 ++++-- app/test-eventdev/test_perf_common.h | 13 +- app/test-eventdev/test_perf_queue.c | 66 +- app/test/meson.build | 1 + app/test/test_event_vector_adapter.c | 682 ++++++++++++++ config/rte_config.h | 1 + doc/api/doxy-api-index.md | 1 + doc/guides/eventdevs/features/default.ini | 7 + .../eventdev/event_vector_adapter.rst | 208 +++++ doc/guides/prog_guide/eventdev/eventdev.rst | 10 +- doc/guides/prog_guide/eventdev/index.rst | 1 + doc/guides/rel_notes/release_25_07.rst | 11 + doc/guides/tools/testeventdev.rst | 6 + lib/eventdev/event_vector_adapter_pmd.h | 85 ++ lib/eventdev/eventdev_pmd.h | 38 + lib/eventdev/meson.build | 3 + lib/eventdev/rte_event_vector_adapter.c | 864 ++++++++++++++++++ lib/eventdev/rte_event_vector_adapter.h | 481 ++++++++++ lib/eventdev/rte_eventdev.c | 24 + lib/eventdev/rte_eventdev.h | 10 + 24 files changed, 2779 insertions(+), 99 deletions(-) create mode 100644 app/test/test_event_vector_adapter.c create mode 100644 doc/guides/prog_guide/eventdev/event_vector_adapter.rst create mode 100644 lib/eventdev/event_vector_adapter_pmd.h create mode 100644 lib/eventdev/rte_event_vector_adapter.c create mode 100644 lib/eventdev/rte_event_vector_adapter.h -- 2.43.0