From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [pull-request] next-eventdev 19.11 RC2
Date: Mon, 4 Nov 2019 17:15:39 +0000 [thread overview]
Message-ID: <BYAPR18MB242410F2183850A0757B5448C87F0@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
The following changes since commit 19397c7bf2545e6adab41b657a1f1da3c7344e7b:
version: 19.11-rc1 (2019-10-27 22:46:22 +0100)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to c952045d4a81d16f745ee0080e6870fafd9a220a:
doc: add application usage guide for l2fwd-event (2019-11-04 22:39:36 +0530)
----------------------------------------------------------------
Pavan Nikhilesh (7):
event/octeontx2: use wfe while waiting for head
event/octeontx2: remove hotspots by prefetching data
examples/l2fwd-event: add default poll mode routines
examples/l2fwd-event: add infra for eventdev
examples/l2fwd-event: add service core setup
examples/l2fwd-event: add eventdev main loop
examples/l2fwd-event: add graceful teardown
Sunil Kumar Kori (5):
examples/l2fwd-event: add infra to split eventdev framework
examples/l2fwd-event: add event device setup
examples/l2fwd-event: add eventdev queue and port setup
examples/l2fwd-event: add event Rx/Tx adapter setup
doc: add application usage guide for l2fwd-event
MAINTAINERS | 6 +
doc/guides/rel_notes/release_19_11.rst | 6 +
doc/guides/sample_app_ug/index.rst | 1 +
doc/guides/sample_app_ug/intro.rst | 5 +
doc/guides/sample_app_ug/l2_forward_event.rst | 698 +++++++++++++++++++++++
drivers/event/octeontx2/otx2_worker.h | 31 +-
drivers/event/octeontx2/otx2_worker_dual.c | 1 +
examples/Makefile | 1 +
examples/l2fwd-event/Makefile | 62 ++
examples/l2fwd-event/l2fwd_common.c | 97 ++++
examples/l2fwd-event/l2fwd_common.h | 132 +++++
examples/l2fwd-event/l2fwd_event.c | 393 +++++++++++++
examples/l2fwd-event/l2fwd_event.h | 73 +++
examples/l2fwd-event/l2fwd_event_generic.c | 315 ++++++++++
examples/l2fwd-event/l2fwd_event_internal_port.c | 294 ++++++++++
examples/l2fwd-event/l2fwd_poll.c | 177 ++++++
examples/l2fwd-event/l2fwd_poll.h | 25 +
examples/l2fwd-event/main.c | 579 +++++++++++++++++++
examples/l2fwd-event/meson.build | 23 +
examples/meson.build | 2 +-
20 files changed, 2917 insertions(+), 4 deletions(-)
create mode 100644 doc/guides/sample_app_ug/l2_forward_event.rst
create mode 100644 examples/l2fwd-event/Makefile
create mode 100644 examples/l2fwd-event/l2fwd_common.c
create mode 100644 examples/l2fwd-event/l2fwd_common.h
create mode 100644 examples/l2fwd-event/l2fwd_event.c
create mode 100644 examples/l2fwd-event/l2fwd_event.h
create mode 100644 examples/l2fwd-event/l2fwd_event_generic.c
create mode 100644 examples/l2fwd-event/l2fwd_event_internal_port.c
create mode 100644 examples/l2fwd-event/l2fwd_poll.c
create mode 100644 examples/l2fwd-event/l2fwd_poll.h
create mode 100644 examples/l2fwd-event/main.c
create mode 100644 examples/l2fwd-event/meson.build
next reply other threads:[~2019-11-04 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 17:15 Jerin Jacob Kollanukkaran [this message]
2019-11-07 11:30 ` 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=BYAPR18MB242410F2183850A0757B5448C87F0@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).