From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [pull-request] next-eventdev 20.02 RC1
Date: Wed, 15 Jan 2020 11:57:54 +0000 [thread overview]
Message-ID: <BYAPR18MB242475FC94F0B7D5B6C8D6A0C8370@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
Following items moved to RC2:
a) Eventdev l3fwd integration
http://patches.dpdk.org/patch/64446/
Status:
- Addressed the review comments from NXP
- Got the Acked-by from NXP after testing on their HW.
- Addressed the first set of review comments from Konstantin
- Pushing to RC2 to enable to more review if needed.
b) Eventdev feature matrix documentation
http://patches.dpdk.org/patch/63511/
The following changes since commit 31bb45bcfdf5d67737eab17747b383775c9c36ae:
ci: add travis ci support for native aarch64 (2020-01-14 09:45:23 +0100)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to 0b6ee9a9a5e13866cd603cd116d25914af966e2a:
event/octeontx2: relax memory requirement for event timers (2020-01-15 17:17:16 +0530)
----------------------------------------------------------------
Mattias Rönnblom (3):
event/dsw: add by-name xstats retrieval
event/dsw: immediately flush buffers on zero-sized enqueue
event/dsw: avoid credit leak on oversized enqueue bursts
Pavan Nikhilesh (6):
examples/l2fwd-event: fix event device config
examples/l2fwd-event: fix ethdev RSS setup
test/eventdev: fix unintended vdev creation
test/eventdev: fix octeontx2 event device name
event/octeontx2: fix device name in device info
event/octeontx2: relax memory requirement for event timers
app/test/test_eventdev.c | 8 +-
drivers/event/dsw/dsw_event.c | 37 ++++--
drivers/event/dsw/dsw_xstats.c | 144 +++++++++++++++++------
drivers/event/octeontx2/otx2_evdev.h | 2 +-
drivers/event/octeontx2/otx2_tim_evdev.c | 11 +-
drivers/event/sw/sw_evdev_xstats.c | 2 -
examples/l2fwd-event/l2fwd_common.c | 11 ++
examples/l2fwd-event/l2fwd_event.c | 2 +-
examples/l2fwd-event/l2fwd_event_generic.c | 9 +-
examples/l2fwd-event/l2fwd_event_internal_port.c | 11 +-
10 files changed, 174 insertions(+), 63 deletions(-)
next reply other threads:[~2020-01-15 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 11:57 Jerin Jacob Kollanukkaran [this message]
2020-01-16 18:38 ` 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=BYAPR18MB242475FC94F0B7D5B6C8D6A0C8370@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.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).