DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: 'dpdk-dev' <dev@dpdk.org>
Subject: [dpdk-dev]  [pull-request] next-eventdev 20.02 RC2
Date: Tue, 28 Jan 2020 09:13:42 +0000	[thread overview]
Message-ID: <BYAPR18MB2424A39CA64C00E49DC2D813C80A0@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)

The following changes since commit c465e6b94be343303303f26b95f3c2ae4969063e:

  maintainers: set git tree for EAL and core libraries (2020-01-22 23:05:28 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 0c8f991f48949e0c0c128513625620f5137d3d5b:

  doc: update l3fwd user guide to support eventdev (2020-01-28 14:35:25 +0530)

----------------------------------------------------------------
Mattias Rönnblom (1):
      event/dsw: use custom element size ring for control

Pavan Nikhilesh (7):
      examples/l3fwd: add event device configuration
      examples/l3fwd: add event eth Rx/Tx adapter setup
      examples/l3fwd: add service core setup based on caps
      examples/l3fwd: add event lpm main loop
      examples/l3fwd: add event em main loop
      examples/l3fwd: add graceful teardown for eventdevice
      doc: update l3fwd user guide to support eventdev

Sunil Kumar Kori (4):
      examples/l3fwd: add framework for event device
      examples/l3fwd: split pipelines based on capability
      examples/l3fwd: add ethdev setup based on eventdev
      examples/l3fwd: add event port and queue setup

 MAINTAINERS                                |   1 +
 doc/guides/rel_notes/release_20_02.rst     |   5 +
 doc/guides/sample_app_ug/l3_forward.rst    |  79 ++++++-
 drivers/event/dsw/Makefile                 |   3 +
 drivers/event/dsw/dsw_evdev.c              |   9 +-
 drivers/event/dsw/dsw_evdev.h              |  10 +-
 drivers/event/dsw/dsw_event.c              |  16 +-
 drivers/event/dsw/meson.build              |   3 +
 examples/l3fwd/Makefile                    |   3 +-
 examples/l3fwd/l3fwd.h                     |  30 +++
 examples/l3fwd/l3fwd_em.c                  | 177 +++++++++++++++
 examples/l3fwd/l3fwd_em.h                  | 169 +++++++++-----
 examples/l3fwd/l3fwd_em_hlm.h              | 131 +++++++++++
 examples/l3fwd/l3fwd_em_sequential.h       |  26 +++
 examples/l3fwd/l3fwd_event.c               | 263 ++++++++++++++++++++++
 examples/l3fwd/l3fwd_event.h               |  86 +++++++
 examples/l3fwd/l3fwd_event_generic.c       | 303 +++++++++++++++++++++++++
 examples/l3fwd/l3fwd_event_internal_port.c | 279 +++++++++++++++++++++++
 examples/l3fwd/l3fwd_lpm.c                 | 203 +++++++++++++++++
 examples/l3fwd/main.c                      | 345 +++++++++++++++++++++++------
 examples/l3fwd/meson.build                 |   5 +-
 21 files changed, 2000 insertions(+), 146 deletions(-)
 create mode 100644 examples/l3fwd/l3fwd_event.c
 create mode 100644 examples/l3fwd/l3fwd_event.h
 create mode 100644 examples/l3fwd/l3fwd_event_generic.c
 create mode 100644 examples/l3fwd/l3fwd_event_internal_port.c

             reply	other threads:[~2020-01-28  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  9:13 Jerin Jacob Kollanukkaran [this message]
2020-02-04 19:10 ` 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=BYAPR18MB2424A39CA64C00E49DC2D813C80A0@BYAPR18MB2424.namprd18.prod.outlook.com \
    --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).