DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev]  [pull-request] next-eventdev 18.05 PRE-RC1
Date: Fri, 15 Mar 2019 05:50:39 +0000	[thread overview]
Message-ID: <20190315055014.GA25347@jerin> (raw)
Message-ID: <20190315055039.4V_ffcaQPwK1HDr-QZfTX9WXLszWTlKpDhvTKnFQAD4@z> (raw)

The following changes since commit 239912fa798e6e671072ca7ff987afd74c1e506c:

  git: ignore build directories (2019-03-13 11:57:05 +0100)

are available in the Git repository at:

  http://dpdk.org/git/next/dpdk-next-eventdev 

for you to fetch changes up to 744407cf7b80f9e5c886c2304211b429febb4394:

  doc: add notes about eventdev producer consumer dependency (2019-03-15 11:16:50 +0530)

----------------------------------------------------------------
Pallantla Poornima (1):
      event/opdl: fix sprintf with snprintf

Pavan Nikhilesh (7):
      examples/eventdev_pipeline: probe max events
      examples/eventdev_pipeline: follow proper teardown sequence
      app/eventdev: follow proper teardown sequence
      app/eventdev: configure optimum timers per adapter
      app/eventdev: start event producers after eventdev
      examples/eventdev: start ethdev after eth adapter setup
      doc: add notes about eventdev producer consumer dependency

 app/test-eventdev/test_perf_atq.c                  | 31 ++++++++++++++++++++++
 app/test-eventdev/test_perf_common.c               | 23 +---------------
 app/test-eventdev/test_perf_queue.c                | 31 ++++++++++++++++++++++
 app/test-eventdev/test_pipeline_atq.c              | 13 ++++-----
 app/test-eventdev/test_pipeline_common.c           |  1 +
 app/test-eventdev/test_pipeline_queue.c            | 13 ++++-----
 doc/guides/prog_guide/event_crypto_adapter.rst     |  5 ++++
 .../prog_guide/event_ethernet_rx_adapter.rst       |  5 ++++
 doc/guides/prog_guide/event_timer_adapter.rst      |  5 ++++
 doc/guides/prog_guide/eventdev.rst                 |  5 ++++
 drivers/event/opdl/opdl_evdev.c                    |  7 ++---
 drivers/event/opdl/opdl_evdev_xstats.c             |  7 +++--
 examples/eventdev_pipeline/main.c                  | 15 +++++++----
 .../eventdev_pipeline/pipeline_worker_generic.c    |  6 +++++
 examples/eventdev_pipeline/pipeline_worker_tx.c    |  6 +++++
 lib/librte_eventdev/rte_event_crypto_adapter.h     |  4 +++
 lib/librte_eventdev/rte_event_eth_rx_adapter.h     |  4 +++
 lib/librte_eventdev/rte_event_timer_adapter.h      |  4 +++
 18 files changed, 139 insertions(+), 46 deletions(-)

             reply	other threads:[~2019-03-15  5:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15  5:50 Jerin Jacob Kollanukkaran [this message]
2019-03-15  5:50 ` Jerin Jacob Kollanukkaran
2019-03-20 15:09 ` Thomas Monjalon
2019-03-20 15:09   ` Thomas Monjalon

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=20190315055014.GA25347@jerin \
    --to=jerinj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).