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 02E81459BA; Tue, 17 Sep 2024 09:11:18 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A9FB540267; Tue, 17 Sep 2024 09:11:17 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by mails.dpdk.org (Postfix) with ESMTP id 9B40740261 for ; Tue, 17 Sep 2024 09:11:15 +0200 (CEST) Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 48H09wwK031635; Tue, 17 Sep 2024 00:11:13 -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=g T12wd8Kl+ueIrjPB5OsqJtq68QK/W329KqmTUv4aQE=; b=R+49Cu2NbpB5jxDik CzYbY+vfFDFWpESU3q4Ko3hrEcmAesNCdkdXVQiDAFzK3oXw3e7vrDgcGwxwbJ00 ogSYXzdNrbDAnTQ31PKLiWP+QZ1SSCcEuZGkgEZlg7RzgnGlAMcAj7PqkZed73Zd T6LFigJWEFv1hiyukJnT1j1oi8MbdlFluwzqspLzpfTAyuD95YBMgYEu+dI3lnVB UwzGV0T7cBbdxxVGYFLcLnv8ZjsG/sdbnUwNHjPbL62jq2/Q8WhRsYuHcdFChWQw uMEyz+ZGC6C/+AzZn6pxypIl9KSuZH8k25KLTu61HD9nSzBJ7DMaWC9r9hYof3rG 0rMWw== Received: from dc6wp-exch02.marvell.com ([4.21.29.225]) by mx0a-0016f401.pphosted.com (PPS) with ESMTPS id 41n7ujskef-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 Sep 2024 00:11:13 -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; Tue, 17 Sep 2024 00:11:12 -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; Tue, 17 Sep 2024 00:11:12 -0700 Received: from MININT-80QBFE8.corp.innovium.com (MININT-80QBFE8.marvell.com [10.28.21.130]) by maili.marvell.com (Postfix) with ESMTP id 7E66D5B6930; Tue, 17 Sep 2024 00:11:08 -0700 (PDT) From: To: , , , , , , , , CC: , Pavan Nikhilesh Subject: [PATCH v2 0/3] Introduce event pre-scheduling Date: Tue, 17 Sep 2024 12:41:03 +0530 Message-ID: <20240917071106.8815-1-pbhagavatula@marvell.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20240910083117.4281-1-pbhagavatula@marvell.com> References: <20240910083117.4281-1-pbhagavatula@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Proofpoint-GUID: hLKi-K83Tf6ELi-E3ztWEoXg3EB1BlJF X-Proofpoint-ORIG-GUID: hLKi-K83Tf6ELi-E3ztWEoXg3EB1BlJF X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.60.29 definitions=2024-09-06_09,2024-09-06_01,2024-09-02_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 Event pre-scheduling improves scheduling performance by assigning events to event ports in advance when dequeues are issued. This series introduces various types and levels of pre-scheduling to the eventdev library. pre-scheduling Types: * RTE_EVENT_DEV_PRESCHEDULE_NONE: No pre-scheduling. * RTE_EVENT_DEV_PRESCHEDULE: Always issue a pre-schedule when dequeue is issued. * RTE_EVENT_DEV_PRESCHEDULE_ADAPTIVE: Delay issuing pre-schedule until there are no forward progress constraints with the held flow contexts. pre-scheduling Levels: * Event Device Level Pre-scheduling: Pre-scheduling can be enabled or disabled at the event device during configuration. Event devices can indicate pre-scheduling capabilities using `RTE_EVENT_DEV_CAP_EVENT_PRESCHEDULE` and `RTE_EVENT_DEV_CAP_EVENT_PRESCHEDULE_ADAPTIVE` via the event device info function `info.event_dev_cap`. * Event Port Level Prefetch: Pre-scheduling can be selectively enabled or disabled at the event port during runtime. Event devices can indicate this capability using `RTE_EVENT_PORT_CAP_EVENT_PER_PORT_PRESCHEDULE` via the event device info function `info.event_port_cap`. * Application Controlled Prefetch Hint: Applications can provide hints to the event device to start pre-scheduling events using the new API `rte_event_port_pre-schedule`. Event devices can indicate this capabilities using `RTE_EVENT_DEV_CAP_SW_PRESCHEDULE` via the event device info function `info.event_dev_cap`. The rte_event_dequeue_burst operation initiates the pre-schedule operation, which completes in parallel without affecting the flow context of the dequeued events and dequeue latency. On the next dequeue operation, the pre-scheduleed events are dequeued, and pre-schedule operation is initiated again. In the case of application-controlled pre-schedule hints, the currently held flow contexts, if any, are not affected by the pre-schedule operation. On the next dequeue operation, the pre-scheduleed events are returned, but pre-schedule is not initiated again until the application provides the hint again. If pre-scheduling is already enabled at the event device level or event port level, the hint is ignored. v2 Changes: - s/prefetch/pre-schedule (Mattias) Pavan Nikhilesh (3): eventdev: introduce event pre-scheduling eventdev: add event port pre-schedule modify eventdev: add SW event preschedule hint app/test/test_eventdev.c | 114 +++++++++++++++ doc/guides/prog_guide/eventdev/eventdev.rst | 42 ++++++ lib/eventdev/eventdev_pmd.h | 4 + lib/eventdev/eventdev_private.c | 22 ++- lib/eventdev/eventdev_trace_points.c | 6 + lib/eventdev/rte_eventdev.h | 152 ++++++++++++++++++++ lib/eventdev/rte_eventdev_core.h | 11 ++ lib/eventdev/rte_eventdev_trace_fp.h | 19 ++- lib/eventdev/version.map | 6 + 9 files changed, 373 insertions(+), 3 deletions(-) -- 2.25.1