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 541B9A0547; Thu, 9 Sep 2021 14:54:30 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BC11D40041; Thu, 9 Sep 2021 14:54:29 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id EDADE4003E for ; Thu, 9 Sep 2021 14:54:27 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10101"; a="200306293" X-IronPort-AV: E=Sophos;i="5.85,280,1624345200"; d="scan'208";a="200306293" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Sep 2021 05:54:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.85,280,1624345200"; d="scan'208";a="606824695" Received: from silpixa00401089.ir.intel.com ([10.55.129.12]) by fmsmga001.fm.intel.com with ESMTP; 09 Sep 2021 05:54:24 -0700 From: Harry van Haaren To: dev@dpdk.org Cc: pravin.pathak@intel.com, timothy.mcdaniel@intel.com, Harry van Haaren Date: Thu, 9 Sep 2021 12:54:20 +0000 Message-Id: <20210909125422.31144-1-harry.van.haaren@intel.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH 0/2] eventdev: add port usage hints 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 Sender: "dev" These 2 patches are a suggestion to add a hint to the struct rte_event_port_conf.event_port_cfg. The usage of these hints is to allow an application to identify/communicate to the PMD what ports will primarily serve what purpose. E.g, some ports are "mainly producers" in that they are usually polling Ethdev RXQs (or other event sources..) and enqueue the resulting events to the eventdev instance. Similarly there are usages for "worker" (mainly forwards events) and "consumer" (mainly consumes events without re-enq). Note that these flags are *hints* only, and *functionally* any combination of (NEW/FWD/RELEASE) is still allowed by any port. The reason to add these is to allow a PMD to allocate internal resource more efficiently. Note that this implementation does not change the ABI, as it gives a purpose to existing bits in an existing field. Regards, -Harry Harry van Haaren (2): lib/eventdev: add usage hints to port configure API examples/eventdev_pipeline: use port config hints .../pipeline_worker_generic.c | 2 ++ .../eventdev_pipeline/pipeline_worker_tx.c | 2 ++ lib/eventdev/rte_eventdev.h | 23 +++++++++++++++++++ 3 files changed, 27 insertions(+) -- 2.30.2