From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: david.marchand@redhat.com
Subject: Re: [dpdk-dev] [dpdk-announce] [HELP REQUIRED] call for reviews
Date: Wed, 1 Apr 2020 10:11:50 +0100 [thread overview]
Message-ID: <e0b60892-1627-a28c-8953-b58f2f7e2e56@redhat.com> (raw)
In-Reply-To: <10038126.3WhfQktd6Z@xps>
On 01/04/2020 02:29, Thomas Monjalon wrote:
> Hi,
>
> DPDK 20.05-rc1 is planned to be released in less than three weeks.
> This is challenging because some patches are missing reviews.
>
> We all want to have our code reviewed and accepted.
> It will happen if everybody take time to read ideas,
> comment the designs and review the implementations.
>
> Before starting, do not hesitate to prepare yourself comfortably:
> https://www.jango.com/browse_music
>
> Below are some suggested readings, please pick one or more in the list:
>
> - gcc 10 support
> http://inbox.dpdk.org/dev/20200325141137.7088-1-ktraynor@redhat.com/
Also this one from Gavin,
http://inbox.dpdk.org/dev/20200307155629.45021-1-gavin.hu@arm.com/
>
> - clean-up compiler hint attributes
> http://inbox.dpdk.org/dev/20200210162032.1177478-1-thomas@monjalon.net/
>
> - data type for AVX512
> http://inbox.dpdk.org/dev/1583757826-375246-2-git-send-email-vladimir.medvedkin@intel.com/
>
> - helpers for bit operations
> http://inbox.dpdk.org/dev/20200309095410.28983-2-joyce.kong@arm.com/
>
> - C11 atomics
> http://inbox.dpdk.org/dev/1584407863-774-2-git-send-email-phil.yang@arm.com/
> http://inbox.dpdk.org/dev/a6df56db-b0d3-2e45-c872-1f3eb54b1aad@ericsson.com/
>
> - ring enhancemements
> http://inbox.dpdk.org/dev/20200331164330.28854-1-konstantin.ananyev@intel.com/
> http://inbox.dpdk.org/dev/20200224203931.21256-1-honnappa.nagarahalli@arm.com/
> http://inbox.dpdk.org/dev/2445314.H8VbNj7W2P@xps/
>
> - basic memory management for Windows
> http://inbox.dpdk.org/dev/20200330041026.784624-1-dmitry.kozliuk@gmail.com/
>
> - cleanup more resources on shutdown
> http://inbox.dpdk.org/dev/20200104013341.19809-1-stephen@networkplumber.org/
>
> - probing control
> http://inbox.dpdk.org/dev/2593334.B0Pyx7erxp@xps/
>
> - ethdev close behaviour and usage
> http://inbox.dpdk.org/dev/1913442.o4kTbAZ4gJ@xps/
>
> - vectorize virtio packed ring datapath
> http://inbox.dpdk.org/dev/20200327165412.87359-1-yong.liu@intel.com/
>
> - clean-up NIC features matrix in documentation
> http://inbox.dpdk.org/dev/20200311230136.63452-1-thomas@monjalon.net/
>
> - fixes and tests for rte_security
> http://inbox.dpdk.org/dev/20200312151654.7218-1-l.wojciechow@partner.samsung.com/
>
> - nodes graph as packet processing pipeline
> http://inbox.dpdk.org/dev/20200331192945.2466880-1-jerinj@marvell.com/
>
> - telemetry rework
> http://inbox.dpdk.org/dev/20200319171907.60891-1-ciara.power@intel.com/
>
> - tracepoints compatible with LTTng
> http://inbox.dpdk.org/dev/20200329144342.1543749-1-jerinj@marvell.com/
>
> - internal symbol marking
> http://inbox.dpdk.org/dev/1929042.qExNQAuVzC@xps/
>
>
> And to prepare next releases, some design discussions need to progress:
>
> - VFIO token for PF
> http://inbox.dpdk.org/dev/20200305043311.17065-1-vattunuru@marvell.com/
>
> - IF proxy
> http://inbox.dpdk.org/dev/20200310111037.31451-1-aostruszka@marvell.com/
>
> - ethdev capabilities and feature enabling
> http://inbox.dpdk.org/dev/13121897.9FIjf2LrnR@xps/
> http://inbox.dpdk.org/dev/8032312.HfnmF1KY9p@xps/
> http://inbox.dpdk.org/dev/20200319075851.GA26440@chelsio.com/
>
>
> Thanks a lot for helping releases to happen!
>
>
next prev parent reply other threads:[~2020-04-01 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 1:29 Thomas Monjalon
2020-04-01 9:11 ` Kevin Traynor [this message]
2020-06-26 16:43 Thomas Monjalon
2020-06-28 7:10 ` Or Gerlitz
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=e0b60892-1627-a28c-8953-b58f2f7e2e56@redhat.com \
--to=ktraynor@redhat.com \
--cc=david.marchand@redhat.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).