DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "'dev@dpdk.org'" <dev@dpdk.org>,
	'Nipun Gupta' <nipun.gupta@nxp.com>,
	"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-dev]  [pull-request] next-eventdev 19.11 RC1 - Iteration 2
Date: Fri, 18 Oct 2019 08:19:27 +0000	[thread overview]
Message-ID: <BYAPR18MB2424120243A00ABDEDBE6408C86C0@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)

The following changes since commit b36f587f010bba421a8fd0b4c383276ecb796ae3:

  rcu: fix spurious thread unregister (2019-10-18 06:13:36 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 6e547f64f32ff2a3831d21931156c571e8d90f39:

  event/dpaa2: support Tx adapter (2019-10-18 13:33:09 +0530)

----------------------------------------------------------------

Changes pushed to post RC1.

1) Crypto adapter fixes
http://patches.dpdk.org/project/dpdk/list/?series=6648&state=*

2) l2fwd-event application

http://patches.dpdk.org/project/dpdk/list/?series=6839 

Nipun Gupta (5):
      eventdev: flag to identify same destined packets enqueue
      event/dpaa: fix number of supported atomic flows
      event/dpaa: support Tx adapter
      event/dpaa2: set priority as per the dpcon device
      event/dpaa2: support Tx adapter

 app/test-eventdev/test_pipeline_common.h           |  6 +-
 .../prog_guide/event_ethernet_tx_adapter.rst       |  3 +-
 doc/guides/rel_notes/release_19_11.rst             |  7 +-
 drivers/bus/fslmc/portal/dpaa2_hw_pvt.h            | 11 +++
 drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c        | 10 ++-
 drivers/crypto/dpaa2_sec/dpaa2_sec_event.h         |  2 +-
 drivers/event/dpaa/dpaa_eventdev.c                 | 76 ++++++++++++++++--
 drivers/event/dpaa/dpaa_eventdev.h                 |  2 +-
 drivers/event/dpaa2/Makefile                       |  2 +-
 drivers/event/dpaa2/dpaa2_eventdev.c               | 92 ++++++++++++++++++----
 drivers/event/dpaa2/dpaa2_eventdev.h               | 14 +---
 drivers/event/octeontx/ssovf_evdev.c               |  1 +
 drivers/event/octeontx2/otx2_evdev.c               |  2 +
 drivers/net/dpaa2/dpaa2_ethdev.c                   | 11 ++-
 drivers/net/dpaa2/dpaa2_ethdev.h                   |  2 +-
 examples/eventdev_pipeline/pipeline_worker_tx.c    |  2 +-
 lib/librte_eventdev/Makefile                       |  2 +-
 lib/librte_eventdev/meson.build                    |  2 +-
 lib/librte_eventdev/rte_event_eth_tx_adapter.h     | 19 ++++-
 lib/librte_eventdev/rte_eventdev.c                 |  1 +
 lib/librte_eventdev/rte_eventdev.h                 | 10 +++
 21 files changed, 225 insertions(+), 52 deletions(-)

             reply	other threads:[~2019-10-18  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  8:19 Jerin Jacob Kollanukkaran [this message]
2019-10-23 14:22 ` Thomas Monjalon
2019-10-30 17:33 ` Jerin Jacob

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=BYAPR18MB2424120243A00ABDEDBE6408C86C0@BYAPR18MB2424.namprd18.prod.outlook.com \
    --to=jerinj@marvell.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=nipun.gupta@nxp.com \
    --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).