From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <erik.g.carrillo@intel.com>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
by dpdk.org (Postfix) with ESMTP id 0109F6D45
for <dev@dpdk.org>; Fri, 22 Sep 2017 17:15:00 +0200 (CEST)
Received: from fmsmga006.fm.intel.com ([10.253.24.20])
by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
22 Sep 2017 08:14:59 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.42,427,1500966000"; d="scan'208";a="154900536"
Received: from wcpqa1.an.intel.com ([10.123.72.207])
by fmsmga006.fm.intel.com with ESMTP; 22 Sep 2017 08:14:58 -0700
From: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
To: jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org, bruce.richardson@intel.com, harry.van.haaren@intel.com,
hemant.agrawal@nxp.com, gage.ads@intel.com, nipun.gupta@nxp.com,
narender.vangati@intel.com, nikhil.rao@intel.com,
pbhagavatula@caviumnetworks.com, rsanford@akamai.com
Date: Fri, 22 Sep 2017 10:17:10 -0500
Message-Id: <1506093431-57588-1-git-send-email-erik.g.carrillo@intel.com>
X-Mailer: git-send-email 1.7.10
In-Reply-To: <20170817161104.24293-1-jerin.jacob@caviumnetworks.com>
References: <20170817161104.24293-1-jerin.jacob@caviumnetworks.com>
Subject: [dpdk-dev] [RFC PATCH v2 0/1] eventtimer: introduce event timer
adapter
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
<mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
<mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 15:15:01 -0000
Hi Jerin, et al.,
The following RFC patch contains enough of a skeleton implementation
for an event timer adapter to show how the API could call through an ops
structure to a plugin backend to provide different implementations.
In terms of differences from the original RFC, the most obvious one is
that I've replaced occurrences of "wheel" in the API with "adapter",
partly to reflect the similarity with the event_eth_rx_adapter, and
partly because "wheel" suggests an implementation that may not be
the one used (as in the case of the SW impl).
The second big change is to replace API parameters specifying pointer
to rte_event_timer_adapter with ids, which seems more common throughout
DPDK.
Other changes include:
- removed rte_event_timer_adapter_lookup() function, since APIs no longer
accept pointer to rte_event_timer_adapter
- Replaced RTE_EVENT_TIMER_SUCCESS_{ARM,CANCEL} states with
RTE_EVENT_TIMER_ARMED, since the purpose of the SUCCESS_CANCEL state was
unclear
Please have a look and let me know what you think.
Thanks,
Gabriel
Erik Gabriel Carrillo (1):
eventtimer: introduce event timer adapter
drivers/event/sw/Makefile | 1 +
drivers/event/sw/sw_evdev.c | 11 +
drivers/event/sw/sw_evdev_timer_adapter.c | 124 +++++++
lib/librte_eventdev/Makefile | 3 +
lib/librte_eventdev/rte_event_timer_adapter.c | 227 ++++++++++++
lib/librte_eventdev/rte_event_timer_adapter.h | 388 +++++++++++++++++++++
.../rte_event_timer_adapter_driver.h | 128 +++++++
lib/librte_eventdev/rte_eventdev.h | 2 +-
lib/librte_eventdev/rte_eventdev_pmd.h | 15 +
lib/librte_eventdev/rte_eventdev_version.map | 14 +
test/test/Makefile | 1 +
test/test/test_event_timer_adapter.c | 183 ++++++++++
12 files changed, 1096 insertions(+), 1 deletion(-)
create mode 100644 drivers/event/sw/sw_evdev_timer_adapter.c
create mode 100644 lib/librte_eventdev/rte_event_timer_adapter.c
create mode 100644 lib/librte_eventdev/rte_event_timer_adapter.h
create mode 100644 lib/librte_eventdev/rte_event_timer_adapter_driver.h
create mode 100644 test/test/test_event_timer_adapter.c
--
2.6.4