DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev]  [pull-request] next-eventdev 17.11 rc2
Date: Wed, 25 Oct 2017 17:36:51 +0530	[thread overview]
Message-ID: <20171025120640.GA7741@jerin> (raw)

The following changes since commit 681459bf9cd5778ada011e6d8d681436ec5394f0:

  examples/vhost_scsi: fix product id string termination (2017-10-25 12:16:51 +0200)

are available in the git repository at:

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

for you to fetch changes up to b96273bb75fbd99a9732aa4d49658a3525b225b0:

  doc: add event octeontx Rx adapter limitation (2017-10-25 17:33:43 +0530)

----------------------------------------------------------------
Gage Eads (1):
      event/sw: allow fwd and rel when out of credits

Harry van Haaren (1):
      event/sw: fix get of single xstat value

Nikhil Rao (1):
      eventdev: add service get id API to map file

Nipun Gupta (5):
      drivers: add queue parameter in event processing callback
      net/dpaa2: add API's to support event eth adapter
      drivers: add net as dependency for event drivers
      event/dpaa2: support event eth adapter
      event/dpaa2: improve the err handling and log msg

Pavan Bhagavatula (4):
      eventdev: use new event enqueue in Rx adapter
      net/octeontx: add support for event Rx adapter
      event/octeontx: add support for event Rx adapter
      doc: add event octeontx Rx adapter limitation

 doc/guides/eventdevs/octeontx.rst              |   5 +
 drivers/Makefile                               |   2 +-
 drivers/bus/fslmc/portal/dpaa2_hw_pvt.h        |   4 +
 drivers/event/Makefile                         |   2 +-
 drivers/event/dpaa2/Makefile                   |   2 +
 drivers/event/dpaa2/dpaa2_eventdev.c           | 168 ++++++++++++++++++++++++-
 drivers/event/dpaa2/dpaa2_eventdev.h           |   8 ++
 drivers/event/dpaa2/dpaa2_hw_dpcon.c           |   2 +-
 drivers/event/octeontx/Makefile                |   1 +
 drivers/event/octeontx/ssovf_evdev.c           | 126 +++++++++++++++++++
 drivers/event/octeontx/ssovf_evdev.h           |   1 +
 drivers/event/octeontx/ssovf_worker.h          |  35 +++++-
 drivers/event/sw/sw_evdev_worker.c             |  14 ++-
 drivers/event/sw/sw_evdev_xstats.c             |   2 +-
 drivers/net/dpaa2/dpaa2_ethdev.c               |  62 +++++++++
 drivers/net/dpaa2/dpaa2_ethdev.h               |  15 +++
 drivers/net/dpaa2/dpaa2_rxtx.c                 |  20 +++
 drivers/net/dpaa2/rte_pmd_dpaa2_version.map    |   7 ++
 drivers/net/octeontx/base/octeontx_pkivf.c     |  65 ----------
 drivers/net/octeontx/base/octeontx_pkivf.h     | 126 ++++++++++++++++++-
 drivers/net/octeontx/octeontx_ethdev.c         |   3 +-
 drivers/net/octeontx/octeontx_rxtx.c           | 108 +---------------
 drivers/net/octeontx/octeontx_rxtx.h           |  89 +++++++++++++
 lib/librte_eventdev/rte_event_eth_rx_adapter.c |   2 +-
 lib/librte_eventdev/rte_eventdev_version.map   |   3 +-
 25 files changed, 681 insertions(+), 191 deletions(-)

             reply	other threads:[~2017-10-25 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 12:06 Jerin Jacob [this message]
2017-10-25 14:33 ` 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=20171025120640.GA7741@jerin \
    --to=jerin.jacob@caviumnetworks.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).