DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vipin Varghese <vipin.varghese@intel.com>
To: marko.kovacevic@intel.com, john.mcnamara@intel.com,
	jerinj@marvell.com, harry.van.haaren@intel.com,
	keith.wiles@intel.com, gage.eads@intel.com, dev@dpdk.org
Cc: sanjay.padubidri@intel.com, narender.vangati@intel.com,
	ilia.kurakin@intel.com, Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH v1 0/2] event enqueue-dequeue callback handler
Date: Thu,  6 Jun 2019 23:59:55 +0530	[thread overview]
Message-ID: <20190606182957.56596-1-vipin.varghese@intel.com> (raw)

The patch series is an attempt to add callback handlers to event device.

Motivation
==========

Allow user to debug and modify the event list in event device enqueue-dequeue
stages.

The enqueue stage is modified to allow user handler to be invoked prior to
actual device enqueue. The dequeue stage is modified to allow user handler
to be invoked post to actual device dequeue.

Status
======

The new APIs are added as experimental.

Change Log:
==========

Vipin Varghese (2):
  lib/event: add callback handlers for event
  examples/event: add callback handle

 config/common_base                           |   1 +
 examples/eventdev_pipeline/main.c            |  49 +++
 lib/librte_eventdev/rte_eventdev.c           | 361 +++++++++++++++++++
 lib/librte_eventdev/rte_eventdev.h           | 267 +++++++++++++-
 lib/librte_eventdev/rte_eventdev_version.map |   8 +
 5 files changed, 682 insertions(+), 4 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-06-06 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 18:29 Vipin Varghese [this message]
2019-06-06 18:29 ` [dpdk-dev] [PATCH v1 1/2] lib/event: add callback handlers for event Vipin Varghese
2019-06-06 18:29 ` [dpdk-dev] [PATCH v1 2/2] examples/event: add callback handle Vipin Varghese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190606182957.56596-1-vipin.varghese@intel.com \
    --to=vipin.varghese@intel.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=ilia.kurakin@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=keith.wiles@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=narender.vangati@intel.com \
    --cc=sanjay.padubidri@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).