* [dpdk-dev] DPDK Release Status Meeting 17/05/2018
@ 2018-05-18 16:47 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2018-05-18 16:47 UTC (permalink / raw)
To: dev
For the last 3 weeks we have had an 30min inter-company weekly sync on the
release status of the current DPDK release.
It is mainly intended for DPDK Committers to discuss the status of the master
and sub-trees. It is also intended as an update for project managers who need
to track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just send
me and email and I will send you the invite. I will forward the minutes on a
weekly basis.
Please note in particular:
* The need for someone to manage the issues in Bugzilla
* The request for "Tested Platforms" information.
Minutes 17 May 2018 09:32
Agenda
RC4 Status
Validation
RC5
Participants:
Intel
Cavium
Mellanox
NXP
6Wind
RedHat
Debian
Canonical
RC4 Status
Status of the Subtrees
* Crypto
* About 4 patches remaining to be merged
* Next-net
* Will pull from virtio
* Also will pull from vendor subtrees
* Bug fix patches today on Intel sub-sub tree
* Thomas will continue to merge subtrees until RC5
* Thomas asked if we can we pull from subtrees more frequently
* Maintainers agreed
* All STV to test fixes on latest main
* Vhost
* Only 1 remaining patch to be reviewed/merged
* Can be merged soon
* Eventdev
* Nothing remaining to be merged
* Pipeline
* Nothing remaining to be merged
Validation status for RC4
* Intel
* No showstoppers after RC4
* Testing looking gook good
* More stable
* Mellanox
* Tracking defects
* Mainly PMD fixes
* Cavium
* Mainly driver fixes and testing
* NXP
* No major items
* Note: can all validation teams submit a Tested
Platforms section to the release notes. Like this:
http://dpdk.org/doc/guides/rel_notes/release_17_11.html#tested-platforms
GCC8
* DPDK will now compile with GCC8
* However Lagopus (and other applications) don't compile against DPDK
* Patches from Andy Green (24 patches) to address some/all of these issues
* Let's review the patches one-by-one
Issue with Clang build
* Fix submitted
Bugzilla
* We need someone to manage the open defects on Bugzilla
* Required task would be to check defects, set importance/priority, report
to this meeting once a week.
Vhost-user perf drop after CVE fixes.
* Perf drop higher than expected. 8% in vector 1-2% in other path.
* What should we do about this
* Mainly in the vector path
* Won't have time to fix in this release
* Very specific use case
* Will track in Bugzilla: https://dpdk.org/tracker/show_bug.cgi?id=48
* Will also document this as a known issue in the Release Notes
RC5+
* RC5 targeted for Monday 21 May
* RC6 for doc and critical fixes and deprecation notices
* Release date May 25th. 2018!!
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 24/05/2018
@ 2018-05-24 16:29 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2018-05-24 16:29 UTC (permalink / raw)
To: dev
The DPDK Release Status Meeting is mainly intended for DPDK Committers to
discuss the status of the master and sub-trees. It is also intended as an
update for project managers who need to track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just send
me and email and I will send you the invite. I will forward the minutes on a
weekly basis.
Minutes 24 May 2018
Agenda
* RC5 Status
* RC6 and Release
* Other items
Participants:
* Intel
* Cavium
* Mellanox
* NXP
* 6Wind
* RedHat
RC5 Status
* Testing
* Intel Testing
* No major issues
* No build issues
* NXP
* Good
* Cavium
* 1 issue found in bonding testing - patch submitted
* RC5 Main Issues
* Note, the following 2 issues will be included in the release. The
will be marked as known issues in the release notes.
* Bugzilla #50 - Secondary process launch is
unreliable.
https://dpdk.org/tracker/show_bug.cgi?id=50
Secondary process initialization was known to be unreliable before,
with numerous workarounds already being available and
documented. However, DPDK version 18.05 has introduced memory
subsystem rework, which has made situation worse due to much more
memory being pre-reserved at initialization.
* Bugzilla #48 -Unexpected performance regression since CVE-2018-1059
fix with vector path.
https://dpdk.org/tracker/show_bug.cgi?id=48
A small performance drop was expected with CVE-2018-1059 fix
integration. While this expectation is verified for mast cases
(less than 3% drop), a bigger drop is seen when using vector path in
guest with small packets.
RC6+
* Only critical fixes into RC6
* Docs also. Send deprecation notices.
* Planned for Friday 25 May. End of day.
* Automated test will run over weekend.
* Results will be evaluated on Monday 28th May.
* Depending on the results the release will be Monday or Tuesday 28th
or 29th May.
* All major contributors should evaluate on Monday and inform Thomas
of your results: Intel, Cavium, Mellanox, NXP, 6Wind, RedHat,
Debian, Canonical, etc.
* Note: can all major contributors submit a "Tested Platforms" section
to the release notes. Like this:
http://dpdk.org/doc/guides/rel_notes/release_17_11.html#tested-platforms
Other
* We will conduct a retrospective of 18.05 at next weeks
meeting. Please think about:
* What went well
* What went badly
* What we can do to improve
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 31/05/2018
@ 2018-05-31 17:18 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2018-05-31 17:18 UTC (permalink / raw)
To: dev
Minutes from the weekly DPDK Release Status Meeting.
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send me and email and I will send you the invite.
Minutes 31 May 2018
Agenda:
* DPDK 18.05 release.
* Retrospective on 18.05.
* Testing of stable releases.
Participants:
* Intel
* Cavium
* Mellanox
* NXP
* 6Wind
* RedHat
DPDK 18.05 release.
* DPDK 18.08 "The Venky Release" is out. \o/
* Thanks to all the maintainers and contributors.
* See the release notes for the full stats:
http://dpdk.org/ml/archives/announce/2018-May/000204.html
Retrospective on 18.05.
* What went well.
* Largest DPDK release ever.
* Lots of contributors from all the main companies involved in networking.
* Collaboration on major features between companies in the community.
* What didn't go so well.
* The release was very late and required a lot of release candidates.
* RC1 was late and low quality.
* Many major defects found in RC testing.
* Some reviews were slow or late.
* What can we do differently next time.
* Should we change the number of releases per year from 4 to 3 or 2?
* Merge earlier from subtrees: every 7-10 days.
* Push patches earlier.
* Review patches more critically. Does every feature/patch need to go in.
* Use unit tests more
* Make them a requirement for any sizeable code.
* Make them easier to write/use/run.
* Add a make/meson target for generating coverage results from units
tests. Any volunteers?
* Hold more strictly to the release milestone dates.
Testing of stable releases.
* Luca Boccassi asked about testing of the stable release.
* All major contributing companies should confirm test results on the stable
releases.
* Luca will send an email to the list about it:
http://dpdk.org/ml/archives/dev/2018-May/103249.html
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 06/07/2018
@ 2018-06-13 20:43 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2018-06-13 20:43 UTC (permalink / raw)
To: dev
DPDK Release Status Meeting 06/07/2018
======================================
Minutes from the weekly DPDK Release Status Meeting.
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send me and email and I will send you the invite.
Minutes 6 June 2018
-------------------
Agenda:
* New Patchwork v2.
* Roadmaps.
* Upcoming changes from Tech Board meeting.
* Proposal deadline.
* Backlog of old patches.
* Proposal Deadline.
* Memory rework.
* Applying patches to master.
* Subtrees.
Stable
* Testing from Intel ongoing.
* Mellanox: 17.11 + 18.02.
* RedHat: putting testing in place.
Participants:
* Intel
* Mellanox
* RedHat
* Broadcom
New Patchwork version.
* Patchwork upgraded to V2.0.2 - Thanks Thomas, Mellanox and Stephen Finucane.
* Now supports "Series" i.e., patchsets for new patches.
* New client available that supports applying a full patch series:
git-pw: http://patchwork.readthedocs.io/projects/git-pw/en/latest/
Roadmaps
* All contributing companies are encourages to send updated roadmaps for
18.08 and later: http://dpdk.org/dev/roadmap
* Intel, Mellanox and Broadcom committed to sending updates.
Upcoming changes from Tech Board meeting.
* Explicit time limits for reviews/commits. Acked patches will be committed
within 2 weeks. This has already been agreed previously and documented:
http://dpdk.org/doc/guides/contributing/patches.html#steps-to-getting-your-patch-merged
There was a new recommendation that non-acked, non-commented files will
be committed after 3 weeks if there are no objections/comments.
* Weekly merge. Subtrees to be merged on Thursdays. Master on Friday.
Backlog of old patches.
* There is a backlog of old patches:
http://dpdk.org/dev/patchwork/project/dpdk/list/?order=date
Need help cleaning this updated
Proposal Deadline
* 8 June
* Other dates: http://dpdk.org/dev/roadmap#dates
Memory rework
* Thomas reported that Mellanox are still seeing issues
* Will interface with Anatoly
* Will check with OvS
Applying patches to master
* Looking for patches to apply early.
* HyperV patches will be applied.
Subtrees
* Net: Not many patches yet
* Virtio: Quiet for now.
* Crypto: Nothing merged yet. 62 patches in the backlog.
Stable
* Testing from Intel ongoing.
* Mellanox: 17.11 + 18.02.
* RedHat: putting testing in place.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 14/07/2018
@ 2018-06-18 8:41 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2018-06-18 8:41 UTC (permalink / raw)
To: dev
DPDK Release Status Meeting 14/07/2018
======================================
Minutes from the weekly DPDK Release Status Meeting.
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send me and email and I will send you the invite.
Minutes 14 June 2018
--------------------
Agenda:
* Subtrees
* Reviews
* Bugzilla
* LTS GAP
* Design Review
Participants:
* Intel
* Cavium
* Mellanox
* 6Wind
* Broadcom
Subtrees
--------
* Next-Net - Started taking some patches.
* Next-Crypto - Nothing applied yet but 40 patches pending.
103 patches outstanding in Crypto and Compression.
* Next-virtio -No update.
* Next-Eventdev - Has started pulling in patches.
* Next-Ip-pipeline - No update.
* Master - Will pull trees at end on Friday/Saturday.
Bugzilla
--------
* We need a volunteer to manage the DPDK Bugzilla:
https://dpdk.org/tracker/
* Main task will be to review incoming defects and make sure they are
assigned to the right maintainer.
* The number of new defects is currently small so this shouldn't take more
than a 1-2 hours per week.
* If there isn't a volunteer then we will circulate the role, for each
release, between the main contributing companies.
LTS Maintainer Gap
------------------
* The current LTS/Stable releases and maintainers are:
http://dpdk.org/dev/roadmap#stable ::
Version Date End of life Maintainer
16.11.8 Aug 14 2018 Nov 2018 (LTS) Luca Boccassi
17.11.3 Jun 15 2018 Nov 2019 (LTS) Yuanhan Liu
18.02.2 Jun 15 2018 Jun 2018 Luca Boccassi
18.05.1 Aug 24 2018 Aug 2018 Christian Ehrhardt
18.08.1 Nov 16 2018 Nov 2018 Looking for volunteer
18.11.1 Jan 11 2019 Nov 2020 (LTS) Kevin Traynor
* Yuanhan will be stepping down after the next 17.11.x release.
* We are looking for another volunteer.
* Also many thanks to the current LTS/Stable maintainers.
Design Reviews
--------------
* If anyone would like to have an online design review/discussion of a
proposal for an new feature let me know and I will set it up. For examples,
if they have an RFC that could be better explained over a call with some
slides. We have very good discussions at the DPDK Userspace event and it
would be good to have similar discussions from time to time on major new
features.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 21/07/2018
@ 2018-06-22 12:13 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2018-06-22 12:13 UTC (permalink / raw)
To: dev
DPDK Release Status Meeting 21/07/2018
======================================
Minutes from the weekly DPDK Release Status Meeting.
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send me and email and I will send you the invite.
Minutes 21 June 2018
--------------------
Agenda:
* Subtrees
* Bugzilla
* New website
* Reviewathon
* Dates
Participants:
* Intel
* Cavium
* Mellanox
* NXP
* 6Wind
* Broadcom
Subtrees
--------
* Next-Net
* Not many more patches from last week. Will review/merge more this week.
* Removing old offload API. Help needed, Thomas offered.
* Updating CRC offload and updating examples for offload checks in ethdev
are more ethdev related work.
* Next-Crypto
* No new patches applied since last week.
* Investigating compilation issue.
* Will only be able to apply simpler patches until next week.
* Next-virtio
* No update.
* Next-Eventdev
* Issues with patches from Gage Eads @intel.
* Next-Ip-pipeline
* SofNIC patches will be merged through this tree.
* Master -
* Will review pending patches
* Let Thomas know if there are priority patches for review.
Bugzilla
--------
* Ajit Khaparde from Broadcom volunteered to maintain Bugzilla.
* Main task will be to review incoming defects and make sure they are
assigned to the right maintainer.
* We will review new bugs weekly at this call.
New Web Site
------------
* New DPDK website is available: https://www.dpdk.org/
* Many thanks to Thomas.
* Split in 2 entities. The first "main" for Marketing, Events and DPDK related
projects. The second "core" for DPDK only.
* The "main" website:
* Written in Wordpress - Managed by Linux Foundation.
* Request changes on web@dpdk.org
* Core:
* core.dpdk.org maintained by the community
* DPDK Specific
* No mention of other projects - even DTS
* Managed as separate server
* Hugo + Markdown
* Need to update contributing guide to explain workflow
* Looking for a volunteer to try this and write it up.
* All the URLs have changes - old URLs work with redirect. If not let Thomas
know.
Reviewathon
-----------
* We plan a Community Reviewathon, next Tuesday 26th June.
* Community will co-ordinate on IRC.
* Look for announcement of dev mailing list.
18.08 Dates
-----------
* Integration deadline: June 29, 2018. Soon my pretties, soon.
* Release: August 1, 2018.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 28/07/2018
@ 2018-06-28 10:31 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2018-06-28 10:31 UTC (permalink / raw)
To: dev
DPDK Release Status Meeting 28/07/2018
======================================
Minutes from the weekly DPDK Release Status Meeting.
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send me and email and I will send you the invite.
Minutes 28 June 2018
--------------------
Agenda:
* Subtrees
* Merge Deadline
* Reviewathon
* Bugzilla
Participants:
* Intel
* Mellanox
* Red Hat
* 6Wind
* Broadcom
Subtrees
--------
* Next-Net
* Some patches applied but some more to go in.
* Some of the next-net subtrees need to merge some more patches.
* Patch to remove old offload API still not sent to mailing list.
* CRC and RSS offload patches are not merged. More updates may be required
for RSS.
* Next-Crypto
* Applied some more patches but there is a big backlog.
* Asymmetric extension to cryptodev under review but some changes are
required. Unsure if it will make it on time. Already postponed from last
release so we want to get it into this release. Part of cryptodev so we
need to be careful.
* Other PMDs pending but changes are isolated. Less risk.
* Next-virtio
* 4-5 series pending.
* 3 are by Maxime so he is looking for external reviewers.
* Lack of reviews partially due to DPDK Summit China.
* Next-Eventdev
* No update.
* Next-Ip-pipeline
* Pull request sent.
* Master
* Lots of work.
* Lots of patches from Anatoly.
Merge Deadline
--------------
* Target date was Friday 29th July.
* All subtrees are behind on merging.
* Agreement to move merge deadline to Friday July 6th.
* RC1 will Monday July 9th.
* There will be a hard deadline on features in RC1.
* PMDs can go into RC2 .
* RC2 deadline will be July 14th.
* Release date is still August 1.
DPDK Summits
------------
* DPDK Summit China just finished, June 28, 2018:
https://www.dpdk.org/event/dpdk-summit-china-2018/
* DPDK Userspace, Dublin September 5-6, 2018. Call for Papers open:
https://www.dpdk.org/event/dpdk-userspace-dublin-2018/
Reviewathon
-----------
* Reviewathon happened on Tuesday 26th, via email and IRC.
* Mellanox and Intel were the main participants.
* We will run another one on Tuesday 3rd July.
* Mellanox and Intel, Read Hat and 6Wind agreed to participate.
Bugzilla
--------
* All maintainers should register with DPDK Bugzilla so issues can be assigned
to them for review. https://bugs.dpdk.org/
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 26/07/2018
@ 2018-07-26 10:52 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2018-07-26 10:52 UTC (permalink / raw)
To: dev
DPDK Release Status Meeting 26/07/2018
======================================
Minutes from the weekly DPDK Release Status Meeting.
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send me and email and I will send you the invite.
Minutes 26 July 2018
--------------------
Agenda:
* Subtrees
* RC1
* RC2
* Release Dates
* Compilation Testing/Issues
* Bugzilla
* Userspace
Participants:
* Intel
* Cavium
* Mellanox
* NXP
* Debian
* Broadcom
Subtrees
--------
* Next-Net
* Ready to pull.
* Next-Crypto
* Merged to master.
* Next-virtio
* Some patches/fixes for memory issues need to be applied.
Tiwei to merge.
* Next-Eventdev
* Patchset/PR ready.
* Next-Ip-pipeline
* Patchset/PR ready.
* Master
* Will merge patchset for autotest.
* Waiting for virtio patches.
* Will merge up to RC2 today.
RC1
---
* Fixes/patches submitted for issues identifies as High and Medium during
testing.
RC2
---
* RC2 target was Wednesday 25th July.
* New RC2 target is Thursday 26th July.
* Virtio memory related patches and fixes.
* Tiwei will push to virtio subtree.
* Will sync on IRC with Thomas.
* Qian will send a list of fix patches.
Release Dates
-------------
* RC2 target is Thursday 26th July.
* RC3 should be next Thursday Aug 2nd.
* If that is stable we may skip RC4 and go to release.
* Target release date is Wednesday Aug.
Compilation testing
-------------------
* FreeBSD 10.0 removed from compilation since it is deprecated.
* Will add FreeBSD 11.x instead.
* Docs need to be updated to reflect these changes. John to investigate.
* In the next release we should decide as a community what OS and kernel
versions will be supported. We should also discuss this at DPDK Userspace
Dublin.
* We should prepare patches for 18.11 with supported versions.
* We should also look at any upcoming issues with GCC 9.
* Pablo will run compilation test for Thomas prior to RC2.
* Luca, from Debian, highlighted the SuSE open build service that we could
potentially use to test packaging:
https://openbuildservice.org/
https://build.opensuse.org/
* NXP have tested 18.08-RC1 builds and will report back on any issues in RC2.
Bugzilla
--------
* Issue from the last 7 days:
https://bugs.dpdk.org/buglist.cgi?chfieldfrom=7d
Userspace
---------
* DPDK Userspace, Dublin September 5-6:
https://www.dpdk.org/event/dpdk-userspace-dublin-2018/
* Call for Papers closes Friday 27th July:
https://docs.google.com/forms/d/e/1FAIpQLSd5hfn58cTKWBcBO_eK6qKWAA5cG9BpPhBWZR_FMLIrgZKWuQ/viewform
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 02/08/2018
@ 2018-08-02 12:25 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2018-08-02 12:25 UTC (permalink / raw)
To: dev
DPDK Release Status Meeting 02/08/2018
======================================
Minutes from the weekly DPDK Release Status Meeting.
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send me and email and I will send you the invite.
Minutes 2 August 2018
--------------------
Agenda:
* RC2
* RC3
* Deprecation Notices
* FreeBSD
* Release Dates
Participants:
* Intel
* Cavium
* Mellanox
* NXP
* ARM
RC2
---
* Look okay overall from Intel testing.
* Some issues to be resolved in virtio/vhost.
RC3
---
RC3 targeted for Sunday 5th August.
Status of the subtrees:
* Next-Net
* Pull ongoing.
* Pulled virtio.
* Pulling from vendors.
* Next-Crypto
* 1 patch pending to be applied today.
* Next-virtio
* Pulled.
* Next-Eventdev
* No new patches.
* Next-Ip-pipeline
* Up to date.
Deprecation Notices
-------------------
Please ensure all deprecation notices are reviewed and acked:
http://patches.dpdk.org/project/dpdk/list/?q=deprecation
FreeBSD
-------
We are looking for a FreeBSD DPDK maintainer to keep the ports up to date and
fix minor incompatibility issues. Ideally someone who also works with the
FreeBSD community.
Release Dates
-------------
* RC3 targeted for Sunday Aug 5th.
* No RC4, although doc additions and minor cosmetic fixes will be accepted.
* Target release date is Thursday Aug 9th for release.
^ permalink raw reply [relevance 16%]
* [dpdk-dev] DPDK Release Status Meeting 24/01/2018
@ 2019-01-25 9:24 14% Mcnamara, John
0 siblings, 1 reply; 140+ results
From: Mcnamara, John @ 2019-01-25 9:24 UTC (permalink / raw)
To: dev
Cc: Mcnamara, John, Thomas Monjalon, Jerin Jacob, Akhil Goyal,
Dumitrescu, Cristian, Xu, Qian Q, Yongseok Koh, Maxime Coquelin,
Zhang, Qi Z, Shahaf Shuler, De Lara Guarch, Pablo, O'Hare,
Cathal, Yigit, Ferruh
Release Status Meeting 24/01/2018
28 June 2018
09:32
Agenda
------
* Subtrees
* Bugzilla
* Dates
Subtrees
--------
* Next-Net
* There are no critical/blocking issues. There is only a bunch of
patches merged, again nothing critical. Pulled from sub-trees.
It can be ready for Friday for rc4.
* Next-Crypto
* No patches
* Next-virtio
* Have prepared branch with 4 patches.
* Next-Eventdev
* No patches
* Next-Ip-pipeline
* No patches
* Master
* Documentation patches
RC4 target for Friday 25 January.
RC3 Testing
-----------
* No critical or very big issues for RC3 - from Intel Testing
LTS Testing
-----------
* Intel cannot test the LTS until after Chinese Spring Festival
* Should be able to start retesting in the week of Feb 18th
* Questions from Intel Test about the use of the Stable Tree.
Do people use it? Each stable/LTS release requires a lot of
testing and there are currently 3 releases to be tested.
Deprecation notices
-------------------
Please review the deprecation notices below:
* doc: add deprecation notice for meson: http://patches.dpdk.org/patch/49877/
* doc: add deprecation notice to remove rte meter color: http://patches.dpdk.org/patch/48712/
* doc: update API deprecation for device reset: http://patches.dpdk.org/patch/44990/
* doc: announce change of rte service API parameter type: http://patches.dpdk.org/patch/49987/
* doc: announce ring API change: http://patches.dpdk.org/patch/49961/
OVS 2.11 Status
---------------
* 2.11 branched from master January 18th.
* 4 week stabilization period.
* Release targeted February 18th~.
DPDK 19.05
----------
* Request for to try get some changes in early
* Agreement to accept proposed dates for 19.05
* Intel to submit patch to website to update dates
* Proposal Deadline: Friday 1 March 2019
* Merge deadline: Friday 22 March 2019
* RC1 release: Friday 29 March 2019
* Release: Friday 10 May 2019
^ permalink raw reply [relevance 14%]
* Re: [dpdk-dev] DPDK Release Status Meeting 24/01/2018
@ 2019-02-01 16:57 10% ` Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2019-02-01 16:57 UTC (permalink / raw)
To: Aaron Conole, Jay Rolette
Cc: dev, Thomas Monjalon, Jerin Jacob, Akhil Goyal, Dumitrescu,
Cristian, Xu, Qian Q, Yongseok Koh, Maxime Coquelin, Zhang, Qi Z,
Shahaf Shuler, De Lara Guarch, Pablo, O'Hare, Cathal, Yigit,
Ferruh, Kevin Traynor, Timothy Redaelli
> -----Original Message-----
> From: Aaron Conole [mailto:aconole@redhat.com]
> Sent: Friday, January 25, 2019 9:16 PM
> To: Jay Rolette <rolette@infinite.io>
> Cc: Mcnamara, John <john.mcnamara@intel.com>; dev@dpdk.org; Thomas
> Monjalon <thomas@monjalon.net>; Jerin Jacob
> <jerin.jacob@caviumnetworks.com>; Akhil Goyal <akhil.goyal@nxp.com>;
> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q
> <qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin
> <maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf
> Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; O'Hare, Cathal
> <cathal.ohare@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; Kevin
> Traynor <ktraynor@redhat.com>; Timothy Redaelli <tredaelli@redhat.com>
> Subject: Re: [dpdk-dev] DPDK Release Status Meeting 24/01/2018
>
> Jay Rolette <rolette@infinite.io> writes:
>
> >> * Questions from Intel Test about the use of the Stable Tree.
> >> Do people use it? Each stable/LTS release requires a lot of
> >> testing and there are currently 3 releases to be tested.
> >
> > We do @ infinite io.
>
> +1. Red Hat also uses the LTS releases.
Hi,
I should have been clearer on this. I meant the non-LTS "stable" release (the one we maintain for one release cycle). Historically it was meant for CVEs and hot-fixes on the head release. The question related to that stable release and whether people use it.
As suggested on the maintainers call the other day I'll probably put together a survey to find out.
The utility of the LTS releases isn't in question. :-)
John
^ permalink raw reply [relevance 10%]
* [dpdk-dev] DPDK Release Status Meeting 28/2/2019
@ 2019-03-01 16:34 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2019-03-01 16:34 UTC (permalink / raw)
To: dpdk-dev
Cc: Stokes, Ian, Thomas Monjalon, Jerin Jacob, Yigit, Ferruh, Akhil,
Goyal, Dumitrescu, Cristian, Xu, Qian Q, Yongseok Koh,
Maxime Coquelin, Zhang, Qi Z, Shahaf Shuler, De Lara Guarch,
Pablo
Minutes 28 February 2019
------------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Opens
Release Dates
-------------
* v19.05 dates, no change:
* Proposal Deadline: Friday, 1 March
* RC1: Friday, 29 March
* Release: Friday, 10 May
* Schedule web page updated accordingly:
http://core.dpdk.org/roadmap/#dates
* v19.08 proposal, please comment:
* Proposal/V1 Friday 07 June 2019
* Integration/Merge/RC1 Friday 05 July 2019
* Release Thurs 01 August 2019
Subtrees
--------
* Next-Net
* No updates
* Next-virtio
* Some patches to review
* Next-Crypto
* Patches scheduled. Merged planned for 1 week
* Need a new sub-tree maintainer
* Next-Eventdev
* No patches
* Next-Ip-pipeline
* Some patches available
* Master
* AF_XDP on target for submission in this release
* Questions about Ipsec and QAT additions. Should also be on track.
* The locking patches from ARM will have a big impact. The community
is asked to review and test them carefully.
LTS and stable
--------------
* Intel has completed testing for 16.11.8 or 17.11.5. Some issues were
found but they are currently investigating if these are genuine issues.
* v18.11.1-rc1 and v18.08.1-rc3 are available for testing
OvS
---
* 2.11.0 was released February 28
Static code analysis tools
--------------------------
* Coverity is back but new analyses aren't running
* Some other suggestions:
* CPPcheck: run periodically by Ferruh
* Sonarcloud: https://sonarcloud.io/
* LGTM: https://lgtm.com/
* Infer: https://fbinfer.com/
* We are looking for volunteers to run some of the other tools on the
DPDK code base to see if they are suitable
Opens
-----
* Akhil is looking for co-maintainer for crypto sub-tree,
any volunteer please contact to Akhil or Thomas.
* Coverity is partially back, but new analyses aren't running
* Looking for suggestions from the community for a better or more stable
solutions
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to
discuss the status of the master tree and sub-trees, and for project
managers to track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 15%]
* Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
@ 2019-04-01 15:47 8% ` Mcnamara, John
2019-04-01 15:47 8% ` Mcnamara, John
0 siblings, 1 reply; 140+ results
From: Mcnamara, John @ 2019-04-01 15:47 UTC (permalink / raw)
To: David Marchand, Yigit, Ferruh
Cc: dpdk-dev, Stokes, Ian, Thomas Monjalon, Jerin Jacob, Akhil,
Goyal, Dumitrescu, Cristian, Xu, Qian Q, Yongseok Koh,
Maxime Coquelin, Zhang, Qi Z, Shahaf Shuler, De Lara Guarch,
Pablo
> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Thursday, March 28, 2019 12:48 PM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John <john.mcnamara@intel.com>
> Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.stokes@intel.com>; Thomas Monjalon <thomas@monjalon.net>; Jerin Jacob <jerin.jacob@caviumnetworks.com>; Akhil, Goyal <akhil.goyal@nxp.com>; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q <qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin <maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
>
> On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Coverity
> --------
>
> * Coverity is back on, John run a new scan with latest code:
> https://scan.coverity.com/projects/dpdk-data-plane-development-kit
>
> The "components" mappings seem quite old/invalid to me:
> - we still have the old pmds path à la lib/librte_pmd_XXX
> - pmd_bond points to an drivers/net/bond/.
> - pmd_mlx4 points to drivers/net/ixgbe/.
>
> And others catches almost everything (400k loc).
>
> John, can you fix it?
Yes. Let me know the mappings/changes you want to make and I can implement them or we can make you and admin and you can do it.
John
^ permalink raw reply [relevance 8%]
* Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
2019-04-01 15:47 8% ` Mcnamara, John
@ 2019-04-01 15:47 8% ` Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2019-04-01 15:47 UTC (permalink / raw)
To: David Marchand, Yigit, Ferruh
Cc: dpdk-dev, Stokes, Ian, Thomas Monjalon, Jerin Jacob, Akhil,
Goyal, Dumitrescu, Cristian, Xu, Qian Q, Yongseok Koh,
Maxime Coquelin, Zhang, Qi Z, Shahaf Shuler, De Lara Guarch,
Pablo
> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Thursday, March 28, 2019 12:48 PM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John <john.mcnamara@intel.com>
> Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.stokes@intel.com>; Thomas Monjalon <thomas@monjalon.net>; Jerin Jacob <jerin.jacob@caviumnetworks.com>; Akhil, Goyal <akhil.goyal@nxp.com>; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q <qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin <maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
>
> On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Coverity
> --------
>
> * Coverity is back on, John run a new scan with latest code:
> https://scan.coverity.com/projects/dpdk-data-plane-development-kit
>
> The "components" mappings seem quite old/invalid to me:
> - we still have the old pmds path à la lib/librte_pmd_XXX
> - pmd_bond points to an drivers/net/bond/.
> - pmd_mlx4 points to drivers/net/ixgbe/.
>
> And others catches almost everything (400k loc).
>
> John, can you fix it?
Yes. Let me know the mappings/changes you want to make and I can implement them or we can make you and admin and you can do it.
John
^ permalink raw reply [relevance 8%]
* [dpdk-dev] [PATCH v1] doc: fix spelling errors reported by aspell
@ 2019-04-03 13:26 3% John McNamara
2019-04-03 13:26 3% ` John McNamara
0 siblings, 1 reply; 140+ results
From: John McNamara @ 2019-04-03 13:26 UTC (permalink / raw)
To: dev; +Cc: John McNamara
Signed-off-by: John McNamara <john.mcnamara@intel.com>
---
Some notes on this.
It is probably best not to apply this patch until just before the release
since it could potentially create a lot of conflicts. I'll resubmit a v2
prior to the 19.05 release.
The fixes list is below. I didn't include them in the commit message
since I don't think the effort of backporting is worth it.
Fixes: a6531d58b415 ("compressdev: replace mbuf scatter gather flag")
Fixes: 58abf6e77c6b ("doc: add contributors guide")
Fixes: 3728e9ba7739 ("crypto/aesni_mb: support IPSec Multi-buffer lib v0.46")
Fixes: 2717246ecd7d ("cryptodev: replace mbuf scatter gather flag")
Fixes: 02545b6ca29a ("doc: update build instructions for qat PMDs")
Fixes: 4c07e0552f0a ("crypto/scheduler: add multicore scheduling mode")
Fixes: c7aa67f5a9e4 ("doc: add eventdev OPDL PMD guide")
Fixes: 0857b9421138 ("doc: add event device and software eventdev")
Fixes: 206b6ba882cf ("doc: add VF live migration howto with bonded virtio")
Fixes: 6993fe1375c1 ("doc: add VM live migration howto with vhost-user")
Fixes: 3e0ceb9f17ff ("doc: add basic howto for flow API")
Fixes: 6e9270eab112 ("doc: add telemetry how-to")
Fixes: 0ba3870e7559 ("doc: add guide to use virtio-user as exceptional path")
Fixes: 6ef75e405d5a ("doc: add af_packet PMD guide")
Fixes: 3d38e3dcf197 ("net/atlantic: implement Rx path")
Fixes: 6c2809628cd5 ("net/cxgbe: improve latency for slow traffic")
Fixes: cda260a4ac1a ("net/cxgbe: add option to keep outer VLAN tag in QinQ")
Fixes: 0c504f6950b6 ("net/dpaa: support push mode")
Fixes: 846a8305f277 ("doc: add DPAA2 NIC details")
Fixes: 61e093398fbc ("doc: add instructions for WC in ENAv2")
Fixes: 65313f1a822a ("doc: add guide for ENETC PMD")
Fixes: 0543f9d24ae1 ("net/enic: flow API documentation")
Fixes: 13e855a3b996 ("doc: add inline crypto feature")
Fixes: 04c8542f96f7 ("net/i40e: set TC strict priority mode")
Fixes: 621c5c1db2b1 ("doc: add ixgbe known issue with legacy interrrupt")
Fixes: 75e2bc54c018 ("net/kni: add KNI PMD")
Fixes: 2c0dd7b69fb0 ("config: add static linkage of mlx dependency")
Fixes: 0280f2812284 ("doc: add mlx5 E-Switch VXLAN tunnels limitations")
Fixes: 2c0dd7b69fb0 ("config: add static linkage of mlx dependency")
Fixes: 7d6bf6b866b8 ("net/mlx5: add Multi-Packet Rx support")
Fixes: 0ba610ca1d17 ("net/mvpp2: document MTR and TM usage")
Fixes: 4b048f352c01 ("doc: clarify usage of netvsc PMD")
Fixes: ef28aa96e53b ("net/nfp: support multiprocess")
Fixes: c7cb2d7a5f2a ("net/sfc: add device configuration checks")
Fixes: 8cb45c97d396 ("net/sfc: add unknown unicast/multicast match in flow API")
Fixes: c22d3c508e0c ("net/sfc: support parameter to choose performance profile")
Fixes: a5e1231f099b ("net/szedata2: do not affect Ethernet interfaces")
Fixes: bcab6c1d27fa ("net/tap: allow user MAC to be passed as args")
Fixes: ceccf8dc7c3d ("doc: create NXP DPAA platform guide")
Fixes: b84c108742a9 ("doc: create NXP DPAA2 platform guide")
Fixes: 4935e1e9f76e ("bbdev: introduce wireless base band device lib")
Fixes: a584d3bea902 ("doc: add compressdev library guide")
Fixes: 0318c02b57cf ("doc: add cryptodev chapter in prog guide")
Fixes: c149818b0e51 ("doc: add note on multiple crypto vdevs")
Fixes: 0318c02b57cf ("doc: add cryptodev chapter in prog guide")
Fixes: 31850d26850e ("doc: add cryptodev sample code")
Fixes: b9209dc21999 ("doc: add asymmetric crypto in programmer guide")
Fixes: a5d7a3f77ddc ("unify tools naming")
Fixes: 0dd62a01874a ("doc: add EFD library section in programmers guide")
Fixes: b31739328354 ("doc: update guides for memory subsystem")
Fixes: 3810ae435783 ("eventdev: add interrupt driven queues to Rx adapter")
Fixes: c1eaab510dba ("eventdev: add callback for Rx adapter SW transfers")
Fixes: 7358c91ffa85 ("doc: add eventdev library to programmers guide")
Fixes: 50bdac5916d9 ("flow_classify: remove table id parameter from API")
Fixes: fdec9301f52d ("doc: add flow classify guides")
Fixes: 9ef6cb1a1583 ("doc: add IPsec library guide")
Fixes: 89397a01ce4a ("kni: set default carrier state of interface")
Fixes: 349950ddb9c5 ("metrics: add information metrics library")
Fixes: 2ad7ba9a6567 ("bitrate: add bitrate statistics library")
Fixes: 5cd3cac9ed22 ("latency: added new library for latency stats")
Fixes: e22266669e86 ("doc: add IPC guide")
Fixes: 9d5ba88c2d41 ("doc: add ARM profiling methods")
Fixes: 7307cf6333ca ("ethdev: add raw encapsulation action")
Fixes: 6f1c2168bccb ("ethdev: add generic TTL rewrite actions")
Fixes: 40ff8c99ea99 ("doc: add details of security library")
Fixes: e660897d8a0a ("doc: describe traffic management API")
Fixes: 9ba1e744ab65 ("vhost: add a flag to enable dequeue zero copy")
Fixes: ef1e8ede3da5 ("raw/ifpga: add Intel FPGA bus rawdev driver")
Fixes: 86fa6c57a175 ("doc: add known igb_uio issue for i40e")
Fixes: b667029e9096 ("doc: add Linux 4.10.0 known issue in release notes")
Fixes: a32ca9a4ebc1 ("mk: fix scope of disabling AVX512F support")
Fixes: c9b13d944088 ("doc: update release notes for 17.11")
Fixes: 1ffee690eaa1 ("examples/bbdev: add sample app")
Fixes: 1094ca96689c ("doc: add SW eventdev pipeline to sample app guide")
Fixes: fdec9301f52d ("doc: add flow classify guides")
Fixes: bef33b0a9d58 ("doc: add new introduction to sample app guides")
Fixes: 71f2e9ba7d8c ("doc: update IP pipeline application guide")
Fixes: ec17993a145a ("examples/ipsec-secgw: support security offload")
Fixes: 02dc5b7d58c7 ("doc: update ipsec-secgw guide and release notes")
Fixes: 4d1a771bd88d ("doc: add guide for performance-thread example")
Fixes: 331ce43dc564 ("doc: add policer table details for metering application")
Fixes: 474572d2ae5a ("app/pipeline: move from test directory")
Fixes: a971c509a523 ("doc: update vhost sample guide")
Fixes: e3075e969eff ("doc: add driver limitation for vhost dequeue zero copy")
Fixes: db75c7af19bb ("examples/vhost_scsi: introduce a new sample app")
Fixes: 50ac590ff826 ("doc: update VM power manager sample guide")
Fixes: a63504a90f6a ("examples/power: add JSON string handling")
Fixes: 50ac590ff826 ("doc: update VM power manager sample guide")
Fixes: fb73e096110a ("app/testpmd: enable device hotplug monitoring")
Fixes: 3c156061b938 ("app/testpmd: add noisy neighbour forwarding mode")
Fixes: a67857e97ba8 ("doc: clarify usage of testpmd MAC forward mode")
Fixes: 8d9d4c2428be ("app/testpmd: update softnic mode documentation")
Fixes: c4e04283abee ("doc: fix literal block in testpmd guide")
Fixes: 0aeb7077d171 ("doc: add 802.3ad modes in testpmd guide")
Fixes: 5b590fbe09b6 ("app/testpmd: add traffic management forwarding mode")
Fixes: 708d0bcb72c2 ("app/testpmd: add commands to modify TTL")
Fixes: e977e4199a8d ("app/testpmd: add commands to load/unload BPF filters")
Fixes: c6baca7adc94 ("doc: describe new performance test application")
Fixes: 98a7ea332ba3 ("fix typos using codespell utility")
Fixes: c6baca7adc94 ("doc: describe new performance test application")
Fixes: 8a37f37fc243 ("app/procinfo: add --show-port")
Fixes: c13e8984404a ("app/procinfo: add --show-ring")
Fixes: bacf34762ac5 ("doc: update limitations in procinfo guide")
Fixes: 8723590ec603 ("doc: update bbdev test app guide")
doc/guides/compressdevs/overview.rst | 2 +-
doc/guides/contributing/patches.rst | 2 +-
doc/guides/cryptodevs/aesni_mb.rst | 2 +-
doc/guides/cryptodevs/overview.rst | 2 +-
doc/guides/cryptodevs/qat.rst | 2 +-
doc/guides/cryptodevs/scheduler.rst | 2 +-
doc/guides/eventdevs/opdl.rst | 4 +--
doc/guides/eventdevs/sw.rst | 4 +--
doc/guides/howto/lm_bond_virtio_sriov.rst | 2 +-
doc/guides/howto/lm_virtio_vhost_user.rst | 4 +--
doc/guides/howto/rte_flow.rst | 6 ++---
doc/guides/howto/telemetry.rst | 2 +-
.../howto/virtio_user_as_exceptional_path.rst | 8 +++---
doc/guides/nics/af_packet.rst | 4 +--
doc/guides/nics/atlantic.rst | 2 +-
doc/guides/nics/cxgbe.rst | 4 +--
doc/guides/nics/dpaa.rst | 2 +-
doc/guides/nics/dpaa2.rst | 2 +-
doc/guides/nics/ena.rst | 2 +-
doc/guides/nics/enetc.rst | 2 +-
doc/guides/nics/enic.rst | 2 +-
doc/guides/nics/features.rst | 2 +-
doc/guides/nics/i40e.rst | 2 +-
doc/guides/nics/ixgbe.rst | 4 +--
doc/guides/nics/kni.rst | 2 +-
doc/guides/nics/mlx4.rst | 2 +-
doc/guides/nics/mlx5.rst | 10 ++++----
doc/guides/nics/mvpp2.rst | 2 +-
doc/guides/nics/netvsc.rst | 2 +-
doc/guides/nics/nfp.rst | 4 +--
doc/guides/nics/sfc_efx.rst | 14 +++++-----
doc/guides/nics/szedata2.rst | 2 +-
doc/guides/nics/tap.rst | 2 +-
doc/guides/platform/dpaa.rst | 4 +--
doc/guides/platform/dpaa2.rst | 4 +--
doc/guides/prog_guide/bbdev.rst | 4 +--
doc/guides/prog_guide/compressdev.rst | 6 ++---
doc/guides/prog_guide/cryptodev_lib.rst | 14 +++++-----
doc/guides/prog_guide/dev_kit_build_system.rst | 2 +-
doc/guides/prog_guide/efd_lib.rst | 2 +-
doc/guides/prog_guide/env_abstraction_layer.rst | 2 +-
.../prog_guide/event_ethernet_rx_adapter.rst | 6 ++---
doc/guides/prog_guide/eventdev.rst | 6 ++---
doc/guides/prog_guide/flow_classify_lib.rst | 12 ++++-----
doc/guides/prog_guide/ipsec_lib.rst | 16 ++++++------
doc/guides/prog_guide/kernel_nic_interface.rst | 2 +-
doc/guides/prog_guide/metrics_lib.rst | 12 ++++-----
doc/guides/prog_guide/multi_proc_support.rst | 2 +-
doc/guides/prog_guide/profile_app.rst | 4 +--
doc/guides/prog_guide/rte_flow.rst | 6 ++---
doc/guides/prog_guide/rte_security.rst | 20 +++++++--------
doc/guides/prog_guide/traffic_management.rst | 2 +-
doc/guides/prog_guide/vhost_lib.rst | 2 +-
doc/guides/rawdevs/ifpga_rawdev.rst | 2 +-
doc/guides/rel_notes/known_issues.rst | 8 +++---
doc/guides/rel_notes/release_17_11.rst | 10 ++++----
doc/guides/sample_app_ug/bbdev_app.rst | 4 +--
doc/guides/sample_app_ug/eventdev_pipeline.rst | 2 +-
doc/guides/sample_app_ug/flow_classify.rst | 8 +++---
doc/guides/sample_app_ug/intro.rst | 2 +-
doc/guides/sample_app_ug/ip_pipeline.rst | 4 +--
doc/guides/sample_app_ug/ipsec_secgw.rst | 8 +++---
doc/guides/sample_app_ug/performance_thread.rst | 4 +--
doc/guides/sample_app_ug/qos_metering.rst | 2 +-
doc/guides/sample_app_ug/test_pipeline.rst | 2 +-
doc/guides/sample_app_ug/vhost.rst | 4 +--
doc/guides/sample_app_ug/vhost_scsi.rst | 2 +-
doc/guides/sample_app_ug/vm_power_management.rst | 14 +++++-----
doc/guides/testpmd_app_ug/run_app.rst | 10 ++++----
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 30 +++++++++++-----------
doc/guides/tools/cryptoperf.rst | 22 ++++++++--------
doc/guides/tools/proc_info.rst | 6 ++---
doc/guides/tools/testbbdev.rst | 2 +-
73 files changed, 192 insertions(+), 192 deletions(-)
diff --git a/doc/guides/compressdevs/overview.rst b/doc/guides/compressdevs/overview.rst
index 70bbe82..809e4e6 100644
--- a/doc/guides/compressdevs/overview.rst
+++ b/doc/guides/compressdevs/overview.rst
@@ -18,7 +18,7 @@ Supported Feature Flags
without making any modifications to it (no compression done).
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means PMD supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index d8404e6..3b2b174 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -8,7 +8,7 @@ Contributing Code to DPDK
This document outlines the guidelines for submitting code to DPDK.
-The DPDK development process is modelled (loosely) on the Linux Kernel development model so it is worth reading the
+The DPDK development process is modeled (loosely) on the Linux Kernel development model so it is worth reading the
Linux kernel guide on submitting patches:
`How to Get Your Change Into the Linux Kernel <https://www.kernel.org/doc/html/latest/process/submitting-patches.html>`_.
The rationale for many of the DPDK guidelines is explained in greater detail in the kernel guidelines.
diff --git a/doc/guides/cryptodevs/aesni_mb.rst b/doc/guides/cryptodevs/aesni_mb.rst
index 47f2ecc..b61802d 100644
--- a/doc/guides/cryptodevs/aesni_mb.rst
+++ b/doc/guides/cryptodevs/aesni_mb.rst
@@ -133,7 +133,7 @@ Extra notes
For AES Counter mode (AES-CTR), the library supports two different sizes for Initialization
Vector (IV):
-* 12 bytes: used mainly for IPSec, as it requires 12 bytes from the user, which internally
+* 12 bytes: used mainly for IPsec, as it requires 12 bytes from the user, which internally
are appended the counter block (4 bytes), which is set to 1 for the first block
(no padding required from the user)
diff --git a/doc/guides/cryptodevs/overview.rst b/doc/guides/cryptodevs/overview.rst
index 607e758..dd25b22 100644
--- a/doc/guides/cryptodevs/overview.rst
+++ b/doc/guides/cryptodevs/overview.rst
@@ -18,7 +18,7 @@ Supported Feature Flags
being the operation in-place (input address = output address).
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means pmd supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
index da9655c..651bf38 100644
--- a/doc/guides/cryptodevs/qat.rst
+++ b/doc/guides/cryptodevs/qat.rst
@@ -225,7 +225,7 @@ Dependency on the QAT kernel driver
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To use QAT an SRIOV-enabled QAT kernel driver is required. The VF
-devices created and initialised by this driver will be used by the QAT PMDs.
+devices created and initialized by this driver will be used by the QAT PMDs.
Instructions for installation are below, but first an explanation of the
relationships between the PF/VF devices and the PMDs visible to
diff --git a/doc/guides/cryptodevs/scheduler.rst b/doc/guides/cryptodevs/scheduler.rst
index a754a27..7004ca4 100644
--- a/doc/guides/cryptodevs/scheduler.rst
+++ b/doc/guides/cryptodevs/scheduler.rst
@@ -165,7 +165,7 @@ operation:
For pure small packet size (64 bytes) traffic however the multi-core mode is not
an optimal solution, as it doesn't give significant per-core performance improvement.
For mixed traffic (IMIX) the optimal number of worker cores is around 2-3.
- For large packets (1.5 Kbytes) scheduler shows linear scaling in performance
+ For large packets (1.5 kbytes) scheduler shows linear scaling in performance
up to eight cores.
Each worker uses its own slave cryptodev. Only software cryptodevs
are supported. Only the same type of cryptodevs should be used concurrently.
diff --git a/doc/guides/eventdevs/opdl.rst b/doc/guides/eventdevs/opdl.rst
index 0262a33..8334ba5 100644
--- a/doc/guides/eventdevs/opdl.rst
+++ b/doc/guides/eventdevs/opdl.rst
@@ -8,7 +8,7 @@ The OPDL (Ordered Packet Distribution Library) eventdev is a specific\
implementation of the eventdev API. It is particularly suited to packet\
processing workloads that have high throughput and low latency requirements.\
All packets follow the same path through the device. The order in which\
-packets follow is determinted by the order in which queues are set up.\
+packets follow is determined by the order in which queues are set up.\
Events are left on the ring until they are transmitted. As a result packets\
do not go out of order
@@ -61,7 +61,7 @@ Queue Dependencies
As stated the order in which packets travel through queues is static in
nature. They go through the queues in the order the queues are setup at
-initialisation ``rte_event_queue_setup()``. For example if an application
+initialization ``rte_event_queue_setup()``. For example if an application
sets up 3 queues, Q0, Q1, Q2 and has 3 associated ports P0, P1, P2 and
P3 then packets must be
diff --git a/doc/guides/eventdevs/sw.rst b/doc/guides/eventdevs/sw.rst
index afdcad7..04c8b03 100644
--- a/doc/guides/eventdevs/sw.rst
+++ b/doc/guides/eventdevs/sw.rst
@@ -70,7 +70,7 @@ Credit Quanta
The credit quanta is the number of credits that a port will fetch at a time from
the instance's credit pool. Higher numbers will cause less overhead in the
atomic credit fetch code, however it also reduces the overall number of credits
-in the system faster. A balanced number (eg 32) ensures that only small numbers
+in the system faster. A balanced number (e.g. 32) ensures that only small numbers
of credits are pre-allocated at a time, while also mitigating performance impact
of the atomics.
@@ -100,7 +100,7 @@ feature would be significant.
~~~~~~~~~~~~~~~~~~
The software eventdev does not support creating queues that handle all types of
-traffic. An eventdev with this capability allows enqueueing Atomic, Ordered and
+traffic. An eventdev with this capability allows enqueuing Atomic, Ordered and
Parallel traffic to the same queue, but scheduling each of them appropriately.
The reason to not allow Atomic, Ordered and Parallel event types in the
diff --git a/doc/guides/howto/lm_bond_virtio_sriov.rst b/doc/guides/howto/lm_bond_virtio_sriov.rst
index ee8ccda..07563b3 100644
--- a/doc/guides/howto/lm_bond_virtio_sriov.rst
+++ b/doc/guides/howto/lm_bond_virtio_sriov.rst
@@ -328,7 +328,7 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
testpmd> show bonding config 2
testpmd> port attach 0000:00:04.0
diff --git a/doc/guides/howto/lm_virtio_vhost_user.rst b/doc/guides/howto/lm_virtio_vhost_user.rst
index 6ebc10f..ecb7832 100644
--- a/doc/guides/howto/lm_virtio_vhost_user.rst
+++ b/doc/guides/howto/lm_virtio_vhost_user.rst
@@ -243,7 +243,7 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
Virtio traffic is seen at P0 and P1.
@@ -338,7 +338,7 @@ reset_vf_on_212_131.sh
#!/bin/sh
# This script is run on the host 10.237.212.131 to reset SRIOV
- # BDF for Ninatic NIC is 0000:06:00.0
+ # BDF for Niantic NIC is 0000:06:00.0
cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
echo 0 > /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
diff --git a/doc/guides/howto/rte_flow.rst b/doc/guides/howto/rte_flow.rst
index 3dcda6c..e197376 100644
--- a/doc/guides/howto/rte_flow.rst
+++ b/doc/guides/howto/rte_flow.rst
@@ -23,7 +23,7 @@ In this example we will create a simple rule that drops packets whose IPv4
destination equals 192.168.3.2. This code is equivalent to the following
testpmd command (wrapped for clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst is 192.168.3.2 / end actions drop / end
Code
@@ -118,7 +118,7 @@ a mask.
This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst spec 192.168.3.0 dst mask 255.255.255.0 /
end actions drop / end
@@ -219,7 +219,7 @@ In this example we will create a rule that routes all vlan id 123 to queue 3.
This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
+ testpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
end actions queue index 3 / end
Code
diff --git a/doc/guides/howto/telemetry.rst b/doc/guides/howto/telemetry.rst
index 00f8f7a..e10804d 100644
--- a/doc/guides/howto/telemetry.rst
+++ b/doc/guides/howto/telemetry.rst
@@ -18,7 +18,7 @@ which acts as the client.
In DPDK, applications are used to initialize the ``telemetry``. To view incoming
traffic on featured ports, the application should be run first (ie. after ports
are configured). Once the application is running, the service assurance agent
-(for example the collectd plugin) should be run to begin querying the API.
+(for example the CollectD plugin) should be run to begin querying the API.
A client connects their Service Assurance application to the DPDK application
via a UNIX socket. Once a connection is established, a client can send JSON
diff --git a/doc/guides/howto/virtio_user_as_exceptional_path.rst b/doc/guides/howto/virtio_user_as_exceptional_path.rst
index 4910c12..ec021af 100644
--- a/doc/guides/howto/virtio_user_as_exceptional_path.rst
+++ b/doc/guides/howto/virtio_user_as_exceptional_path.rst
@@ -1,7 +1,7 @@
.. SPDX-License-Identifier: BSD-3-Clause
Copyright(c) 2016 Intel Corporation.
-.. _virtio_user_as_excpetional_path:
+.. _virtio_user_as_exceptional_path:
Virtio_user as Exceptional Path
===============================
@@ -22,7 +22,7 @@ solution is very promising in:
* Features
vhost-net is born to be a networking solution, which has lots of networking
- related featuers, like multi queue, tso, multi-seg mbuf, etc.
+ related features, like multi queue, tso, multi-seg mbuf, etc.
* Performance
@@ -38,7 +38,7 @@ in :numref:`figure_virtio_user_as_exceptional_path`.
.. figure:: img/virtio_user_as_exceptional_path.*
- Overview of a DPDK app using virtio-user as excpetional path
+ Overview of a DPDK app using virtio-user as exceptional path
Sample Usage
@@ -75,7 +75,7 @@ compiling the kernel and those kernel modules should be inserted.
* ``queues``
- Number of multi-queues. Each qeueue will be served by a kthread. For example:
+ Number of multi-queues. Each queue will be served by a kthread. For example:
.. code-block:: console
diff --git a/doc/guides/nics/af_packet.rst b/doc/guides/nics/af_packet.rst
index 1260bb2..efd6f1c 100644
--- a/doc/guides/nics/af_packet.rst
+++ b/doc/guides/nics/af_packet.rst
@@ -13,13 +13,13 @@ PACKET_MMAP, which provides a mmap'ed ring buffer, shared between user space
and kernel, that's used to send and receive packets. This helps reducing system
calls and the copies needed between user space and Kernel.
-The PACKET_FANOUT_HASH behaviour of AF_PACKET is used for frame reception.
+The PACKET_FANOUT_HASH behavior of AF_PACKET is used for frame reception.
Options and inherent limitations
--------------------------------
The following options can be provided to set up an af_packet port in DPDK.
-Some of these, in turn, will be used to configure the PAKET_MMAP settings.
+Some of these, in turn, will be used to configure the PACKET_MMAP settings.
* ``iface`` - name of the Kernel interface to attach to (required);
* ``qpairs`` - number of Rx and Tx queues (optional, default 1);
diff --git a/doc/guides/nics/atlantic.rst b/doc/guides/nics/atlantic.rst
index 80591b1..f6f2c66 100644
--- a/doc/guides/nics/atlantic.rst
+++ b/doc/guides/nics/atlantic.rst
@@ -18,7 +18,7 @@ Supported features
- Port statistics
- RSS (Receive Side Scaling)
- Checksum offload
-- Jumbo Frame upto 16K
+- Jumbo Frame up to 16K
Configuration Information
^^^^^^^^^^^^^^^^^^^^^^^^^
diff --git a/doc/guides/nics/cxgbe.rst b/doc/guides/nics/cxgbe.rst
index f3e6115..7a893cc 100644
--- a/doc/guides/nics/cxgbe.rst
+++ b/doc/guides/nics/cxgbe.rst
@@ -126,7 +126,7 @@ enabling debugging options may affect system performance.
- ``CONFIG_RTE_LIBRTE_CXGBE_TPUT`` (default **y**)
- Toggle behaviour to prefer Throughput or Latency.
+ Toggle behavior to prefer Throughput or Latency.
Runtime Options
~~~~~~~~~~~~~~~
@@ -140,7 +140,7 @@ be passed as part of EAL arguments. For example,
- ``keep_ovlan`` (default **0**)
- Toggle behaviour to keep/strip outer VLAN in Q-in-Q packets. If
+ Toggle behavior to keep/strip outer VLAN in Q-in-Q packets. If
enabled, the outer VLAN tag is preserved in Q-in-Q packets. Otherwise,
the outer VLAN tag is stripped in Q-in-Q packets.
diff --git a/doc/guides/nics/dpaa.rst b/doc/guides/nics/dpaa.rst
index fb7bc7d..2243a4a 100644
--- a/doc/guides/nics/dpaa.rst
+++ b/doc/guides/nics/dpaa.rst
@@ -251,7 +251,7 @@ state during application initialization:
automatically be assigned from the these high perf PUSH queues. Any queue
configuration beyond that will be standard Rx queues. The application can
choose to change their number if HW portals are limited.
- The valid values are from '0' to '4'. The valuse shall be set to '0' if the
+ The valid values are from '0' to '4'. The values shall be set to '0' if the
application want to use eventdev with DPAA device.
diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst
index 392ab05..a532d08 100644
--- a/doc/guides/nics/dpaa2.rst
+++ b/doc/guides/nics/dpaa2.rst
@@ -379,7 +379,7 @@ active -- Ethernet, crypto, compression, etc.
DPBP based Mempool driver
~~~~~~~~~~~~~~~~~~~~~~~~~
-The DPBP driver is bound to a DPBP objects and provides sevices to
+The DPBP driver is bound to a DPBP objects and provides services to
create a hardware offloaded packet buffer mempool.
DPAA2 NIC Driver
diff --git a/doc/guides/nics/ena.rst b/doc/guides/nics/ena.rst
index 80da4b6..d44f3cd 100644
--- a/doc/guides/nics/ena.rst
+++ b/doc/guides/nics/ena.rst
@@ -189,7 +189,7 @@ Prerequisites
reduces the latency of the packets by pushing the header directly through
the PCI to the device, before the DMA is even triggered. For proper work
kernel PCI driver must support write combining (WC). In mainline version of
- ``igb_uio`` (in DPDK repo) it must be enabled by loding module with
+ ``igb_uio`` (in DPDK repo) it must be enabled by loading module with
``wc_activate=1`` flag (example below). However, mainline's vfio-pci
driver in kernel doesn't have WC support yet (planed to be added).
If vfio-pci used user should be either turn off ENAv2 (to avoid performance
diff --git a/doc/guides/nics/enetc.rst b/doc/guides/nics/enetc.rst
index 8038bf2..376768d 100644
--- a/doc/guides/nics/enetc.rst
+++ b/doc/guides/nics/enetc.rst
@@ -69,7 +69,7 @@ Supported ENETC SoCs
Prerequisites
~~~~~~~~~~~~~
-There are three main pre-requisities for executing ENETC PMD on a ENETC
+There are three main pre-requisites for executing ENETC PMD on a ENETC
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/nics/enic.rst b/doc/guides/nics/enic.rst
index 726a69e..cdb55e0 100644
--- a/doc/guides/nics/enic.rst
+++ b/doc/guides/nics/enic.rst
@@ -224,7 +224,7 @@ the use of SR-IOV.
passthrough devices do not require libvirt, port profiles, and VM-FEX.
-.. _enic-genic-flow-api:
+.. _enic-generic-flow-api:
Generic Flow API support
------------------------
diff --git a/doc/guides/nics/features.rst b/doc/guides/nics/features.rst
index c5bf322..d57ddc2 100644
--- a/doc/guides/nics/features.rst
+++ b/doc/guides/nics/features.rst
@@ -495,7 +495,7 @@ Supports adding traffic mirroring rules.
Inline crypto
-------------
-Supports inline crypto processing (eg. inline IPsec). See Security library and PMD documentation for more details.
+Supports inline crypto processing (e.g. inline IPsec). See Security library and PMD documentation for more details.
* **[uses] rte_eth_rxconf,rte_eth_rxmode**: ``offloads:DEV_RX_OFFLOAD_SECURITY``,
* **[uses] rte_eth_txconf,rte_eth_txmode**: ``offloads:DEV_TX_OFFLOAD_SECURITY``.
diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 9680a92..2e9ec79 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -580,7 +580,7 @@ bandwidth setting.
TC TX scheduling mode setting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-There're 2 TX scheduling modes for TCs, round robin and strict priority mode.
+There are 2 TX scheduling modes for TCs, round robin and strict priority mode.
If a TC is set to strict priority mode, it can consume unlimited bandwidth.
It means if APP has set the max bandwidth for that TC, it comes to no
effect.
diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
index 1c294b0..975143f 100644
--- a/doc/guides/nics/ixgbe.rst
+++ b/doc/guides/nics/ixgbe.rst
@@ -203,8 +203,8 @@ as a workaround.
X550 does not support legacy interrupt mode
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Desccription
-^^^^^^^^^^^^
+Description
+^^^^^^^^^^^
X550 cannot get interrupts if using ``uio_pci_generic`` module or using legacy
interrupt mode of ``igb_uio`` or ``vfio``. Because the errata of X550 states
that the Interrupt Status bit is not implemented. The errata is the item #22
diff --git a/doc/guides/nics/kni.rst b/doc/guides/nics/kni.rst
index a66c595..602a06b 100644
--- a/doc/guides/nics/kni.rst
+++ b/doc/guides/nics/kni.rst
@@ -65,7 +65,7 @@ backend device by default.
PMD arguments
-------------
-``no_request_thread``, by default PMD creates a phtread for each KNI interface
+``no_request_thread``, by default PMD creates a pthread for each KNI interface
to handle Linux network interface control commands, like ``ifconfig kni0 up``
With ``no_request_thread`` option, pthread is not created and control commands
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index 4ad361a..28e3666 100644
--- a/doc/guides/nics/mlx4.rst
+++ b/doc/guides/nics/mlx4.rst
@@ -83,7 +83,7 @@ These options can be modified in the ``.config`` file.
- ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
- Embed static flavour of the dependencies **libibverbs** and **libmlx4**
+ Embed static flavor of the dependencies **libibverbs** and **libmlx4**
in the PMD shared library or the executable static binary.
- ``CONFIG_RTE_LIBRTE_MLX4_DEBUG`` (default **n**)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 0200373..3f3226a 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -149,7 +149,7 @@ Limitations
- E-Switch VXLAN decapsulation Flow:
- - can be appiled to PF port only.
+ - can be applied to PF port only.
- must specify VF port action (packet redirection from PF to VF).
- must specify tunnel outer UDP local (destination) port, wildcards not allowed.
- must specify tunnel outer VNI, wildcards not allowed.
@@ -164,7 +164,7 @@ Limitations
- must specify the VXLAN item with tunnel outer parameters.
- must specify the tunnel outer VNI in the VXLAN item.
- must specify the tunnel outer remote (destination) UDP port in the VXLAN item.
- - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interace, wildcards not allowed.
+ - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interface, wildcards not allowed.
- must specify the tunnel outer remote (destination) IPv4 or IPv6 in the VXLAN item, group IPs allowed.
- must specify the tunnel outer destination MAC address in the VXLAN item, this address will be used to create neigh rule.
@@ -212,7 +212,7 @@ These options can be modified in the ``.config`` file.
- ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
- Embed static flavour of the dependencies **libibverbs** and **libmlx5**
+ Embed static flavor of the dependencies **libibverbs** and **libmlx5**
in the PMD shared library or the executable static binary.
- ``CONFIG_RTE_LIBRTE_MLX5_DEBUG`` (default **n**)
@@ -319,7 +319,7 @@ Run-time configuration
buffers per a packet, one large buffer is posted in order to receive multiple
packets on the buffer. A MPRQ buffer consists of multiple fixed-size strides
and each stride receives one packet. MPRQ can improve throughput for
- small-packet tarffic.
+ small-packet traffic.
When MPRQ is enabled, max_rx_pkt_len can be larger than the size of
user-provided mbuf even if DEV_RX_OFFLOAD_SCATTER isn't enabled. PMD will
@@ -330,7 +330,7 @@ Run-time configuration
- ``mprq_log_stride_num`` parameter [int]
Log 2 of the number of strides for Multi-Packet Rx queue. Configuring more
- strides can reduce PCIe tarffic further. If configured value is not in the
+ strides can reduce PCIe traffic further. If configured value is not in the
range of device capability, the default value will be set with a warning
message. The default value is 4 which is 16 strides per a buffer, valid only
if ``mprq_en`` is set.
diff --git a/doc/guides/nics/mvpp2.rst b/doc/guides/nics/mvpp2.rst
index 09e2f2a..bacc013 100644
--- a/doc/guides/nics/mvpp2.rst
+++ b/doc/guides/nics/mvpp2.rst
@@ -91,7 +91,7 @@ Limitations
chance to start in a sane state.
- MUSDK architecture does not support changing configuration in run time.
- All nessesary configurations should be done before first dev_start().
+ All necessary configurations should be done before first dev_start().
- RX queue start/stop is not supported.
diff --git a/doc/guides/nics/netvsc.rst b/doc/guides/nics/netvsc.rst
index 87fabf5..6dbb9a5 100644
--- a/doc/guides/nics/netvsc.rst
+++ b/doc/guides/nics/netvsc.rst
@@ -89,7 +89,7 @@ operations:
.. Note::
- The dpkd-devbind.py script can not be used since it only handles PCI devices.
+ The dpdk-devbind.py script can not be used since it only handles PCI devices.
Prerequisites
diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst
index 09a8529..309fa5d 100644
--- a/doc/guides/nics/nfp.rst
+++ b/doc/guides/nics/nfp.rst
@@ -149,8 +149,8 @@ PF multiprocess support
-----------------------
Due to how the driver needs to access the NFP through a CPP interface, which implies
-to use specific registers inside the chip, the number of secondary proceses with PF
-ports is limitted to only one.
+to use specific registers inside the chip, the number of secondary processes with PF
+ports is limited to only one.
This limitation will be solved in future versions but having basic multiprocess support
is important for allowing development and debugging through the PF using a secondary
diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst
index 028c92c..d8512fa 100644
--- a/doc/guides/nics/sfc_efx.rst
+++ b/doc/guides/nics/sfc_efx.rst
@@ -96,7 +96,7 @@ Non-supported Features
The features not yet supported include:
-- Receive queue interupts
+- Receive queue interrupts
- Priority-based flow control
@@ -209,12 +209,12 @@ Validating flow rules depends on the firmware variant.
The :ref:`flow_isolated_mode` is supported.
-Ethernet destinaton individual/group match
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Ethernet destination individual/group match
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ethernet item supports I/G matching, if only the corresponding bit is set
-in the mask of destination address. If destinaton address in the spec is
-multicast, it matches all multicast (and broadcast) packets, oherwise it
+in the mask of destination address. If destination address in the spec is
+multicast, it matches all multicast (and broadcast) packets, otherwise it
matches unicast packets that are not filtered by other flow rules.
Exceptions to flow rules
@@ -348,10 +348,10 @@ boolean parameters value.
- ``perf_profile`` [auto|throughput|low-latency] (default **throughput**)
- Choose hardware tunning to be optimized for either throughput or
+ Choose hardware tuning to be optimized for either throughput or
low-latency.
**auto** allows NIC firmware to make a choice based on
- installed licences and firmware variant configured using **sfboot**.
+ installed licenses and firmware variant configured using **sfboot**.
- ``stats_update_period_ms`` [long] (default **1000**)
diff --git a/doc/guides/nics/szedata2.rst b/doc/guides/nics/szedata2.rst
index a2092f9..94dba82 100644
--- a/doc/guides/nics/szedata2.rst
+++ b/doc/guides/nics/szedata2.rst
@@ -89,7 +89,7 @@ The NFB cards are multi-port multi-queue cards, where (generally) data from any
Ethernet port may be sent to any queue.
They were historically represented in DPDK as a single port.
-However, the new NFB-200G2QL card employs an addon cable which allows to connect
+However, the new NFB-200G2QL card employs an add-on cable which allows to connect
it to two physical PCI-E slots at the same time (see the diagram below).
This is done to allow 200 Gbps of traffic to be transferred through the PCI-E
bus (note that a single PCI-E 3.0 x16 slot provides only 125 Gbps theoretical
diff --git a/doc/guides/nics/tap.rst b/doc/guides/nics/tap.rst
index 063bd0b..4b6d77d 100644
--- a/doc/guides/nics/tap.rst
+++ b/doc/guides/nics/tap.rst
@@ -40,7 +40,7 @@ actual MAC address: ``00:64:74:61:70:[00-FF]``.
--vdev=net_tap0,mac="00:64:74:61:70:11"
The MAC address will have a user value passed as string. The MAC address is in
-format with delimeter ``:``. The string is byte converted to hex and you get
+format with delimiter ``:``. The string is byte converted to hex and you get
the actual MAC address: ``00:64:74:61:70:11``.
It is possible to specify a remote netdevice to capture packets from by adding
diff --git a/doc/guides/platform/dpaa.rst b/doc/guides/platform/dpaa.rst
index 3904871..6005f22 100644
--- a/doc/guides/platform/dpaa.rst
+++ b/doc/guides/platform/dpaa.rst
@@ -4,7 +4,7 @@
NXP QorIQ DPAA Board Support Package
====================================
-This doc has information about steps to setup QorIq dpaa
+This doc has information about steps to setup QorIQ dpaa
based layerscape platform and information about common offload
hw block drivers of **NXP QorIQ DPAA** SoC family.
@@ -38,7 +38,7 @@ Common Offload HW Block Drivers
Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA PMD on a DPAA
+There are four main pre-requisites for executing DPAA PMD on a DPAA
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/platform/dpaa2.rst b/doc/guides/platform/dpaa2.rst
index 5a64406..2586af0 100644
--- a/doc/guides/platform/dpaa2.rst
+++ b/doc/guides/platform/dpaa2.rst
@@ -4,7 +4,7 @@
NXP QorIQ DPAA2 Board Support Package
=====================================
-This doc has information about steps to setup NXP QoriQ DPAA2 platform
+This doc has information about steps to setup NXP QorIQ DPAA2 platform
and information about common offload hw block drivers of
**NXP QorIQ DPAA2** SoC family.
@@ -48,7 +48,7 @@ Common Offload HW Block Drivers
Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA2 PMD on a DPAA2
+There are four main pre-requisites for executing DPAA2 PMD on a DPAA2
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index 9de1444..658ffd4 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -78,7 +78,7 @@ From the application point of view, each instance of a bbdev device consists of
one or more queues identified by queue IDs. While different devices may have
different capabilities (e.g. support different operation types), all queues on
a device support identical configuration possibilities. A queue is configured
-for only one type of operation and is configured at initializations time.
+for only one type of operation and is configured at initialization time.
When an operation is enqueued to a specific queue ID, the result is dequeued
from the same queue ID.
@@ -678,7 +678,7 @@ bbdev framework, by giving a sample code performing a loop-back operation with a
baseband processor capable of transceiving data packets.
The following sample C-like pseudo-code shows the basic steps to encode several
-buffers using (**sw_trubo**) bbdev PMD.
+buffers using (**sw_turbo**) bbdev PMD.
.. code-block:: c
diff --git a/doc/guides/prog_guide/compressdev.rst b/doc/guides/prog_guide/compressdev.rst
index ad97037..a06c835 100644
--- a/doc/guides/prog_guide/compressdev.rst
+++ b/doc/guides/prog_guide/compressdev.rst
@@ -17,7 +17,7 @@ Device Creation
Physical compression devices are discovered during the bus probe of the EAL function
which is executed at DPDK initialization, based on their unique device identifier.
-For eg. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
+For e.g. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
Specific physical compression devices, like other physical devices in DPDK can be
white-listed or black-listed using the EAL command line options.
@@ -379,7 +379,7 @@ using priv_xform would look like:
setup op->m_src and op->m_dst;
}
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, comp_ops, NUM_OPS);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deque = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, NUM_OPS);
} while (num_dqud < num_enqd);
@@ -526,7 +526,7 @@ An example pseudocode to set up and process a stream having NUM_CHUNKS with each
op->src.length = CHUNK_LEN;
op->input_chksum = 0;
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, &op[i], 1);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deqd = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, 1);
} while (num_deqd < num_enqd);
diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst
index 74a930b..dae40fb 100644
--- a/doc/guides/prog_guide/cryptodev_lib.rst
+++ b/doc/guides/prog_guide/cryptodev_lib.rst
@@ -14,7 +14,7 @@ and AEAD symmetric and asymmetric Crypto operations.
Design Principles
-----------------
-The cryptodev library follows the same basic principles as those used in DPDKs
+The cryptodev library follows the same basic principles as those used in DPDK's
Ethernet Device framework. The Crypto framework provides a generic Crypto device
framework which supports both physical (hardware) and virtual (software) Crypto
devices as well as a generic Crypto API which allows Crypto devices to be
@@ -48,7 +48,7 @@ From the command line using the --vdev EAL option
* If DPDK application requires multiple software crypto PMD devices then required
number of ``--vdev`` with appropriate libraries are to be added.
- * An Application with crypto PMD instaces sharing the same library requires unique ID.
+ * An Application with crypto PMD instances sharing the same library requires unique ID.
Example: ``--vdev 'crypto_aesni_mb0' --vdev 'crypto_aesni_mb1'``
@@ -396,7 +396,7 @@ Operation Management and Allocation
The cryptodev library provides an API set for managing Crypto operations which
utilize the Mempool Library to allocate operation buffers. Therefore, it ensures
-that the crytpo operation is interleaved optimally across the channels and
+that the crypto operation is interleaved optimally across the channels and
ranks for optimal processing.
A ``rte_crypto_op`` contains a field indicating the pool that it originated from.
When calling ``rte_crypto_op_free(op)``, the operation returns to its original pool.
@@ -549,7 +549,7 @@ chain.
union {
struct rte_cryptodev_sym_session *session;
- /**< Handle for the initialised session context */
+ /**< Handle for the initialized session context */
struct rte_crypto_sym_xform *xform;
/**< Session-less API Crypto operation parameters */
};
@@ -602,7 +602,7 @@ Sample code
There are various sample applications that show how to use the cryptodev library,
such as the L2fwd with Crypto sample application (L2fwd-crypto) and
-the IPSec Security Gateway application (ipsec-secgw).
+the IPsec Security Gateway application (ipsec-secgw).
While these applications demonstrate how an application can be created to perform
generic crypto operation, the required complexity hides the basic steps of
@@ -807,7 +807,7 @@ using one of the crypto PMDs available in DPDK.
/*
* Dequeue the crypto operations until all the operations
- * are proccessed in the crypto device.
+ * are processed in the crypto device.
*/
uint16_t num_dequeued_ops, total_num_dequeued_ops = 0;
do {
@@ -886,7 +886,7 @@ the order in which the transforms are passed indicates the order of the chaining
Not all asymmetric crypto xforms are supported for chaining. Currently supported
asymmetric crypto chaining is Diffie-Hellman private key generation followed by
public generation. Also, currently API does not support chaining of symmetric and
-asymmetric crypto xfroms.
+asymmetric crypto xforms.
Each xform defines specific asymmetric crypto algo. Currently supported are:
* RSA
diff --git a/doc/guides/prog_guide/dev_kit_build_system.rst b/doc/guides/prog_guide/dev_kit_build_system.rst
index 96dbf30..74dba4d 100644
--- a/doc/guides/prog_guide/dev_kit_build_system.rst
+++ b/doc/guides/prog_guide/dev_kit_build_system.rst
@@ -204,7 +204,7 @@ Creates the following symbol:
Which ``dpdk-pmdinfogen`` scans for. Using this information other relevant
bits of data can be exported from the object file and used to produce a
hardware support description, that ``dpdk-pmdinfogen`` then encodes into a
-json formatted string in the following format:
+JSON formatted string in the following format:
.. code-block:: c
diff --git a/doc/guides/prog_guide/efd_lib.rst b/doc/guides/prog_guide/efd_lib.rst
index cb1a1df..2b355ff 100644
--- a/doc/guides/prog_guide/efd_lib.rst
+++ b/doc/guides/prog_guide/efd_lib.rst
@@ -423,6 +423,6 @@ References
1- EFD is based on collaborative research work between Intel and
Carnegie Mellon University (CMU), interested readers can refer to the paper
-“Scaling Up Clustered Network Appliances with ScaleBricks;” Dong Zhou et al.
+"Scaling Up Clustered Network Appliances with ScaleBricks" Dong Zhou et al.
at SIGCOMM 2015 (`http://conferences.sigcomm.org/sigcomm/2015/pdf/papers/p241.pdf`)
for more information.
diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index c134636..a8ae214 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -705,7 +705,7 @@ The most important fields in the structure and how they are used are described b
Malloc heap is a doubly-linked list, where each element keeps track of its
previous and next elements. Due to the fact that hugepage memory can come and
-go, neighbouring malloc elements may not necessarily be adjacent in memory.
+go, neighboring malloc elements may not necessarily be adjacent in memory.
Also, since a malloc element may span multiple pages, its contents may not
necessarily be IOVA-contiguous either - each malloc element is only guaranteed
to be virtually contiguous.
diff --git a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
index e955299..c7dda92 100644
--- a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
+++ b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
@@ -162,7 +162,7 @@ The servicing_weight member of struct rte_event_eth_rx_adapter_queue_conf
is applicable when the adapter uses a service core function. The application
has to enable Rx queue interrupts when configuring the ethernet device
using the ``rte_eth_dev_configure()`` function and then use a servicing_weight
-of zero when addding the Rx queue to the adapter.
+of zero when adding the Rx queue to the adapter.
The adapter creates a thread blocked on the interrupt, on an interrupt this
thread enqueues the port id and the queue id to a ring buffer. The adapter
@@ -180,9 +180,9 @@ Rx Callback for SW Rx Adapter
For SW based packet transfers, i.e., when the
``RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT`` is not set in the adapter's
capabilities flags for a particular ethernet device, the service function
-temporarily enqueues mbufs to an event buffer before batch enqueueing these
+temporarily enqueues mbufs to an event buffer before batch enqueuing these
to the event device. If the buffer fills up, the service function stops
-dequeueing packets from the ethernet device. The application may want to
+dequeuing packets from the ethernet device. The application may want to
monitor the buffer fill level and instruct the service function to selectively
enqueue packets to the event device. The application may also use some other
criteria to decide which packets should enter the event device even when
diff --git a/doc/guides/prog_guide/eventdev.rst b/doc/guides/prog_guide/eventdev.rst
index dcdfeb7..7ea14ba 100644
--- a/doc/guides/prog_guide/eventdev.rst
+++ b/doc/guides/prog_guide/eventdev.rst
@@ -42,7 +42,7 @@ The rte_event structure contains the following metadata fields, which the
application fills in to have the event scheduled as required:
* ``flow_id`` - The targeted flow identifier for the enq/deq operation.
-* ``event_type`` - The source of this event, eg RTE_EVENT_TYPE_ETHDEV or CPU.
+* ``event_type`` - The source of this event, e.g. RTE_EVENT_TYPE_ETHDEV or CPU.
* ``sub_event_type`` - Distinguishes events inside the application, that have
the same event_type (see above)
* ``op`` - This field takes one of the RTE_EVENT_OP_* values, and tells the
@@ -265,7 +265,7 @@ Linking Queues and Ports
The final step is to "wire up" the ports to the queues. After this, the
eventdev is capable of scheduling events, and when cores request work to do,
the correct events are provided to that core. Note that the RX core takes input
-from eg: a NIC so it is not linked to any eventdev queues.
+from e.g.: a NIC so it is not linked to any eventdev queues.
Linking all workers to atomic queues, and the TX core to the single-link queue
can be achieved like this:
@@ -276,7 +276,7 @@ can be achieved like this:
uint8_t tx_port_id = 5;
uint8_t atomic_qs[] = {0, 1};
uint8_t single_link_q = 2;
- uin8t_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
+ uint8t_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
for(int worker_port_id = 1; worker_port_id <= 4; worker_port_id++) {
int links_made = rte_event_port_link(dev_id, worker_port_id, atomic_qs, NULL, 2);
diff --git a/doc/guides/prog_guide/flow_classify_lib.rst b/doc/guides/prog_guide/flow_classify_lib.rst
index f0ed5a1..fbb71f5 100644
--- a/doc/guides/prog_guide/flow_classify_lib.rst
+++ b/doc/guides/prog_guide/flow_classify_lib.rst
@@ -94,7 +94,7 @@ The library has the following API's
* Associated actions (list terminated by the END pattern item).
* @param[out] error
* Perform verbose error reporting if not NULL. Structure
- * initialised in case of error only.
+ * initialized in case of error only.
* @return
* 0 on success, error code otherwise
*/
@@ -120,7 +120,7 @@ The library has the following API's
* returns 1 if rule present already, 0 otherwise.
* @param[out] error
* Perform verbose error reporting if not NULL. Structure
- * initialised in case of error only.
+ * initialized in case of error only.
* @return
* A valid handle in case of success, NULL otherwise.
*/
@@ -175,7 +175,7 @@ Classifier creation
The application creates the ``Classifier`` using the
``rte_flow_classifier_create`` API.
-The ``rte_flow_classify_params`` structure must be initialised by the
+The ``rte_flow_classify_params`` structure must be initialized by the
application before calling the API.
.. code-block:: c
@@ -229,7 +229,7 @@ Adding a table to the Classifier
The application adds a table to the ``Classifier`` using the
``rte_flow_classify_table_create`` API.
-The ``rte_flow_classify_table_params`` structure must be initialised by the
+The ``rte_flow_classify_table_params`` structure must be initialized by the
application before calling the API.
.. code-block:: c
@@ -246,7 +246,7 @@ application before calling the API.
};
To create an ACL table the ``rte_table_acl_params`` structure must be
-initialised and assigned to ``arg_create`` in the
+initialized and assigned to ``arg_create`` in the
``rte_flow_classify_table_params`` structure.
.. code-block:: c
@@ -265,7 +265,7 @@ initialised and assigned to ``arg_create`` in the
struct rte_acl_field_def field_format[RTE_ACL_MAX_FIELDS];
};
-The fields for the ACL rule must also be initialised by the application.
+The fields for the ACL rule must also be initialized by the application.
An ACL table can be added to the ``Classifier`` for each ACL rule, for example
another table could be added for the IPv6 5-tuple rule.
diff --git a/doc/guides/prog_guide/ipsec_lib.rst b/doc/guides/prog_guide/ipsec_lib.rst
index 992fdf4..1beb8e7 100644
--- a/doc/guides/prog_guide/ipsec_lib.rst
+++ b/doc/guides/prog_guide/ipsec_lib.rst
@@ -65,7 +65,7 @@ In that mode the library functions perform
- check SQN
- prepare *rte_crypto_op* structure for each input packet
- - verify that integity check and decryption performed by crypto device
+ - verify that integrity check and decryption performed by crypto device
completed successfully
- check padding data
- remove outer IP header (tunnel mode) / update IP header (transport mode)
@@ -88,7 +88,7 @@ In that mode the library functions perform
* for inbound packets:
- - verify that integity check and decryption performed by *rte_security*
+ - verify that integrity check and decryption performed by *rte_security*
device completed successfully
- check SQN
- check padding data
@@ -101,10 +101,10 @@ In that mode the library functions perform
- generate SQN and IV
- add outer IP header (tunnel mode) / update IP header (transport mode)
- add ESP header and trailer, padding and IV data
- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
inline-crypto processing has to be performed by HW on this packet
- invoke *rte_security* device specific *set_pkt_metadata()* to associate
- secuirty device specific data with the packet
+ security device specific data with the packet
RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -113,15 +113,15 @@ In that mode the library functions perform
* for inbound packets:
- - verify that integity check and decryption performed by *rte_security*
+ - verify that integrity check and decryption performed by *rte_security*
device completed successfully
* for outbound packets:
- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
inline-crypto processing has to be performed by HW on this packet
- invoke *rte_security* device specific *set_pkt_metadata()* to associate
- secuirty device specific data with the packet
+ security device specific data with the packet
RTE_SECURITY_ACTION_TYPE_LOOKASIDE_PROTOCOL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -131,7 +131,7 @@ In that mode the library functions perform
* for inbound packets:
- prepare *rte_crypto_op* structure for each input packet
- - verify that integity check and decryption performed by crypto device
+ - verify that integrity check and decryption performed by crypto device
completed successfully
* for outbound packets:
diff --git a/doc/guides/prog_guide/kernel_nic_interface.rst b/doc/guides/prog_guide/kernel_nic_interface.rst
index 7fcbd93..daf87f4 100644
--- a/doc/guides/prog_guide/kernel_nic_interface.rst
+++ b/doc/guides/prog_guide/kernel_nic_interface.rst
@@ -227,7 +227,7 @@ application functions:
``config_promiscusity``:
- Called when the user changes the promiscusity state of the KNI
+ Called when the user changes the promiscuity state of the KNI
interface. For example, when the user runs ``ip link set promisc
[on|off] dev <ifaceX>``. If the user sets this callback function to
NULL, but sets the ``port_id`` field to a value other than -1, a default
diff --git a/doc/guides/prog_guide/metrics_lib.rst b/doc/guides/prog_guide/metrics_lib.rst
index e68e4e7..f2071f2 100644
--- a/doc/guides/prog_guide/metrics_lib.rst
+++ b/doc/guides/prog_guide/metrics_lib.rst
@@ -25,7 +25,7 @@ individual device. Since the metrics library is self-contained, the only
restriction on port numbers is that they are less than ``RTE_MAX_ETHPORTS``
- there is no requirement for the ports to actually exist.
-Initialising the library
+Initializing the library
------------------------
Before the library can be used, it has to be initialized by calling
@@ -169,13 +169,13 @@ following names:
- ``peak_bits_in``: Peak inbound bit-rate
- ``peak_bits_out``: Peak outbound bit-rate
-Once initialised and clocked at the appropriate frequency, these
+Once initialized and clocked at the appropriate frequency, these
statistics can be obtained by querying the metrics library.
Initialization
~~~~~~~~~~~~~~
-Before the library can be used, it has to be initialised by calling
+Before the library can be used, it has to be initialized by calling
``rte_stats_bitrate_create()``, which will return a bit-rate
calculation object. Since the bit-rate library uses the metrics library
to report the calculated statistics, the bit-rate library then needs to
@@ -233,13 +233,13 @@ via the metrics library using the following names:
- ``mac_latency_ns``: Maximum processing latency (nano-seconds)
- ``jitter_ns``: Variance in processing latency (nano-seconds)
-Once initialised and clocked at the appropriate frequency, these
+Once initialized and clocked at the appropriate frequency, these
statistics can be obtained by querying the metrics library.
Initialization
~~~~~~~~~~~~~~
-Before the library can be used, it has to be initialised by calling
+Before the library can be used, it has to be initialized by calling
``rte_latencystats_init()``.
.. code-block:: c
@@ -266,7 +266,7 @@ Library shutdown
~~~~~~~~~~~~~~~~
When finished, ``rte_latencystats_uninit()`` needs to be called to
-de-initialise the latency library.
+de-initialize the latency library.
.. code-block:: c
diff --git a/doc/guides/prog_guide/multi_proc_support.rst b/doc/guides/prog_guide/multi_proc_support.rst
index 1384fe3..6196d3f 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -273,7 +273,7 @@ will be populated by IPC are as follows:
those peer processes that were active at the time of request, how many have
replied)
* ``msgs`` - pointer to where all of the responses are stored. The order in
- which responses appear is undefined. Whendoing sycnrhonous requests, this
+ which responses appear is undefined. When doing synchronous requests, this
memory must be freed by the requestor after request completes!
For asynchronous requests, a function pointer to the callback function must be
diff --git a/doc/guides/prog_guide/profile_app.rst b/doc/guides/prog_guide/profile_app.rst
index 5af795c..a36ebef 100644
--- a/doc/guides/prog_guide/profile_app.rst
+++ b/doc/guides/prog_guide/profile_app.rst
@@ -64,7 +64,7 @@ The default ``cntvct_el0`` based ``rte_rdtsc()`` provides a portable means to
get a wall clock counter in user space. Typically it runs at <= 100MHz.
The alternative method to enable ``rte_rdtsc()`` for a high resolution wall
-clock counter is through the armv8 PMU subsystem. The PMU cycle counter runs
+clock counter is through the ARMv8 PMU subsystem. The PMU cycle counter runs
at CPU frequency. However, access to the PMU cycle counter from user space is
not enabled by default in the arm64 linux kernel. It is possible to enable
cycle counter for user space access by configuring the PMU from the privileged
@@ -75,7 +75,7 @@ scheme. Application can choose the PMU based implementation with
``CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU``.
The example below shows the steps to configure the PMU based cycle counter on
-an armv8 machine.
+an ARMv8 machine.
.. code-block:: console
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 0203f4f..1aec578 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2129,7 +2129,7 @@ as defined in the ``rte_flow_action_raw_decap``
This action modifies the payload of matched flows. The data supplied must
be a valid header, either holding layer 2 data in case of removing layer 2
-before eincapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
+before encapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
tunnel definition starting from layer 2 and moving to the tunnel item itself.
When applied to the original packet the resulting packet must be a
valid packet.
@@ -2279,7 +2279,7 @@ Action: ``DEC_TTL``
Decrease TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_dec_ttl:
@@ -2297,7 +2297,7 @@ Action: ``SET_TTL``
Assigns a new TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_set_ttl:
diff --git a/doc/guides/prog_guide/rte_security.rst b/doc/guides/prog_guide/rte_security.rst
index cb70caa..7d0734a 100644
--- a/doc/guides/prog_guide/rte_security.rst
+++ b/doc/guides/prog_guide/rte_security.rst
@@ -40,7 +40,7 @@ Inline Crypto
~~~~~~~~~~~~~
RTE_SECURITY_ACTION_TYPE_INLINE_CRYPTO:
-The crypto processing for security protocol (e.g. IPSec) is processed
+The crypto processing for security protocol (e.g. IPsec) is processed
inline during receive and transmission on NIC port. The flow based
security action should be configured on the port.
@@ -48,7 +48,7 @@ Ingress Data path - The packet is decrypted in RX path and relevant
crypto status is set in Rx descriptors. After the successful inline
crypto processing the packet is presented to host as a regular Rx packet
however all security protocol related headers are still attached to the
-packet. e.g. In case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. In case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will remain in the packet but the received packet
contains the decrypted data where the encrypted data was when the packet
arrived. The driver Rx path check the descriptors and and based on the
@@ -111,7 +111,7 @@ Inline protocol offload
~~~~~~~~~~~~~~~~~~~~~~~
RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL:
-The crypto and protocol processing for security protocol (e.g. IPSec)
+The crypto and protocol processing for security protocol (e.g. IPsec)
is processed inline during receive and transmission. The flow based
security action should be configured on the port.
@@ -119,7 +119,7 @@ Ingress Data path - The packet is decrypted in the RX path and relevant
crypto status is set in the Rx descriptors. After the successful inline
crypto processing the packet is presented to the host as a regular Rx packet
but all security protocol related headers are optionally removed from the
-packet. e.g. in the case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. in the case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will be removed from the packet and the received packet
will contains the decrypted packet only. The driver Rx path checks the
descriptors and based on the crypto status sets additional flags in
@@ -132,7 +132,7 @@ to identify the security processing done on the packet.
The underlying device in this case is stateful. It is expected that
the device shall support crypto processing for all kind of packets matching
to a given flow, this includes fragmented packets (post reassembly).
- E.g. in case of IPSec the device may internally manage anti-replay etc.
+ E.g. in case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in the descriptor.
@@ -150,7 +150,7 @@ to cross the MTU size.
.. note::
The underlying device will manage state information required for egress
- processing. E.g. in case of IPSec, the seq number will be added to the
+ processing. E.g. in case of IPsec, the seq number will be added to the
packet, however the device shall provide indication when the sequence number
is about to overflow. The underlying device may support post encryption TSO.
@@ -199,13 +199,13 @@ crypto device.
Decryption: The packet is sent to the crypto device for security
protocol processing. The device will decrypt the packet and it will also
optionally remove additional security headers from the packet.
-E.g. in case of IPSec, IPSec tunnel headers (if any), ESP/AH headers
+E.g. in case of IPsec, IPsec tunnel headers (if any), ESP/AH headers
will be removed from the packet and the decrypted packet may contain
plain data only.
.. note::
- In case of IPSec the device may internally manage anti-replay etc.
+ In case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in descriptor.
@@ -217,7 +217,7 @@ for any protocol header addition.
.. note::
- In the case of IPSec, the seq number will be added to the packet,
+ In the case of IPsec, the seq number will be added to the packet,
It shall provide an indication when the sequence number is about to
overflow.
@@ -549,7 +549,7 @@ IPsec related configuration parameters are defined in ``rte_security_ipsec_xform
struct rte_security_ipsec_sa_options options;
/**< various SA options */
enum rte_security_ipsec_sa_direction direction;
- /**< IPSec SA Direction - Egress/Ingress */
+ /**< IPsec SA Direction - Egress/Ingress */
enum rte_security_ipsec_sa_protocol proto;
/**< IPsec SA Protocol - AH/ESP */
enum rte_security_ipsec_sa_mode mode;
diff --git a/doc/guides/prog_guide/traffic_management.rst b/doc/guides/prog_guide/traffic_management.rst
index 98ac431..05b34d9 100644
--- a/doc/guides/prog_guide/traffic_management.rst
+++ b/doc/guides/prog_guide/traffic_management.rst
@@ -39,7 +39,7 @@ whether a specific implementation does meet the needs to the user application.
At the TM level, users can get high level idea with the help of various
parameters such as maximum number of nodes, maximum number of hierarchical
levels, maximum number of shapers, maximum number of private shapers, type of
-scheduling algorithm (Strict Priority, Weighted Fair Queueing , etc.), etc.,
+scheduling algorithm (Strict Priority, Weighted Fair Queuing , etc.), etc.,
supported by the implementation.
Likewise, users can query the capability of the TM at the hierarchical level to
diff --git a/doc/guides/prog_guide/vhost_lib.rst b/doc/guides/prog_guide/vhost_lib.rst
index a86c07a..fc3ee43 100644
--- a/doc/guides/prog_guide/vhost_lib.rst
+++ b/doc/guides/prog_guide/vhost_lib.rst
@@ -63,7 +63,7 @@ The following is an overview of some key Vhost API functions:
512).
* zero copy is really good for VM2VM case. For iperf between two VMs, the
- boost could be above 70% (when TSO is enableld).
+ boost could be above 70% (when TSO is enabled).
* For zero copy in VM2NIC case, guest Tx used vring may be starved if the
PMD driver consume the mbuf but not release them timely.
diff --git a/doc/guides/rawdevs/ifpga_rawdev.rst b/doc/guides/rawdevs/ifpga_rawdev.rst
index d400db6..a3d92a6 100644
--- a/doc/guides/rawdevs/ifpga_rawdev.rst
+++ b/doc/guides/rawdevs/ifpga_rawdev.rst
@@ -91,7 +91,7 @@ Run-time parameters
-------------------
This driver is invoked automatically in systems added with Intel FPGA,
-but PR and IFPGA Bus scan is trigged by command line using
+but PR and IFPGA Bus scan is triggered by command line using
``--vdev 'ifpga_rawdev_cfg`` EAL option.
The following device parameters are supported:
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 358dfa3..276327c 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -676,7 +676,7 @@ igb uio legacy mode can not be used in X710/XL710/XXV710
**Description**:
X710/XL710/XXV710 NICs lack support for indicating INTx is asserted via the interrupt
- bit in the PCI status register. Linux delected them from INTx support table. The related
+ bit in the PCI status register. Linux deleted them from INTx support table. The related
`commit <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/pci/quirks.c?id=8bcf4525c5d43306c5fd07e132bc8650e3491aec>`_.
**Implication**:
@@ -722,9 +722,9 @@ Linux kernel 4.10.0 iommu attribute read error
**Description**:
When VT-d is enabled (``iommu=pt intel_iommu=on``), reading IOMMU attributes from
/sys/devices/virtual/iommu/dmarXXX/intel-iommu/cap on Linux kernel 4.10.0 error.
- This bug is fixed in `Linux commmit a7fdb6e648fb
+ This bug is fixed in `Linux commit a7fdb6e648fb
<https://patchwork.kernel.org/patch/9595727/>`_,
- This bug is introduced in `Linux commmit 39ab9555c241
+ This bug is introduced in `Linux commit 39ab9555c241
<https://patchwork.kernel.org/patch/9554403/>`_,
**Implication**:
@@ -842,7 +842,7 @@ AVX-512 support disabled
drop.
On DPDK v19.02 ``AVX-512`` disable scope is reduced to ``GCC`` and ``binutils version 2.30`` based
- on information accured from the GCC community defect.
+ on information accrued from the GCC community defect.
**Reason**:
Generated ``AVX-512`` code cause crash:
diff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/release_17_11.rst
index 2a93af3..6448b6c 100644
--- a/doc/guides/rel_notes/release_17_11.rst
+++ b/doc/guides/rel_notes/release_17_11.rst
@@ -168,7 +168,7 @@ New Features
* The DES CBC algorithm.
* The DES DOCSIS BPI algorithm.
- This change requires version 0.47 of the IPSec Multi-buffer library. For
+ This change requires version 0.47 of the IPsec Multi-buffer library. For
more details see the :doc:`../cryptodevs/aesni_mb` documentation.
* **Updated the OpenSSL PMD.**
@@ -198,7 +198,7 @@ New Features
* **Added the Security Offload Library.**
Added an experimental library - ``rte_security``. This provide security APIs
- for protocols like IPSec using inline ipsec offload to ethernet devices or
+ for protocols like IPsec using inline ipsec offload to ethernet devices or
full protocol offload with lookaside crypto devices.
See the :doc:`../prog_guide/rte_security` section of the DPDK Programmers
@@ -207,11 +207,11 @@ New Features
* **Updated the DPAA2_SEC crypto driver to support rte_security.**
Updated the ``dpaa2_sec`` crypto PMD to support ``rte_security`` lookaside
- protocol offload for IPSec.
+ protocol offload for IPsec.
* **Updated the IXGBE ethernet driver to support rte_security.**
- Updated ixgbe ethernet PMD to support ``rte_security`` inline IPSec offload.
+ Updated ixgbe ethernet PMD to support ``rte_security`` inline IPsec offload.
* **Updated i40e driver to support GTP-C/GTP-U.**
@@ -509,7 +509,7 @@ ABI Changes
* **New parameter added to rte_eth_dev.**
A new parameter ``security_ctx`` has been added to ``rte_eth_dev`` to
- support security operations like IPSec inline.
+ support security operations like IPsec inline.
* **New parameter added to rte_cryptodev.**
diff --git a/doc/guides/sample_app_ug/bbdev_app.rst b/doc/guides/sample_app_ug/bbdev_app.rst
index 40a3264..405e706 100644
--- a/doc/guides/sample_app_ug/bbdev_app.rst
+++ b/doc/guides/sample_app_ug/bbdev_app.rst
@@ -68,7 +68,7 @@ The application accepts a number of command line options:
where:
-* ``e ENCODING_CORES``: hexmask for encoding lcored (default = 0x2)
+* ``e ENCODING_CORES``: hexmask for encoding lcores (default = 0x2)
* ``d DECODING_CORES``: hexmask for decoding lcores (default = 0x4)
* ``p ETH_PORT_ID``: ethernet port ID (default = 0)
* ``b BBDEV_ID``: BBDev ID (default = 0)
@@ -87,7 +87,7 @@ issue the command:
$ ./build/bbdev --vdev='baseband_turbo_sw' -w <NIC0PCIADDR> -c 0x38 --socket-mem=2,2 \
--file-prefix=bbdev -- -e 0x10 -d 0x20
-where, NIC0PCIADDR is the PCI addresse of the Rx port
+where, NIC0PCIADDR is the PCI address of the Rx port
This command creates one virtual bbdev devices ``baseband_turbo_sw`` where the
device gets linked to a corresponding ethernet port as whitelisted by
diff --git a/doc/guides/sample_app_ug/eventdev_pipeline.rst b/doc/guides/sample_app_ug/eventdev_pipeline.rst
index 0ec0290..dc7972a 100644
--- a/doc/guides/sample_app_ug/eventdev_pipeline.rst
+++ b/doc/guides/sample_app_ug/eventdev_pipeline.rst
@@ -49,7 +49,7 @@ these settings is shown below:
./build/eventdev_pipeline --vdev event_sw0 -- -r1 -t1 -e4 -w FF00 -s4 -n0 -c32 -W1000 -D
The application has some sanity checking built-in, so if there is a function
-(eg; the RX core) which doesn't have a cpu core mask assigned, the application
+(e.g.; the RX core) which doesn't have a cpu core mask assigned, the application
will print an error message:
.. code-block:: console
diff --git a/doc/guides/sample_app_ug/flow_classify.rst b/doc/guides/sample_app_ug/flow_classify.rst
index a6383b3..1c765a5 100644
--- a/doc/guides/sample_app_ug/flow_classify.rst
+++ b/doc/guides/sample_app_ug/flow_classify.rst
@@ -64,7 +64,7 @@ ACL field definitions for the IPv4 5 tuple rule
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The following field definitions are used when creating the ACL table during
-initialisation of the ``Flow Classify`` application..
+initialization of the ``Flow Classify`` application..
.. code-block:: c
@@ -222,13 +222,13 @@ table`` to the flow classifier.
rte_exit(EXIT_FAILURE, "Cannot create classifier\n");
}
- /* initialise ACL table params */
+ /* initialize ACL table params */
table_acl_params.name = "table_acl_ipv4_5tuple";
table_acl_params.n_rule_fields = RTE_DIM(ipv4_defs);
table_acl_params.n_rules = FLOW_CLASSIFY_MAX_RULE_NUM;
memcpy(table_acl_params.field_format, ipv4_defs, sizeof(ipv4_defs));
- /* initialise table create params */
+ /* initialize table create params */
cls_table_params.ops = &rte_table_acl_ops,
cls_table_params.arg_create = &table_acl_params,
cls_table_params.type = RTE_FLOW_CLASSIFY_TABLE_ACL_IP4_5TUPLE;
@@ -240,7 +240,7 @@ table`` to the flow classifier.
rte_exit(EXIT_FAILURE, "Failed to create classifier table\n");
}
-It then reads the ipv4_rules_file.txt file and initialises the parameters for
+It then reads the ipv4_rules_file.txt file and initializes the parameters for
the ``rte_flow_classify_table_entry_add`` API.
This API adds a rule to the ACL table.
diff --git a/doc/guides/sample_app_ug/intro.rst b/doc/guides/sample_app_ug/intro.rst
index 159bcf7..9070419 100644
--- a/doc/guides/sample_app_ug/intro.rst
+++ b/doc/guides/sample_app_ug/intro.rst
@@ -106,7 +106,7 @@ examples are highlighted below.
(packet arrival) and TX (packet transmission) by adding callbacks to the RX
and TX packet processing functions.
-* :doc:`IPSec Security Gateway<ipsec_secgw>`: The IPSec Security
+* :doc:`IPsec Security Gateway<ipsec_secgw>`: The IPsec Security
Gateway application is minimal example of something closer to a real world
example. This is also a good example of an application using the DPDK
Cryptodev framework.
diff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst
index 447a544..d7a05b7 100644
--- a/doc/guides/sample_app_ug/ip_pipeline.rst
+++ b/doc/guides/sample_app_ug/ip_pipeline.rst
@@ -113,7 +113,7 @@ Application stages
Initialization
~~~~~~~~~~~~~~
-During this stage, EAL layer is initialised and application specific arguments are parsed. Furthermore, the data strcutures
+During this stage, EAL layer is initialized and application specific arguments are parsed. Furthermore, the data structures
(i.e. linked lists) for application objects are initialized. In case of any initialization error, an error message
is displayed and the application is terminated.
@@ -185,7 +185,7 @@ Examples
+-----------------------+----------------------+----------------+------------------------------------+
| IP routing | LPM (IPv4) | Forward | 1. Mempool Create |
| | | | 2. Link create |
- | | * Key = IP dest addr | | 3. Pipeline creat |
+ | | * Key = IP dest addr | | 3. Pipeline create |
| | * Offset = 286 | | 4. Pipeline port in/out |
| | * Table size = 4K | | 5. Pipeline table |
| | | | 6. Pipeline port in table |
diff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_app_ug/ipsec_secgw.rst
index 3d784e7..ac118c1 100644
--- a/doc/guides/sample_app_ug/ipsec_secgw.rst
+++ b/doc/guides/sample_app_ug/ipsec_secgw.rst
@@ -25,8 +25,8 @@ The application classifies the ports as *Protected* and *Unprotected*.
Thus, traffic received on an Unprotected or Protected port is consider
Inbound or Outbound respectively.
-The application also supports complete IPSec protocol offload to hardware
-(Look aside crypto accelarator or using ethernet device). It also support
+The application also supports complete IPsec protocol offload to hardware
+(Look aside crypto accelerator or using ethernet device). It also support
inline ipsec processing by the supported ethernet device during transmission.
These modes can be selected during the SA creation configuration.
@@ -124,7 +124,7 @@ Where:
* ``-e``: enables Security Association extended sequence number processing
(available only with librte_ipsec code path).
-* ``-a``: enables Security Association sequence number atomic behaviour
+* ``-a``: enables Security Association sequence number atomic behavior
(available only with librte_ipsec code path).
* ``--config (port,queue,lcore)[,(port,queue,lcore)]``: determines which queues
@@ -752,7 +752,7 @@ DUT OS(NIC1)--(IPsec)-->(NIC1)ipsec-secgw(TAP)--(plain)-->(TAP)SUT OS
SUT OS(TAP)--(plain)-->(TAP)psec-secgw(NIC1)--(IPsec)-->(NIC1)DUT OS
-It then tries to perform some data transfer using the scheme decribed above.
+It then tries to perform some data transfer using the scheme described above.
usage
~~~~~
diff --git a/doc/guides/sample_app_ug/performance_thread.rst b/doc/guides/sample_app_ug/performance_thread.rst
index e2c04ef..ac6ee8a 100644
--- a/doc/guides/sample_app_ug/performance_thread.rst
+++ b/doc/guides/sample_app_ug/performance_thread.rst
@@ -500,8 +500,8 @@ An application may save and retrieve a single pointer to application data in
the L-thread struct.
For legacy and backward compatibility reasons two alternative methods are also
-offered, the first is modelled directly on the pthread get/set specific APIs,
-the second approach is modelled on the ``RTE_PER_LCORE`` macros, whereby
+offered, the first is modeled directly on the pthread get/set specific APIs,
+the second approach is modeled on the ``RTE_PER_LCORE`` macros, whereby
``PER_LTHREAD`` macros are introduced, in both cases the storage is local to
the L-thread.
diff --git a/doc/guides/sample_app_ug/qos_metering.rst b/doc/guides/sample_app_ug/qos_metering.rst
index 2e8e017..d75f7da 100644
--- a/doc/guides/sample_app_ug/qos_metering.rst
+++ b/doc/guides/sample_app_ug/qos_metering.rst
@@ -151,5 +151,5 @@ In this particular case:
* For the rest of the cases, the color is changed to red.
.. note::
- * In color blind mode, first row GREEN colour is only valid.
+ * In color blind mode, first row GREEN color is only valid.
* To drop the packet, policer_table action has to be set to DROP.
diff --git a/doc/guides/sample_app_ug/test_pipeline.rst b/doc/guides/sample_app_ug/test_pipeline.rst
index 5f313c5..5aefd8d 100644
--- a/doc/guides/sample_app_ug/test_pipeline.rst
+++ b/doc/guides/sample_app_ug/test_pipeline.rst
@@ -32,7 +32,7 @@ Compiling the Application
-------------------------
To compile the sample application see :doc:`compiling`
-The application is located in the ``$RTE_SDK/app/test-pipline`` directory.
+The application is located in the ``$RTE_SDK/app/test-pipeline`` directory.
Running the Application
diff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst
index df4d6f9..a71ada6 100644
--- a/doc/guides/sample_app_ug/vhost.rst
+++ b/doc/guides/sample_app_ug/vhost.rst
@@ -116,7 +116,7 @@ will create it. Put simply, it's the server to create the socket file.
The vm2vm parameter sets the mode of packet switching between guests in
the host.
-- 0 disables vm2vm, impling that VM's packets will always go to the NIC port.
+- 0 disables vm2vm, implying that VM's packets will always go to the NIC port.
- 1 means a normal mac lookup packet routing.
- 2 means hardware mode packet forwarding between guests, it allows packets
go to the NIC port, hardware L2 switch will determine which guest the
@@ -148,7 +148,7 @@ default value is 15.
**--dequeue-zero-copy**
Dequeue zero copy will be enabled when this option is given. it is worth to
-note that if NIC is binded to driver with iommu enabled, dequeue zero copy
+note that if NIC is bound to driver with iommu enabled, dequeue zero copy
cannot work at VM2NIC mode (vm2vm=0) due to currently we don't setup iommu
dma mapping for guest memory.
diff --git a/doc/guides/sample_app_ug/vhost_scsi.rst b/doc/guides/sample_app_ug/vhost_scsi.rst
index 7ab7d0d..6b9bf62 100644
--- a/doc/guides/sample_app_ug/vhost_scsi.rst
+++ b/doc/guides/sample_app_ug/vhost_scsi.rst
@@ -63,7 +63,7 @@ Vhost_scsi Common Issues
* vhost_scsi can not start with block size 512 Bytes:
- Currently DPDK vhost library was designed for NET device(althrough the APIs
+ Currently DPDK vhost library was designed for NET device(although the APIs
are generic now), for 512 Bytes block device, Qemu BIOS(x86 BIOS Enhanced
Disk Device) will enumerate all block device and do some IOs to those block
devices with 512 Bytes sector size. DPDK vhost library can not process such
diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst
index 14d432e..7d73de3 100644
--- a/doc/guides/sample_app_ug/vm_power_management.rst
+++ b/doc/guides/sample_app_ug/vm_power_management.rst
@@ -53,8 +53,8 @@ The solution is comprised of two high-level components:
application below for more information on setting the policy values.
- Out-of-band monitoring of workloads via cores hardware event counters:
- The host application can manage power for an application in a virtualised
- OR non-virtualised environment by looking at the event counters of the
+ The host application can manage power for an application in a virtualized
+ OR non-virtualized environment by looking at the event counters of the
cores and taking action based on the branch hit/miss ratio. See the host
application '--core-list' command line parameter below.
@@ -344,7 +344,7 @@ monitoring of branch ratio on cores doing busy polling via PMDs.
When this parameter is used, the list of cores specified will monitor the ratio
between branch hits and branch misses. A tightly polling PMD thread will have a
- very low branch ratio, so the core frequency will be scaled down to the minimim
+ very low branch ratio, so the core frequency will be scaled down to the minimum
allowed value. When packets are received, the code path will alter, causing the
branch ratio to increase. When the ratio goes above the ratio threshold, the
core frequency will be scaled up to the maximum allowed value.
@@ -384,7 +384,7 @@ the file.
The fifo is at /tmp/powermonitor/fifo
-The jason string can be a policy or instruction, and takes the following
+The JSON string can be a policy or instruction, and takes the following
format:
.. code-block:: javascript
@@ -734,7 +734,7 @@ policy down to the host application. These parameters are as follows:
A comma-separated list of cores in the VM that the user wants the host application to
monitor. The list of cores in any vm starts at zero, and these are mapped to the
physical cores by the host application once the policy is passed down.
- Valid syntax includes individial cores '2,3,4', or a range of cores '2-4', or a
+ Valid syntax includes individual cores '2,3,4', or a range of cores '2-4', or a
combination of both '1,3,5-7'
.. code-block:: console
@@ -742,7 +742,7 @@ policy down to the host application. These parameters are as follows:
--busy-hours {list of busy hours}
A comma-separated list of hours within which to set the core frequency to maximum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console
@@ -750,7 +750,7 @@ policy down to the host application. These parameters are as follows:
--quiet-hours {list of quiet hours}
A comma-separated list of hours within which to set the core frequency to minimum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console
diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
index b717b8c..eb632e2 100644
--- a/doc/guides/testpmd_app_ug/run_app.rst
+++ b/doc/guides/testpmd_app_ug/run_app.rst
@@ -369,7 +369,7 @@ The commandline options are:
* ``--hot-plug``
- Enable device event monitor machenism for hotplug.
+ Enable device event monitor mechanism for hotplug.
* ``--vxlan-gpe-port=N``
@@ -409,21 +409,21 @@ The commandline options are:
* ``--noisy-lkup-memory=N``
- Set the size of the noisy neighbour simulation memory buffer in MB to N.
+ Set the size of the noisy neighbor simulation memory buffer in MB to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-reads=N``
- Set the number of reads to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of reads to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-writes=N``
- Set the number of writes to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of writes to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-reads-writes=N``
- Set the number of r/w accesses to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of r/w accesses to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index 06c8b2a..8eb39cd 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -302,7 +302,7 @@ The available information categories are:
This is the default mode.
* ``mac``: Changes the source and the destination Ethernet addresses of packets before forwarding them.
- Default application behaviour is to set source Ethernet address to that of the transmitting interface, and destination
+ Default application behavior is to set source Ethernet address to that of the transmitting interface, and destination
address to a dummy value (set during init). The user may specify a target destination Ethernet address via the 'eth-peer' or
'eth-peers-configfile' command-line options. It is not currently possible to specify a specific source Ethernet address.
@@ -323,9 +323,9 @@ The available information categories are:
* ``ieee1588``: Demonstrate L2 IEEE1588 V2 PTP timestamping for RX and TX. Requires ``CONFIG_RTE_LIBRTE_IEEE1588=y``.
* ``softnic``: Demonstrates the softnic forwarding operation. In this mode, packet forwarding is
- similar to I/O mode except for the fact that packets are loopback to the softnic ports only. Therefore, portmask parameter should be set to softnic port only. The various software based custom NIC pipelines specified through the softnic firmware (DPDK packet framework script) can be tested in this mode. Furthermore, it allows to build 5-level hierarchical QoS scheduler as a default option that can be enabled through CLI once testpmd application is initialised. The user can modify the default scheduler hierarchy or can specify the new QoS Scheduler hierarchy through CLI. Requires ``CONFIG_RTE_LIBRTE_PMD_SOFTNIC=y``.
+ similar to I/O mode except for the fact that packets are loopback to the softnic ports only. Therefore, portmask parameter should be set to softnic port only. The various software based custom NIC pipelines specified through the softnic firmware (DPDK packet framework script) can be tested in this mode. Furthermore, it allows to build 5-level hierarchical QoS scheduler as a default option that can be enabled through CLI once testpmd application is initialized. The user can modify the default scheduler hierarchy or can specify the new QoS Scheduler hierarchy through CLI. Requires ``CONFIG_RTE_LIBRTE_PMD_SOFTNIC=y``.
-* ``noisy``: Noisy neighbour simulation.
+* ``noisy``: Noisy neighbor simulation.
Simulate more realistic behavior of a guest machine engaged in receiving
and sending packets performing Virtual Network Function (VNF).
@@ -2286,7 +2286,7 @@ set bonding lacp dedicated_queue
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enable dedicated tx/rx queues on bonding devices slaves to handle LACP control plane traffic
-when in mode 4 (link-aggregration-802.3ad)::
+when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding lacp dedicated_queues (port_id) (enable|disable)
@@ -2294,7 +2294,7 @@ when in mode 4 (link-aggregration-802.3ad)::
set bonding agg_mode
~~~~~~~~~~~~~~~~~~~~
-Enable one of the specific aggregators mode when in mode 4 (link-aggregration-802.3ad)::
+Enable one of the specific aggregators mode when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding agg_mode (port_id) (bandwidth|count|stable)
@@ -2688,8 +2688,8 @@ where:
* ``shared_shaper_id``: Shared shaper ID to be deleted.
-Set port traffic management hiearchy node private shaper
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Set port traffic management hierarchy node private shaper
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
set the port traffic management hierarchy node private shaper::
@@ -2740,7 +2740,7 @@ Delete the WRED profile::
Add port traffic management hierarchy nonleaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add nonleaf node to port traffic management hiearchy::
+Add nonleaf node to port traffic management hierarchy::
testpmd> add port tm nonleaf node (port_id) (node_id) (parent_node_id) \
(priority) (weight) (level_id) (shaper_profile_id) \
@@ -2755,7 +2755,7 @@ where:
* ``weight``: Node weight (lowest weight is one). The node weight is relative
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
* ``n_sp_priorities``: Number of strict priorities.
@@ -2766,7 +2766,7 @@ where:
Add port traffic management hierarchy leaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add leaf node to port traffic management hiearchy::
+Add leaf node to port traffic management hierarchy::
testpmd> add port tm leaf node (port_id) (node_id) (parent_node_id) \
(priority) (weight) (level_id) (shaper_profile_id) \
@@ -2781,7 +2781,7 @@ where:
* ``weight``: Node weight (lowest weight is one). The node weight is relative
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
* ``cman_mode``: Congestion management mode to be enabled for this node.
@@ -2793,7 +2793,7 @@ where:
Delete port traffic management hierarchy node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Delete node from port traffic management hiearchy::
+Delete node from port traffic management hierarchy::
testpmd> del port tm node (port_id) (node_id)
@@ -3986,7 +3986,7 @@ This section lists supported actions and their attributes, if any.
- ``dec_ttl``: Performs a decrease TTL value action
-- ``set_ttl``: Set TTL value with specificed value
+- ``set_ttl``: Set TTL value with specified value
- ``ttl_value {unsigned}``: The new TTL value to be set
- ``set_mac_src``: set source MAC address
@@ -4519,7 +4519,7 @@ The following sections show functions to load/unload eBPF based filters.
bpf-load
~~~~~~~~
-Load an eBPF program as a callback for partciular RX/TX queue::
+Load an eBPF program as a callback for particular RX/TX queue::
testpmd> bpf-load rx|tx (portid) (queueid) (load-flags) (bpf-prog-filename)
@@ -4557,7 +4557,7 @@ To load (not JITed) t1.o at TX queue 0, port 0::
bpf-unload
~~~~~~~~~~
-Unload previously loaded eBPF program for partciular RX/TX queue::
+Unload previously loaded eBPF program for particular RX/TX queue::
testpmd> bpf-unload rx|tx (portid) (queueid)
diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst
index c366af4..2fc6544 100644
--- a/doc/guides/tools/cryptoperf.rst
+++ b/doc/guides/tools/cryptoperf.rst
@@ -59,7 +59,7 @@ To set on the linearization options add below definition to the
**Step 3: Build the application**
Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the
-``dpdk-test-crypto-perf`` applcation.
+``dpdk-test-crypto-perf`` application.
Initially, the user must select a DPDK target to choose the correct target type
and compiler options to use when building the libraries.
@@ -80,7 +80,7 @@ EAL Options
~~~~~~~~~~~
The following are the EAL command-line options that can be used in conjunction
-with the ``dpdk-test-crypto-perf`` applcation.
+with the ``dpdk-test-crypto-perf`` application.
See the DPDK Getting Started Guides for more information on these options.
* ``-c <COREMASK>`` or ``-l <CORELIST>``
@@ -96,10 +96,10 @@ See the DPDK Getting Started Guides for more information on these options.
Add a virtual device.
-Appication Options
-~~~~~~~~~~~~~~~~~~
+Application Options
+~~~~~~~~~~~~~~~~~~~
-The following are the appication command-line options:
+The following are the application command-line options:
* ``--ptest type``
@@ -338,13 +338,13 @@ Test Vector File
The test vector file is a text file contain information about test vectors.
The file is made of the sections. The first section doesn't have header.
It contain global information used in each test variant vectors -
-typically information about plaintext, ciphertext, cipher key, aut key,
+typically information about plaintext, ciphertext, cipher key, auth key,
initial vector. All other sections begin header.
The sections contain particular information typically digest.
**Format of the file:**
-Each line beginig with sign '#' contain comment and it is ignored by parser::
+Each line beginning with sign '#' contain comment and it is ignored by parser::
# <comment>
@@ -352,16 +352,16 @@ Header line is just name in square bracket::
[<section name>]
-Data line contain information tocken then sign '=' and
+Data line contain information token then sign '=' and
a string of bytes in C byte array format::
- <tocken> = <C byte array>
+ <token> = <C byte array>
-**Tockens list:**
+**Tokens list:**
* ``plaintext``
- Original plaintext to be crypted.
+ Original plaintext to be encrypted.
* ``ciphertext``
diff --git a/doc/guides/tools/proc_info.rst b/doc/guides/tools/proc_info.rst
index 6bdf5a8..2ea1b59 100644
--- a/doc/guides/tools/proc_info.rst
+++ b/doc/guides/tools/proc_info.rst
@@ -44,7 +44,7 @@ If no port mask is specified xstats are reset for all DPDK ports.
**-m**: Print DPDK memory information.
**--show-port**
-The show-port parameter displays port level various configuration informationi
+The show-port parameter displays port level various configuration information
associated to RX port queue pair.
**--show-tm**
@@ -56,7 +56,7 @@ The show-crypto parameter displays available cryptodev configurations,
settings and stats per node.
**--show-ring[=name]**
-The show-ring pararmeter display current allocation of all ring with
+The show-ring parameter display current allocation of all ring with
debug information. Specifying the name allows to display details for specific
ring. For invalid or no ring name, whole list is dump.
@@ -76,7 +76,7 @@ Limitations
* When running ``dpdk-procinfo`` with shared library mode, it is required to
pass the same NIC PMD libraries as used for the primary application. Any
- mismatch in PMD library arguments can lead to undefined behaviour and results
+ mismatch in PMD library arguments can lead to undefined behavior and results
affecting primary application too.
* Stats retrieval using ``dpdk-procinfo`` is not supported for virtual devices like PCAP and TAP.
diff --git a/doc/guides/tools/testbbdev.rst b/doc/guides/tools/testbbdev.rst
index f338647..0001a0d 100644
--- a/doc/guides/tools/testbbdev.rst
+++ b/doc/guides/tools/testbbdev.rst
@@ -139,7 +139,7 @@ There are 6 main test cases that can be executed using testbbdev tool:
* Latency measurement [-c latency]
- Measures the time consumed from the first enqueue until the first
appearance of a dequeued result
- - This measurment represents the full latency of a bbdev operation
+ - This measurement represents the full latency of a bbdev operation
(encode or decode) to execute
* Poll-mode Throughput measurement [-c throughput]
--
2.7.5
^ permalink raw reply [relevance 3%]
* [dpdk-dev] [PATCH v1] doc: fix spelling errors reported by aspell
2019-04-03 13:26 3% [dpdk-dev] [PATCH v1] doc: fix spelling errors reported by aspell John McNamara
@ 2019-04-03 13:26 3% ` John McNamara
0 siblings, 0 replies; 140+ results
From: John McNamara @ 2019-04-03 13:26 UTC (permalink / raw)
To: dev; +Cc: John McNamara
Signed-off-by: John McNamara <john.mcnamara@intel.com>
---
Some notes on this.
It is probably best not to apply this patch until just before the release
since it could potentially create a lot of conflicts. I'll resubmit a v2
prior to the 19.05 release.
The fixes list is below. I didn't include them in the commit message
since I don't think the effort of backporting is worth it.
Fixes: a6531d58b415 ("compressdev: replace mbuf scatter gather flag")
Fixes: 58abf6e77c6b ("doc: add contributors guide")
Fixes: 3728e9ba7739 ("crypto/aesni_mb: support IPSec Multi-buffer lib v0.46")
Fixes: 2717246ecd7d ("cryptodev: replace mbuf scatter gather flag")
Fixes: 02545b6ca29a ("doc: update build instructions for qat PMDs")
Fixes: 4c07e0552f0a ("crypto/scheduler: add multicore scheduling mode")
Fixes: c7aa67f5a9e4 ("doc: add eventdev OPDL PMD guide")
Fixes: 0857b9421138 ("doc: add event device and software eventdev")
Fixes: 206b6ba882cf ("doc: add VF live migration howto with bonded virtio")
Fixes: 6993fe1375c1 ("doc: add VM live migration howto with vhost-user")
Fixes: 3e0ceb9f17ff ("doc: add basic howto for flow API")
Fixes: 6e9270eab112 ("doc: add telemetry how-to")
Fixes: 0ba3870e7559 ("doc: add guide to use virtio-user as exceptional path")
Fixes: 6ef75e405d5a ("doc: add af_packet PMD guide")
Fixes: 3d38e3dcf197 ("net/atlantic: implement Rx path")
Fixes: 6c2809628cd5 ("net/cxgbe: improve latency for slow traffic")
Fixes: cda260a4ac1a ("net/cxgbe: add option to keep outer VLAN tag in QinQ")
Fixes: 0c504f6950b6 ("net/dpaa: support push mode")
Fixes: 846a8305f277 ("doc: add DPAA2 NIC details")
Fixes: 61e093398fbc ("doc: add instructions for WC in ENAv2")
Fixes: 65313f1a822a ("doc: add guide for ENETC PMD")
Fixes: 0543f9d24ae1 ("net/enic: flow API documentation")
Fixes: 13e855a3b996 ("doc: add inline crypto feature")
Fixes: 04c8542f96f7 ("net/i40e: set TC strict priority mode")
Fixes: 621c5c1db2b1 ("doc: add ixgbe known issue with legacy interrrupt")
Fixes: 75e2bc54c018 ("net/kni: add KNI PMD")
Fixes: 2c0dd7b69fb0 ("config: add static linkage of mlx dependency")
Fixes: 0280f2812284 ("doc: add mlx5 E-Switch VXLAN tunnels limitations")
Fixes: 2c0dd7b69fb0 ("config: add static linkage of mlx dependency")
Fixes: 7d6bf6b866b8 ("net/mlx5: add Multi-Packet Rx support")
Fixes: 0ba610ca1d17 ("net/mvpp2: document MTR and TM usage")
Fixes: 4b048f352c01 ("doc: clarify usage of netvsc PMD")
Fixes: ef28aa96e53b ("net/nfp: support multiprocess")
Fixes: c7cb2d7a5f2a ("net/sfc: add device configuration checks")
Fixes: 8cb45c97d396 ("net/sfc: add unknown unicast/multicast match in flow API")
Fixes: c22d3c508e0c ("net/sfc: support parameter to choose performance profile")
Fixes: a5e1231f099b ("net/szedata2: do not affect Ethernet interfaces")
Fixes: bcab6c1d27fa ("net/tap: allow user MAC to be passed as args")
Fixes: ceccf8dc7c3d ("doc: create NXP DPAA platform guide")
Fixes: b84c108742a9 ("doc: create NXP DPAA2 platform guide")
Fixes: 4935e1e9f76e ("bbdev: introduce wireless base band device lib")
Fixes: a584d3bea902 ("doc: add compressdev library guide")
Fixes: 0318c02b57cf ("doc: add cryptodev chapter in prog guide")
Fixes: c149818b0e51 ("doc: add note on multiple crypto vdevs")
Fixes: 0318c02b57cf ("doc: add cryptodev chapter in prog guide")
Fixes: 31850d26850e ("doc: add cryptodev sample code")
Fixes: b9209dc21999 ("doc: add asymmetric crypto in programmer guide")
Fixes: a5d7a3f77ddc ("unify tools naming")
Fixes: 0dd62a01874a ("doc: add EFD library section in programmers guide")
Fixes: b31739328354 ("doc: update guides for memory subsystem")
Fixes: 3810ae435783 ("eventdev: add interrupt driven queues to Rx adapter")
Fixes: c1eaab510dba ("eventdev: add callback for Rx adapter SW transfers")
Fixes: 7358c91ffa85 ("doc: add eventdev library to programmers guide")
Fixes: 50bdac5916d9 ("flow_classify: remove table id parameter from API")
Fixes: fdec9301f52d ("doc: add flow classify guides")
Fixes: 9ef6cb1a1583 ("doc: add IPsec library guide")
Fixes: 89397a01ce4a ("kni: set default carrier state of interface")
Fixes: 349950ddb9c5 ("metrics: add information metrics library")
Fixes: 2ad7ba9a6567 ("bitrate: add bitrate statistics library")
Fixes: 5cd3cac9ed22 ("latency: added new library for latency stats")
Fixes: e22266669e86 ("doc: add IPC guide")
Fixes: 9d5ba88c2d41 ("doc: add ARM profiling methods")
Fixes: 7307cf6333ca ("ethdev: add raw encapsulation action")
Fixes: 6f1c2168bccb ("ethdev: add generic TTL rewrite actions")
Fixes: 40ff8c99ea99 ("doc: add details of security library")
Fixes: e660897d8a0a ("doc: describe traffic management API")
Fixes: 9ba1e744ab65 ("vhost: add a flag to enable dequeue zero copy")
Fixes: ef1e8ede3da5 ("raw/ifpga: add Intel FPGA bus rawdev driver")
Fixes: 86fa6c57a175 ("doc: add known igb_uio issue for i40e")
Fixes: b667029e9096 ("doc: add Linux 4.10.0 known issue in release notes")
Fixes: a32ca9a4ebc1 ("mk: fix scope of disabling AVX512F support")
Fixes: c9b13d944088 ("doc: update release notes for 17.11")
Fixes: 1ffee690eaa1 ("examples/bbdev: add sample app")
Fixes: 1094ca96689c ("doc: add SW eventdev pipeline to sample app guide")
Fixes: fdec9301f52d ("doc: add flow classify guides")
Fixes: bef33b0a9d58 ("doc: add new introduction to sample app guides")
Fixes: 71f2e9ba7d8c ("doc: update IP pipeline application guide")
Fixes: ec17993a145a ("examples/ipsec-secgw: support security offload")
Fixes: 02dc5b7d58c7 ("doc: update ipsec-secgw guide and release notes")
Fixes: 4d1a771bd88d ("doc: add guide for performance-thread example")
Fixes: 331ce43dc564 ("doc: add policer table details for metering application")
Fixes: 474572d2ae5a ("app/pipeline: move from test directory")
Fixes: a971c509a523 ("doc: update vhost sample guide")
Fixes: e3075e969eff ("doc: add driver limitation for vhost dequeue zero copy")
Fixes: db75c7af19bb ("examples/vhost_scsi: introduce a new sample app")
Fixes: 50ac590ff826 ("doc: update VM power manager sample guide")
Fixes: a63504a90f6a ("examples/power: add JSON string handling")
Fixes: 50ac590ff826 ("doc: update VM power manager sample guide")
Fixes: fb73e096110a ("app/testpmd: enable device hotplug monitoring")
Fixes: 3c156061b938 ("app/testpmd: add noisy neighbour forwarding mode")
Fixes: a67857e97ba8 ("doc: clarify usage of testpmd MAC forward mode")
Fixes: 8d9d4c2428be ("app/testpmd: update softnic mode documentation")
Fixes: c4e04283abee ("doc: fix literal block in testpmd guide")
Fixes: 0aeb7077d171 ("doc: add 802.3ad modes in testpmd guide")
Fixes: 5b590fbe09b6 ("app/testpmd: add traffic management forwarding mode")
Fixes: 708d0bcb72c2 ("app/testpmd: add commands to modify TTL")
Fixes: e977e4199a8d ("app/testpmd: add commands to load/unload BPF filters")
Fixes: c6baca7adc94 ("doc: describe new performance test application")
Fixes: 98a7ea332ba3 ("fix typos using codespell utility")
Fixes: c6baca7adc94 ("doc: describe new performance test application")
Fixes: 8a37f37fc243 ("app/procinfo: add --show-port")
Fixes: c13e8984404a ("app/procinfo: add --show-ring")
Fixes: bacf34762ac5 ("doc: update limitations in procinfo guide")
Fixes: 8723590ec603 ("doc: update bbdev test app guide")
doc/guides/compressdevs/overview.rst | 2 +-
doc/guides/contributing/patches.rst | 2 +-
doc/guides/cryptodevs/aesni_mb.rst | 2 +-
doc/guides/cryptodevs/overview.rst | 2 +-
doc/guides/cryptodevs/qat.rst | 2 +-
doc/guides/cryptodevs/scheduler.rst | 2 +-
doc/guides/eventdevs/opdl.rst | 4 +--
doc/guides/eventdevs/sw.rst | 4 +--
doc/guides/howto/lm_bond_virtio_sriov.rst | 2 +-
doc/guides/howto/lm_virtio_vhost_user.rst | 4 +--
doc/guides/howto/rte_flow.rst | 6 ++---
doc/guides/howto/telemetry.rst | 2 +-
.../howto/virtio_user_as_exceptional_path.rst | 8 +++---
doc/guides/nics/af_packet.rst | 4 +--
doc/guides/nics/atlantic.rst | 2 +-
doc/guides/nics/cxgbe.rst | 4 +--
doc/guides/nics/dpaa.rst | 2 +-
doc/guides/nics/dpaa2.rst | 2 +-
doc/guides/nics/ena.rst | 2 +-
doc/guides/nics/enetc.rst | 2 +-
doc/guides/nics/enic.rst | 2 +-
doc/guides/nics/features.rst | 2 +-
doc/guides/nics/i40e.rst | 2 +-
doc/guides/nics/ixgbe.rst | 4 +--
doc/guides/nics/kni.rst | 2 +-
doc/guides/nics/mlx4.rst | 2 +-
doc/guides/nics/mlx5.rst | 10 ++++----
doc/guides/nics/mvpp2.rst | 2 +-
doc/guides/nics/netvsc.rst | 2 +-
doc/guides/nics/nfp.rst | 4 +--
doc/guides/nics/sfc_efx.rst | 14 +++++-----
doc/guides/nics/szedata2.rst | 2 +-
doc/guides/nics/tap.rst | 2 +-
doc/guides/platform/dpaa.rst | 4 +--
doc/guides/platform/dpaa2.rst | 4 +--
doc/guides/prog_guide/bbdev.rst | 4 +--
doc/guides/prog_guide/compressdev.rst | 6 ++---
doc/guides/prog_guide/cryptodev_lib.rst | 14 +++++-----
doc/guides/prog_guide/dev_kit_build_system.rst | 2 +-
doc/guides/prog_guide/efd_lib.rst | 2 +-
doc/guides/prog_guide/env_abstraction_layer.rst | 2 +-
.../prog_guide/event_ethernet_rx_adapter.rst | 6 ++---
doc/guides/prog_guide/eventdev.rst | 6 ++---
doc/guides/prog_guide/flow_classify_lib.rst | 12 ++++-----
doc/guides/prog_guide/ipsec_lib.rst | 16 ++++++------
doc/guides/prog_guide/kernel_nic_interface.rst | 2 +-
doc/guides/prog_guide/metrics_lib.rst | 12 ++++-----
doc/guides/prog_guide/multi_proc_support.rst | 2 +-
doc/guides/prog_guide/profile_app.rst | 4 +--
doc/guides/prog_guide/rte_flow.rst | 6 ++---
doc/guides/prog_guide/rte_security.rst | 20 +++++++--------
doc/guides/prog_guide/traffic_management.rst | 2 +-
doc/guides/prog_guide/vhost_lib.rst | 2 +-
doc/guides/rawdevs/ifpga_rawdev.rst | 2 +-
doc/guides/rel_notes/known_issues.rst | 8 +++---
doc/guides/rel_notes/release_17_11.rst | 10 ++++----
doc/guides/sample_app_ug/bbdev_app.rst | 4 +--
doc/guides/sample_app_ug/eventdev_pipeline.rst | 2 +-
doc/guides/sample_app_ug/flow_classify.rst | 8 +++---
doc/guides/sample_app_ug/intro.rst | 2 +-
doc/guides/sample_app_ug/ip_pipeline.rst | 4 +--
doc/guides/sample_app_ug/ipsec_secgw.rst | 8 +++---
doc/guides/sample_app_ug/performance_thread.rst | 4 +--
doc/guides/sample_app_ug/qos_metering.rst | 2 +-
doc/guides/sample_app_ug/test_pipeline.rst | 2 +-
doc/guides/sample_app_ug/vhost.rst | 4 +--
doc/guides/sample_app_ug/vhost_scsi.rst | 2 +-
doc/guides/sample_app_ug/vm_power_management.rst | 14 +++++-----
doc/guides/testpmd_app_ug/run_app.rst | 10 ++++----
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 30 +++++++++++-----------
doc/guides/tools/cryptoperf.rst | 22 ++++++++--------
doc/guides/tools/proc_info.rst | 6 ++---
doc/guides/tools/testbbdev.rst | 2 +-
73 files changed, 192 insertions(+), 192 deletions(-)
diff --git a/doc/guides/compressdevs/overview.rst b/doc/guides/compressdevs/overview.rst
index 70bbe82..809e4e6 100644
--- a/doc/guides/compressdevs/overview.rst
+++ b/doc/guides/compressdevs/overview.rst
@@ -18,7 +18,7 @@ Supported Feature Flags
without making any modifications to it (no compression done).
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means PMD supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index d8404e6..3b2b174 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -8,7 +8,7 @@ Contributing Code to DPDK
This document outlines the guidelines for submitting code to DPDK.
-The DPDK development process is modelled (loosely) on the Linux Kernel development model so it is worth reading the
+The DPDK development process is modeled (loosely) on the Linux Kernel development model so it is worth reading the
Linux kernel guide on submitting patches:
`How to Get Your Change Into the Linux Kernel <https://www.kernel.org/doc/html/latest/process/submitting-patches.html>`_.
The rationale for many of the DPDK guidelines is explained in greater detail in the kernel guidelines.
diff --git a/doc/guides/cryptodevs/aesni_mb.rst b/doc/guides/cryptodevs/aesni_mb.rst
index 47f2ecc..b61802d 100644
--- a/doc/guides/cryptodevs/aesni_mb.rst
+++ b/doc/guides/cryptodevs/aesni_mb.rst
@@ -133,7 +133,7 @@ Extra notes
For AES Counter mode (AES-CTR), the library supports two different sizes for Initialization
Vector (IV):
-* 12 bytes: used mainly for IPSec, as it requires 12 bytes from the user, which internally
+* 12 bytes: used mainly for IPsec, as it requires 12 bytes from the user, which internally
are appended the counter block (4 bytes), which is set to 1 for the first block
(no padding required from the user)
diff --git a/doc/guides/cryptodevs/overview.rst b/doc/guides/cryptodevs/overview.rst
index 607e758..dd25b22 100644
--- a/doc/guides/cryptodevs/overview.rst
+++ b/doc/guides/cryptodevs/overview.rst
@@ -18,7 +18,7 @@ Supported Feature Flags
being the operation in-place (input address = output address).
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means pmd supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
index da9655c..651bf38 100644
--- a/doc/guides/cryptodevs/qat.rst
+++ b/doc/guides/cryptodevs/qat.rst
@@ -225,7 +225,7 @@ Dependency on the QAT kernel driver
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To use QAT an SRIOV-enabled QAT kernel driver is required. The VF
-devices created and initialised by this driver will be used by the QAT PMDs.
+devices created and initialized by this driver will be used by the QAT PMDs.
Instructions for installation are below, but first an explanation of the
relationships between the PF/VF devices and the PMDs visible to
diff --git a/doc/guides/cryptodevs/scheduler.rst b/doc/guides/cryptodevs/scheduler.rst
index a754a27..7004ca4 100644
--- a/doc/guides/cryptodevs/scheduler.rst
+++ b/doc/guides/cryptodevs/scheduler.rst
@@ -165,7 +165,7 @@ operation:
For pure small packet size (64 bytes) traffic however the multi-core mode is not
an optimal solution, as it doesn't give significant per-core performance improvement.
For mixed traffic (IMIX) the optimal number of worker cores is around 2-3.
- For large packets (1.5 Kbytes) scheduler shows linear scaling in performance
+ For large packets (1.5 kbytes) scheduler shows linear scaling in performance
up to eight cores.
Each worker uses its own slave cryptodev. Only software cryptodevs
are supported. Only the same type of cryptodevs should be used concurrently.
diff --git a/doc/guides/eventdevs/opdl.rst b/doc/guides/eventdevs/opdl.rst
index 0262a33..8334ba5 100644
--- a/doc/guides/eventdevs/opdl.rst
+++ b/doc/guides/eventdevs/opdl.rst
@@ -8,7 +8,7 @@ The OPDL (Ordered Packet Distribution Library) eventdev is a specific\
implementation of the eventdev API. It is particularly suited to packet\
processing workloads that have high throughput and low latency requirements.\
All packets follow the same path through the device. The order in which\
-packets follow is determinted by the order in which queues are set up.\
+packets follow is determined by the order in which queues are set up.\
Events are left on the ring until they are transmitted. As a result packets\
do not go out of order
@@ -61,7 +61,7 @@ Queue Dependencies
As stated the order in which packets travel through queues is static in
nature. They go through the queues in the order the queues are setup at
-initialisation ``rte_event_queue_setup()``. For example if an application
+initialization ``rte_event_queue_setup()``. For example if an application
sets up 3 queues, Q0, Q1, Q2 and has 3 associated ports P0, P1, P2 and
P3 then packets must be
diff --git a/doc/guides/eventdevs/sw.rst b/doc/guides/eventdevs/sw.rst
index afdcad7..04c8b03 100644
--- a/doc/guides/eventdevs/sw.rst
+++ b/doc/guides/eventdevs/sw.rst
@@ -70,7 +70,7 @@ Credit Quanta
The credit quanta is the number of credits that a port will fetch at a time from
the instance's credit pool. Higher numbers will cause less overhead in the
atomic credit fetch code, however it also reduces the overall number of credits
-in the system faster. A balanced number (eg 32) ensures that only small numbers
+in the system faster. A balanced number (e.g. 32) ensures that only small numbers
of credits are pre-allocated at a time, while also mitigating performance impact
of the atomics.
@@ -100,7 +100,7 @@ feature would be significant.
~~~~~~~~~~~~~~~~~~
The software eventdev does not support creating queues that handle all types of
-traffic. An eventdev with this capability allows enqueueing Atomic, Ordered and
+traffic. An eventdev with this capability allows enqueuing Atomic, Ordered and
Parallel traffic to the same queue, but scheduling each of them appropriately.
The reason to not allow Atomic, Ordered and Parallel event types in the
diff --git a/doc/guides/howto/lm_bond_virtio_sriov.rst b/doc/guides/howto/lm_bond_virtio_sriov.rst
index ee8ccda..07563b3 100644
--- a/doc/guides/howto/lm_bond_virtio_sriov.rst
+++ b/doc/guides/howto/lm_bond_virtio_sriov.rst
@@ -328,7 +328,7 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
testpmd> show bonding config 2
testpmd> port attach 0000:00:04.0
diff --git a/doc/guides/howto/lm_virtio_vhost_user.rst b/doc/guides/howto/lm_virtio_vhost_user.rst
index 6ebc10f..ecb7832 100644
--- a/doc/guides/howto/lm_virtio_vhost_user.rst
+++ b/doc/guides/howto/lm_virtio_vhost_user.rst
@@ -243,7 +243,7 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
Virtio traffic is seen at P0 and P1.
@@ -338,7 +338,7 @@ reset_vf_on_212_131.sh
#!/bin/sh
# This script is run on the host 10.237.212.131 to reset SRIOV
- # BDF for Ninatic NIC is 0000:06:00.0
+ # BDF for Niantic NIC is 0000:06:00.0
cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
echo 0 > /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
diff --git a/doc/guides/howto/rte_flow.rst b/doc/guides/howto/rte_flow.rst
index 3dcda6c..e197376 100644
--- a/doc/guides/howto/rte_flow.rst
+++ b/doc/guides/howto/rte_flow.rst
@@ -23,7 +23,7 @@ In this example we will create a simple rule that drops packets whose IPv4
destination equals 192.168.3.2. This code is equivalent to the following
testpmd command (wrapped for clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst is 192.168.3.2 / end actions drop / end
Code
@@ -118,7 +118,7 @@ a mask.
This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst spec 192.168.3.0 dst mask 255.255.255.0 /
end actions drop / end
@@ -219,7 +219,7 @@ In this example we will create a rule that routes all vlan id 123 to queue 3.
This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
+ testpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
end actions queue index 3 / end
Code
diff --git a/doc/guides/howto/telemetry.rst b/doc/guides/howto/telemetry.rst
index 00f8f7a..e10804d 100644
--- a/doc/guides/howto/telemetry.rst
+++ b/doc/guides/howto/telemetry.rst
@@ -18,7 +18,7 @@ which acts as the client.
In DPDK, applications are used to initialize the ``telemetry``. To view incoming
traffic on featured ports, the application should be run first (ie. after ports
are configured). Once the application is running, the service assurance agent
-(for example the collectd plugin) should be run to begin querying the API.
+(for example the CollectD plugin) should be run to begin querying the API.
A client connects their Service Assurance application to the DPDK application
via a UNIX socket. Once a connection is established, a client can send JSON
diff --git a/doc/guides/howto/virtio_user_as_exceptional_path.rst b/doc/guides/howto/virtio_user_as_exceptional_path.rst
index 4910c12..ec021af 100644
--- a/doc/guides/howto/virtio_user_as_exceptional_path.rst
+++ b/doc/guides/howto/virtio_user_as_exceptional_path.rst
@@ -1,7 +1,7 @@
.. SPDX-License-Identifier: BSD-3-Clause
Copyright(c) 2016 Intel Corporation.
-.. _virtio_user_as_excpetional_path:
+.. _virtio_user_as_exceptional_path:
Virtio_user as Exceptional Path
===============================
@@ -22,7 +22,7 @@ solution is very promising in:
* Features
vhost-net is born to be a networking solution, which has lots of networking
- related featuers, like multi queue, tso, multi-seg mbuf, etc.
+ related features, like multi queue, tso, multi-seg mbuf, etc.
* Performance
@@ -38,7 +38,7 @@ in :numref:`figure_virtio_user_as_exceptional_path`.
.. figure:: img/virtio_user_as_exceptional_path.*
- Overview of a DPDK app using virtio-user as excpetional path
+ Overview of a DPDK app using virtio-user as exceptional path
Sample Usage
@@ -75,7 +75,7 @@ compiling the kernel and those kernel modules should be inserted.
* ``queues``
- Number of multi-queues. Each qeueue will be served by a kthread. For example:
+ Number of multi-queues. Each queue will be served by a kthread. For example:
.. code-block:: console
diff --git a/doc/guides/nics/af_packet.rst b/doc/guides/nics/af_packet.rst
index 1260bb2..efd6f1c 100644
--- a/doc/guides/nics/af_packet.rst
+++ b/doc/guides/nics/af_packet.rst
@@ -13,13 +13,13 @@ PACKET_MMAP, which provides a mmap'ed ring buffer, shared between user space
and kernel, that's used to send and receive packets. This helps reducing system
calls and the copies needed between user space and Kernel.
-The PACKET_FANOUT_HASH behaviour of AF_PACKET is used for frame reception.
+The PACKET_FANOUT_HASH behavior of AF_PACKET is used for frame reception.
Options and inherent limitations
--------------------------------
The following options can be provided to set up an af_packet port in DPDK.
-Some of these, in turn, will be used to configure the PAKET_MMAP settings.
+Some of these, in turn, will be used to configure the PACKET_MMAP settings.
* ``iface`` - name of the Kernel interface to attach to (required);
* ``qpairs`` - number of Rx and Tx queues (optional, default 1);
diff --git a/doc/guides/nics/atlantic.rst b/doc/guides/nics/atlantic.rst
index 80591b1..f6f2c66 100644
--- a/doc/guides/nics/atlantic.rst
+++ b/doc/guides/nics/atlantic.rst
@@ -18,7 +18,7 @@ Supported features
- Port statistics
- RSS (Receive Side Scaling)
- Checksum offload
-- Jumbo Frame upto 16K
+- Jumbo Frame up to 16K
Configuration Information
^^^^^^^^^^^^^^^^^^^^^^^^^
diff --git a/doc/guides/nics/cxgbe.rst b/doc/guides/nics/cxgbe.rst
index f3e6115..7a893cc 100644
--- a/doc/guides/nics/cxgbe.rst
+++ b/doc/guides/nics/cxgbe.rst
@@ -126,7 +126,7 @@ enabling debugging options may affect system performance.
- ``CONFIG_RTE_LIBRTE_CXGBE_TPUT`` (default **y**)
- Toggle behaviour to prefer Throughput or Latency.
+ Toggle behavior to prefer Throughput or Latency.
Runtime Options
~~~~~~~~~~~~~~~
@@ -140,7 +140,7 @@ be passed as part of EAL arguments. For example,
- ``keep_ovlan`` (default **0**)
- Toggle behaviour to keep/strip outer VLAN in Q-in-Q packets. If
+ Toggle behavior to keep/strip outer VLAN in Q-in-Q packets. If
enabled, the outer VLAN tag is preserved in Q-in-Q packets. Otherwise,
the outer VLAN tag is stripped in Q-in-Q packets.
diff --git a/doc/guides/nics/dpaa.rst b/doc/guides/nics/dpaa.rst
index fb7bc7d..2243a4a 100644
--- a/doc/guides/nics/dpaa.rst
+++ b/doc/guides/nics/dpaa.rst
@@ -251,7 +251,7 @@ state during application initialization:
automatically be assigned from the these high perf PUSH queues. Any queue
configuration beyond that will be standard Rx queues. The application can
choose to change their number if HW portals are limited.
- The valid values are from '0' to '4'. The valuse shall be set to '0' if the
+ The valid values are from '0' to '4'. The values shall be set to '0' if the
application want to use eventdev with DPAA device.
diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst
index 392ab05..a532d08 100644
--- a/doc/guides/nics/dpaa2.rst
+++ b/doc/guides/nics/dpaa2.rst
@@ -379,7 +379,7 @@ active -- Ethernet, crypto, compression, etc.
DPBP based Mempool driver
~~~~~~~~~~~~~~~~~~~~~~~~~
-The DPBP driver is bound to a DPBP objects and provides sevices to
+The DPBP driver is bound to a DPBP objects and provides services to
create a hardware offloaded packet buffer mempool.
DPAA2 NIC Driver
diff --git a/doc/guides/nics/ena.rst b/doc/guides/nics/ena.rst
index 80da4b6..d44f3cd 100644
--- a/doc/guides/nics/ena.rst
+++ b/doc/guides/nics/ena.rst
@@ -189,7 +189,7 @@ Prerequisites
reduces the latency of the packets by pushing the header directly through
the PCI to the device, before the DMA is even triggered. For proper work
kernel PCI driver must support write combining (WC). In mainline version of
- ``igb_uio`` (in DPDK repo) it must be enabled by loding module with
+ ``igb_uio`` (in DPDK repo) it must be enabled by loading module with
``wc_activate=1`` flag (example below). However, mainline's vfio-pci
driver in kernel doesn't have WC support yet (planed to be added).
If vfio-pci used user should be either turn off ENAv2 (to avoid performance
diff --git a/doc/guides/nics/enetc.rst b/doc/guides/nics/enetc.rst
index 8038bf2..376768d 100644
--- a/doc/guides/nics/enetc.rst
+++ b/doc/guides/nics/enetc.rst
@@ -69,7 +69,7 @@ Supported ENETC SoCs
Prerequisites
~~~~~~~~~~~~~
-There are three main pre-requisities for executing ENETC PMD on a ENETC
+There are three main pre-requisites for executing ENETC PMD on a ENETC
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/nics/enic.rst b/doc/guides/nics/enic.rst
index 726a69e..cdb55e0 100644
--- a/doc/guides/nics/enic.rst
+++ b/doc/guides/nics/enic.rst
@@ -224,7 +224,7 @@ the use of SR-IOV.
passthrough devices do not require libvirt, port profiles, and VM-FEX.
-.. _enic-genic-flow-api:
+.. _enic-generic-flow-api:
Generic Flow API support
------------------------
diff --git a/doc/guides/nics/features.rst b/doc/guides/nics/features.rst
index c5bf322..d57ddc2 100644
--- a/doc/guides/nics/features.rst
+++ b/doc/guides/nics/features.rst
@@ -495,7 +495,7 @@ Supports adding traffic mirroring rules.
Inline crypto
-------------
-Supports inline crypto processing (eg. inline IPsec). See Security library and PMD documentation for more details.
+Supports inline crypto processing (e.g. inline IPsec). See Security library and PMD documentation for more details.
* **[uses] rte_eth_rxconf,rte_eth_rxmode**: ``offloads:DEV_RX_OFFLOAD_SECURITY``,
* **[uses] rte_eth_txconf,rte_eth_txmode**: ``offloads:DEV_TX_OFFLOAD_SECURITY``.
diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 9680a92..2e9ec79 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -580,7 +580,7 @@ bandwidth setting.
TC TX scheduling mode setting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-There're 2 TX scheduling modes for TCs, round robin and strict priority mode.
+There are 2 TX scheduling modes for TCs, round robin and strict priority mode.
If a TC is set to strict priority mode, it can consume unlimited bandwidth.
It means if APP has set the max bandwidth for that TC, it comes to no
effect.
diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
index 1c294b0..975143f 100644
--- a/doc/guides/nics/ixgbe.rst
+++ b/doc/guides/nics/ixgbe.rst
@@ -203,8 +203,8 @@ as a workaround.
X550 does not support legacy interrupt mode
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Desccription
-^^^^^^^^^^^^
+Description
+^^^^^^^^^^^
X550 cannot get interrupts if using ``uio_pci_generic`` module or using legacy
interrupt mode of ``igb_uio`` or ``vfio``. Because the errata of X550 states
that the Interrupt Status bit is not implemented. The errata is the item #22
diff --git a/doc/guides/nics/kni.rst b/doc/guides/nics/kni.rst
index a66c595..602a06b 100644
--- a/doc/guides/nics/kni.rst
+++ b/doc/guides/nics/kni.rst
@@ -65,7 +65,7 @@ backend device by default.
PMD arguments
-------------
-``no_request_thread``, by default PMD creates a phtread for each KNI interface
+``no_request_thread``, by default PMD creates a pthread for each KNI interface
to handle Linux network interface control commands, like ``ifconfig kni0 up``
With ``no_request_thread`` option, pthread is not created and control commands
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index 4ad361a..28e3666 100644
--- a/doc/guides/nics/mlx4.rst
+++ b/doc/guides/nics/mlx4.rst
@@ -83,7 +83,7 @@ These options can be modified in the ``.config`` file.
- ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
- Embed static flavour of the dependencies **libibverbs** and **libmlx4**
+ Embed static flavor of the dependencies **libibverbs** and **libmlx4**
in the PMD shared library or the executable static binary.
- ``CONFIG_RTE_LIBRTE_MLX4_DEBUG`` (default **n**)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 0200373..3f3226a 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -149,7 +149,7 @@ Limitations
- E-Switch VXLAN decapsulation Flow:
- - can be appiled to PF port only.
+ - can be applied to PF port only.
- must specify VF port action (packet redirection from PF to VF).
- must specify tunnel outer UDP local (destination) port, wildcards not allowed.
- must specify tunnel outer VNI, wildcards not allowed.
@@ -164,7 +164,7 @@ Limitations
- must specify the VXLAN item with tunnel outer parameters.
- must specify the tunnel outer VNI in the VXLAN item.
- must specify the tunnel outer remote (destination) UDP port in the VXLAN item.
- - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interace, wildcards not allowed.
+ - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interface, wildcards not allowed.
- must specify the tunnel outer remote (destination) IPv4 or IPv6 in the VXLAN item, group IPs allowed.
- must specify the tunnel outer destination MAC address in the VXLAN item, this address will be used to create neigh rule.
@@ -212,7 +212,7 @@ These options can be modified in the ``.config`` file.
- ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
- Embed static flavour of the dependencies **libibverbs** and **libmlx5**
+ Embed static flavor of the dependencies **libibverbs** and **libmlx5**
in the PMD shared library or the executable static binary.
- ``CONFIG_RTE_LIBRTE_MLX5_DEBUG`` (default **n**)
@@ -319,7 +319,7 @@ Run-time configuration
buffers per a packet, one large buffer is posted in order to receive multiple
packets on the buffer. A MPRQ buffer consists of multiple fixed-size strides
and each stride receives one packet. MPRQ can improve throughput for
- small-packet tarffic.
+ small-packet traffic.
When MPRQ is enabled, max_rx_pkt_len can be larger than the size of
user-provided mbuf even if DEV_RX_OFFLOAD_SCATTER isn't enabled. PMD will
@@ -330,7 +330,7 @@ Run-time configuration
- ``mprq_log_stride_num`` parameter [int]
Log 2 of the number of strides for Multi-Packet Rx queue. Configuring more
- strides can reduce PCIe tarffic further. If configured value is not in the
+ strides can reduce PCIe traffic further. If configured value is not in the
range of device capability, the default value will be set with a warning
message. The default value is 4 which is 16 strides per a buffer, valid only
if ``mprq_en`` is set.
diff --git a/doc/guides/nics/mvpp2.rst b/doc/guides/nics/mvpp2.rst
index 09e2f2a..bacc013 100644
--- a/doc/guides/nics/mvpp2.rst
+++ b/doc/guides/nics/mvpp2.rst
@@ -91,7 +91,7 @@ Limitations
chance to start in a sane state.
- MUSDK architecture does not support changing configuration in run time.
- All nessesary configurations should be done before first dev_start().
+ All necessary configurations should be done before first dev_start().
- RX queue start/stop is not supported.
diff --git a/doc/guides/nics/netvsc.rst b/doc/guides/nics/netvsc.rst
index 87fabf5..6dbb9a5 100644
--- a/doc/guides/nics/netvsc.rst
+++ b/doc/guides/nics/netvsc.rst
@@ -89,7 +89,7 @@ operations:
.. Note::
- The dpkd-devbind.py script can not be used since it only handles PCI devices.
+ The dpdk-devbind.py script can not be used since it only handles PCI devices.
Prerequisites
diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst
index 09a8529..309fa5d 100644
--- a/doc/guides/nics/nfp.rst
+++ b/doc/guides/nics/nfp.rst
@@ -149,8 +149,8 @@ PF multiprocess support
-----------------------
Due to how the driver needs to access the NFP through a CPP interface, which implies
-to use specific registers inside the chip, the number of secondary proceses with PF
-ports is limitted to only one.
+to use specific registers inside the chip, the number of secondary processes with PF
+ports is limited to only one.
This limitation will be solved in future versions but having basic multiprocess support
is important for allowing development and debugging through the PF using a secondary
diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst
index 028c92c..d8512fa 100644
--- a/doc/guides/nics/sfc_efx.rst
+++ b/doc/guides/nics/sfc_efx.rst
@@ -96,7 +96,7 @@ Non-supported Features
The features not yet supported include:
-- Receive queue interupts
+- Receive queue interrupts
- Priority-based flow control
@@ -209,12 +209,12 @@ Validating flow rules depends on the firmware variant.
The :ref:`flow_isolated_mode` is supported.
-Ethernet destinaton individual/group match
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Ethernet destination individual/group match
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ethernet item supports I/G matching, if only the corresponding bit is set
-in the mask of destination address. If destinaton address in the spec is
-multicast, it matches all multicast (and broadcast) packets, oherwise it
+in the mask of destination address. If destination address in the spec is
+multicast, it matches all multicast (and broadcast) packets, otherwise it
matches unicast packets that are not filtered by other flow rules.
Exceptions to flow rules
@@ -348,10 +348,10 @@ boolean parameters value.
- ``perf_profile`` [auto|throughput|low-latency] (default **throughput**)
- Choose hardware tunning to be optimized for either throughput or
+ Choose hardware tuning to be optimized for either throughput or
low-latency.
**auto** allows NIC firmware to make a choice based on
- installed licences and firmware variant configured using **sfboot**.
+ installed licenses and firmware variant configured using **sfboot**.
- ``stats_update_period_ms`` [long] (default **1000**)
diff --git a/doc/guides/nics/szedata2.rst b/doc/guides/nics/szedata2.rst
index a2092f9..94dba82 100644
--- a/doc/guides/nics/szedata2.rst
+++ b/doc/guides/nics/szedata2.rst
@@ -89,7 +89,7 @@ The NFB cards are multi-port multi-queue cards, where (generally) data from any
Ethernet port may be sent to any queue.
They were historically represented in DPDK as a single port.
-However, the new NFB-200G2QL card employs an addon cable which allows to connect
+However, the new NFB-200G2QL card employs an add-on cable which allows to connect
it to two physical PCI-E slots at the same time (see the diagram below).
This is done to allow 200 Gbps of traffic to be transferred through the PCI-E
bus (note that a single PCI-E 3.0 x16 slot provides only 125 Gbps theoretical
diff --git a/doc/guides/nics/tap.rst b/doc/guides/nics/tap.rst
index 063bd0b..4b6d77d 100644
--- a/doc/guides/nics/tap.rst
+++ b/doc/guides/nics/tap.rst
@@ -40,7 +40,7 @@ actual MAC address: ``00:64:74:61:70:[00-FF]``.
--vdev=net_tap0,mac="00:64:74:61:70:11"
The MAC address will have a user value passed as string. The MAC address is in
-format with delimeter ``:``. The string is byte converted to hex and you get
+format with delimiter ``:``. The string is byte converted to hex and you get
the actual MAC address: ``00:64:74:61:70:11``.
It is possible to specify a remote netdevice to capture packets from by adding
diff --git a/doc/guides/platform/dpaa.rst b/doc/guides/platform/dpaa.rst
index 3904871..6005f22 100644
--- a/doc/guides/platform/dpaa.rst
+++ b/doc/guides/platform/dpaa.rst
@@ -4,7 +4,7 @@
NXP QorIQ DPAA Board Support Package
====================================
-This doc has information about steps to setup QorIq dpaa
+This doc has information about steps to setup QorIQ dpaa
based layerscape platform and information about common offload
hw block drivers of **NXP QorIQ DPAA** SoC family.
@@ -38,7 +38,7 @@ Common Offload HW Block Drivers
Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA PMD on a DPAA
+There are four main pre-requisites for executing DPAA PMD on a DPAA
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/platform/dpaa2.rst b/doc/guides/platform/dpaa2.rst
index 5a64406..2586af0 100644
--- a/doc/guides/platform/dpaa2.rst
+++ b/doc/guides/platform/dpaa2.rst
@@ -4,7 +4,7 @@
NXP QorIQ DPAA2 Board Support Package
=====================================
-This doc has information about steps to setup NXP QoriQ DPAA2 platform
+This doc has information about steps to setup NXP QorIQ DPAA2 platform
and information about common offload hw block drivers of
**NXP QorIQ DPAA2** SoC family.
@@ -48,7 +48,7 @@ Common Offload HW Block Drivers
Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA2 PMD on a DPAA2
+There are four main pre-requisites for executing DPAA2 PMD on a DPAA2
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index 9de1444..658ffd4 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -78,7 +78,7 @@ From the application point of view, each instance of a bbdev device consists of
one or more queues identified by queue IDs. While different devices may have
different capabilities (e.g. support different operation types), all queues on
a device support identical configuration possibilities. A queue is configured
-for only one type of operation and is configured at initializations time.
+for only one type of operation and is configured at initialization time.
When an operation is enqueued to a specific queue ID, the result is dequeued
from the same queue ID.
@@ -678,7 +678,7 @@ bbdev framework, by giving a sample code performing a loop-back operation with a
baseband processor capable of transceiving data packets.
The following sample C-like pseudo-code shows the basic steps to encode several
-buffers using (**sw_trubo**) bbdev PMD.
+buffers using (**sw_turbo**) bbdev PMD.
.. code-block:: c
diff --git a/doc/guides/prog_guide/compressdev.rst b/doc/guides/prog_guide/compressdev.rst
index ad97037..a06c835 100644
--- a/doc/guides/prog_guide/compressdev.rst
+++ b/doc/guides/prog_guide/compressdev.rst
@@ -17,7 +17,7 @@ Device Creation
Physical compression devices are discovered during the bus probe of the EAL function
which is executed at DPDK initialization, based on their unique device identifier.
-For eg. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
+For e.g. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
Specific physical compression devices, like other physical devices in DPDK can be
white-listed or black-listed using the EAL command line options.
@@ -379,7 +379,7 @@ using priv_xform would look like:
setup op->m_src and op->m_dst;
}
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, comp_ops, NUM_OPS);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deque = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, NUM_OPS);
} while (num_dqud < num_enqd);
@@ -526,7 +526,7 @@ An example pseudocode to set up and process a stream having NUM_CHUNKS with each
op->src.length = CHUNK_LEN;
op->input_chksum = 0;
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, &op[i], 1);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deqd = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, 1);
} while (num_deqd < num_enqd);
diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst
index 74a930b..dae40fb 100644
--- a/doc/guides/prog_guide/cryptodev_lib.rst
+++ b/doc/guides/prog_guide/cryptodev_lib.rst
@@ -14,7 +14,7 @@ and AEAD symmetric and asymmetric Crypto operations.
Design Principles
-----------------
-The cryptodev library follows the same basic principles as those used in DPDKs
+The cryptodev library follows the same basic principles as those used in DPDK's
Ethernet Device framework. The Crypto framework provides a generic Crypto device
framework which supports both physical (hardware) and virtual (software) Crypto
devices as well as a generic Crypto API which allows Crypto devices to be
@@ -48,7 +48,7 @@ From the command line using the --vdev EAL option
* If DPDK application requires multiple software crypto PMD devices then required
number of ``--vdev`` with appropriate libraries are to be added.
- * An Application with crypto PMD instaces sharing the same library requires unique ID.
+ * An Application with crypto PMD instances sharing the same library requires unique ID.
Example: ``--vdev 'crypto_aesni_mb0' --vdev 'crypto_aesni_mb1'``
@@ -396,7 +396,7 @@ Operation Management and Allocation
The cryptodev library provides an API set for managing Crypto operations which
utilize the Mempool Library to allocate operation buffers. Therefore, it ensures
-that the crytpo operation is interleaved optimally across the channels and
+that the crypto operation is interleaved optimally across the channels and
ranks for optimal processing.
A ``rte_crypto_op`` contains a field indicating the pool that it originated from.
When calling ``rte_crypto_op_free(op)``, the operation returns to its original pool.
@@ -549,7 +549,7 @@ chain.
union {
struct rte_cryptodev_sym_session *session;
- /**< Handle for the initialised session context */
+ /**< Handle for the initialized session context */
struct rte_crypto_sym_xform *xform;
/**< Session-less API Crypto operation parameters */
};
@@ -602,7 +602,7 @@ Sample code
There are various sample applications that show how to use the cryptodev library,
such as the L2fwd with Crypto sample application (L2fwd-crypto) and
-the IPSec Security Gateway application (ipsec-secgw).
+the IPsec Security Gateway application (ipsec-secgw).
While these applications demonstrate how an application can be created to perform
generic crypto operation, the required complexity hides the basic steps of
@@ -807,7 +807,7 @@ using one of the crypto PMDs available in DPDK.
/*
* Dequeue the crypto operations until all the operations
- * are proccessed in the crypto device.
+ * are processed in the crypto device.
*/
uint16_t num_dequeued_ops, total_num_dequeued_ops = 0;
do {
@@ -886,7 +886,7 @@ the order in which the transforms are passed indicates the order of the chaining
Not all asymmetric crypto xforms are supported for chaining. Currently supported
asymmetric crypto chaining is Diffie-Hellman private key generation followed by
public generation. Also, currently API does not support chaining of symmetric and
-asymmetric crypto xfroms.
+asymmetric crypto xforms.
Each xform defines specific asymmetric crypto algo. Currently supported are:
* RSA
diff --git a/doc/guides/prog_guide/dev_kit_build_system.rst b/doc/guides/prog_guide/dev_kit_build_system.rst
index 96dbf30..74dba4d 100644
--- a/doc/guides/prog_guide/dev_kit_build_system.rst
+++ b/doc/guides/prog_guide/dev_kit_build_system.rst
@@ -204,7 +204,7 @@ Creates the following symbol:
Which ``dpdk-pmdinfogen`` scans for. Using this information other relevant
bits of data can be exported from the object file and used to produce a
hardware support description, that ``dpdk-pmdinfogen`` then encodes into a
-json formatted string in the following format:
+JSON formatted string in the following format:
.. code-block:: c
diff --git a/doc/guides/prog_guide/efd_lib.rst b/doc/guides/prog_guide/efd_lib.rst
index cb1a1df..2b355ff 100644
--- a/doc/guides/prog_guide/efd_lib.rst
+++ b/doc/guides/prog_guide/efd_lib.rst
@@ -423,6 +423,6 @@ References
1- EFD is based on collaborative research work between Intel and
Carnegie Mellon University (CMU), interested readers can refer to the paper
-“Scaling Up Clustered Network Appliances with ScaleBricks;” Dong Zhou et al.
+"Scaling Up Clustered Network Appliances with ScaleBricks" Dong Zhou et al.
at SIGCOMM 2015 (`http://conferences.sigcomm.org/sigcomm/2015/pdf/papers/p241.pdf`)
for more information.
diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index c134636..a8ae214 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -705,7 +705,7 @@ The most important fields in the structure and how they are used are described b
Malloc heap is a doubly-linked list, where each element keeps track of its
previous and next elements. Due to the fact that hugepage memory can come and
-go, neighbouring malloc elements may not necessarily be adjacent in memory.
+go, neighboring malloc elements may not necessarily be adjacent in memory.
Also, since a malloc element may span multiple pages, its contents may not
necessarily be IOVA-contiguous either - each malloc element is only guaranteed
to be virtually contiguous.
diff --git a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
index e955299..c7dda92 100644
--- a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
+++ b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
@@ -162,7 +162,7 @@ The servicing_weight member of struct rte_event_eth_rx_adapter_queue_conf
is applicable when the adapter uses a service core function. The application
has to enable Rx queue interrupts when configuring the ethernet device
using the ``rte_eth_dev_configure()`` function and then use a servicing_weight
-of zero when addding the Rx queue to the adapter.
+of zero when adding the Rx queue to the adapter.
The adapter creates a thread blocked on the interrupt, on an interrupt this
thread enqueues the port id and the queue id to a ring buffer. The adapter
@@ -180,9 +180,9 @@ Rx Callback for SW Rx Adapter
For SW based packet transfers, i.e., when the
``RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT`` is not set in the adapter's
capabilities flags for a particular ethernet device, the service function
-temporarily enqueues mbufs to an event buffer before batch enqueueing these
+temporarily enqueues mbufs to an event buffer before batch enqueuing these
to the event device. If the buffer fills up, the service function stops
-dequeueing packets from the ethernet device. The application may want to
+dequeuing packets from the ethernet device. The application may want to
monitor the buffer fill level and instruct the service function to selectively
enqueue packets to the event device. The application may also use some other
criteria to decide which packets should enter the event device even when
diff --git a/doc/guides/prog_guide/eventdev.rst b/doc/guides/prog_guide/eventdev.rst
index dcdfeb7..7ea14ba 100644
--- a/doc/guides/prog_guide/eventdev.rst
+++ b/doc/guides/prog_guide/eventdev.rst
@@ -42,7 +42,7 @@ The rte_event structure contains the following metadata fields, which the
application fills in to have the event scheduled as required:
* ``flow_id`` - The targeted flow identifier for the enq/deq operation.
-* ``event_type`` - The source of this event, eg RTE_EVENT_TYPE_ETHDEV or CPU.
+* ``event_type`` - The source of this event, e.g. RTE_EVENT_TYPE_ETHDEV or CPU.
* ``sub_event_type`` - Distinguishes events inside the application, that have
the same event_type (see above)
* ``op`` - This field takes one of the RTE_EVENT_OP_* values, and tells the
@@ -265,7 +265,7 @@ Linking Queues and Ports
The final step is to "wire up" the ports to the queues. After this, the
eventdev is capable of scheduling events, and when cores request work to do,
the correct events are provided to that core. Note that the RX core takes input
-from eg: a NIC so it is not linked to any eventdev queues.
+from e.g.: a NIC so it is not linked to any eventdev queues.
Linking all workers to atomic queues, and the TX core to the single-link queue
can be achieved like this:
@@ -276,7 +276,7 @@ can be achieved like this:
uint8_t tx_port_id = 5;
uint8_t atomic_qs[] = {0, 1};
uint8_t single_link_q = 2;
- uin8t_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
+ uint8t_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
for(int worker_port_id = 1; worker_port_id <= 4; worker_port_id++) {
int links_made = rte_event_port_link(dev_id, worker_port_id, atomic_qs, NULL, 2);
diff --git a/doc/guides/prog_guide/flow_classify_lib.rst b/doc/guides/prog_guide/flow_classify_lib.rst
index f0ed5a1..fbb71f5 100644
--- a/doc/guides/prog_guide/flow_classify_lib.rst
+++ b/doc/guides/prog_guide/flow_classify_lib.rst
@@ -94,7 +94,7 @@ The library has the following API's
* Associated actions (list terminated by the END pattern item).
* @param[out] error
* Perform verbose error reporting if not NULL. Structure
- * initialised in case of error only.
+ * initialized in case of error only.
* @return
* 0 on success, error code otherwise
*/
@@ -120,7 +120,7 @@ The library has the following API's
* returns 1 if rule present already, 0 otherwise.
* @param[out] error
* Perform verbose error reporting if not NULL. Structure
- * initialised in case of error only.
+ * initialized in case of error only.
* @return
* A valid handle in case of success, NULL otherwise.
*/
@@ -175,7 +175,7 @@ Classifier creation
The application creates the ``Classifier`` using the
``rte_flow_classifier_create`` API.
-The ``rte_flow_classify_params`` structure must be initialised by the
+The ``rte_flow_classify_params`` structure must be initialized by the
application before calling the API.
.. code-block:: c
@@ -229,7 +229,7 @@ Adding a table to the Classifier
The application adds a table to the ``Classifier`` using the
``rte_flow_classify_table_create`` API.
-The ``rte_flow_classify_table_params`` structure must be initialised by the
+The ``rte_flow_classify_table_params`` structure must be initialized by the
application before calling the API.
.. code-block:: c
@@ -246,7 +246,7 @@ application before calling the API.
};
To create an ACL table the ``rte_table_acl_params`` structure must be
-initialised and assigned to ``arg_create`` in the
+initialized and assigned to ``arg_create`` in the
``rte_flow_classify_table_params`` structure.
.. code-block:: c
@@ -265,7 +265,7 @@ initialised and assigned to ``arg_create`` in the
struct rte_acl_field_def field_format[RTE_ACL_MAX_FIELDS];
};
-The fields for the ACL rule must also be initialised by the application.
+The fields for the ACL rule must also be initialized by the application.
An ACL table can be added to the ``Classifier`` for each ACL rule, for example
another table could be added for the IPv6 5-tuple rule.
diff --git a/doc/guides/prog_guide/ipsec_lib.rst b/doc/guides/prog_guide/ipsec_lib.rst
index 992fdf4..1beb8e7 100644
--- a/doc/guides/prog_guide/ipsec_lib.rst
+++ b/doc/guides/prog_guide/ipsec_lib.rst
@@ -65,7 +65,7 @@ In that mode the library functions perform
- check SQN
- prepare *rte_crypto_op* structure for each input packet
- - verify that integity check and decryption performed by crypto device
+ - verify that integrity check and decryption performed by crypto device
completed successfully
- check padding data
- remove outer IP header (tunnel mode) / update IP header (transport mode)
@@ -88,7 +88,7 @@ In that mode the library functions perform
* for inbound packets:
- - verify that integity check and decryption performed by *rte_security*
+ - verify that integrity check and decryption performed by *rte_security*
device completed successfully
- check SQN
- check padding data
@@ -101,10 +101,10 @@ In that mode the library functions perform
- generate SQN and IV
- add outer IP header (tunnel mode) / update IP header (transport mode)
- add ESP header and trailer, padding and IV data
- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
inline-crypto processing has to be performed by HW on this packet
- invoke *rte_security* device specific *set_pkt_metadata()* to associate
- secuirty device specific data with the packet
+ security device specific data with the packet
RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -113,15 +113,15 @@ In that mode the library functions perform
* for inbound packets:
- - verify that integity check and decryption performed by *rte_security*
+ - verify that integrity check and decryption performed by *rte_security*
device completed successfully
* for outbound packets:
- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
inline-crypto processing has to be performed by HW on this packet
- invoke *rte_security* device specific *set_pkt_metadata()* to associate
- secuirty device specific data with the packet
+ security device specific data with the packet
RTE_SECURITY_ACTION_TYPE_LOOKASIDE_PROTOCOL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -131,7 +131,7 @@ In that mode the library functions perform
* for inbound packets:
- prepare *rte_crypto_op* structure for each input packet
- - verify that integity check and decryption performed by crypto device
+ - verify that integrity check and decryption performed by crypto device
completed successfully
* for outbound packets:
diff --git a/doc/guides/prog_guide/kernel_nic_interface.rst b/doc/guides/prog_guide/kernel_nic_interface.rst
index 7fcbd93..daf87f4 100644
--- a/doc/guides/prog_guide/kernel_nic_interface.rst
+++ b/doc/guides/prog_guide/kernel_nic_interface.rst
@@ -227,7 +227,7 @@ application functions:
``config_promiscusity``:
- Called when the user changes the promiscusity state of the KNI
+ Called when the user changes the promiscuity state of the KNI
interface. For example, when the user runs ``ip link set promisc
[on|off] dev <ifaceX>``. If the user sets this callback function to
NULL, but sets the ``port_id`` field to a value other than -1, a default
diff --git a/doc/guides/prog_guide/metrics_lib.rst b/doc/guides/prog_guide/metrics_lib.rst
index e68e4e7..f2071f2 100644
--- a/doc/guides/prog_guide/metrics_lib.rst
+++ b/doc/guides/prog_guide/metrics_lib.rst
@@ -25,7 +25,7 @@ individual device. Since the metrics library is self-contained, the only
restriction on port numbers is that they are less than ``RTE_MAX_ETHPORTS``
- there is no requirement for the ports to actually exist.
-Initialising the library
+Initializing the library
------------------------
Before the library can be used, it has to be initialized by calling
@@ -169,13 +169,13 @@ following names:
- ``peak_bits_in``: Peak inbound bit-rate
- ``peak_bits_out``: Peak outbound bit-rate
-Once initialised and clocked at the appropriate frequency, these
+Once initialized and clocked at the appropriate frequency, these
statistics can be obtained by querying the metrics library.
Initialization
~~~~~~~~~~~~~~
-Before the library can be used, it has to be initialised by calling
+Before the library can be used, it has to be initialized by calling
``rte_stats_bitrate_create()``, which will return a bit-rate
calculation object. Since the bit-rate library uses the metrics library
to report the calculated statistics, the bit-rate library then needs to
@@ -233,13 +233,13 @@ via the metrics library using the following names:
- ``mac_latency_ns``: Maximum processing latency (nano-seconds)
- ``jitter_ns``: Variance in processing latency (nano-seconds)
-Once initialised and clocked at the appropriate frequency, these
+Once initialized and clocked at the appropriate frequency, these
statistics can be obtained by querying the metrics library.
Initialization
~~~~~~~~~~~~~~
-Before the library can be used, it has to be initialised by calling
+Before the library can be used, it has to be initialized by calling
``rte_latencystats_init()``.
.. code-block:: c
@@ -266,7 +266,7 @@ Library shutdown
~~~~~~~~~~~~~~~~
When finished, ``rte_latencystats_uninit()`` needs to be called to
-de-initialise the latency library.
+de-initialize the latency library.
.. code-block:: c
diff --git a/doc/guides/prog_guide/multi_proc_support.rst b/doc/guides/prog_guide/multi_proc_support.rst
index 1384fe3..6196d3f 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -273,7 +273,7 @@ will be populated by IPC are as follows:
those peer processes that were active at the time of request, how many have
replied)
* ``msgs`` - pointer to where all of the responses are stored. The order in
- which responses appear is undefined. Whendoing sycnrhonous requests, this
+ which responses appear is undefined. When doing synchronous requests, this
memory must be freed by the requestor after request completes!
For asynchronous requests, a function pointer to the callback function must be
diff --git a/doc/guides/prog_guide/profile_app.rst b/doc/guides/prog_guide/profile_app.rst
index 5af795c..a36ebef 100644
--- a/doc/guides/prog_guide/profile_app.rst
+++ b/doc/guides/prog_guide/profile_app.rst
@@ -64,7 +64,7 @@ The default ``cntvct_el0`` based ``rte_rdtsc()`` provides a portable means to
get a wall clock counter in user space. Typically it runs at <= 100MHz.
The alternative method to enable ``rte_rdtsc()`` for a high resolution wall
-clock counter is through the armv8 PMU subsystem. The PMU cycle counter runs
+clock counter is through the ARMv8 PMU subsystem. The PMU cycle counter runs
at CPU frequency. However, access to the PMU cycle counter from user space is
not enabled by default in the arm64 linux kernel. It is possible to enable
cycle counter for user space access by configuring the PMU from the privileged
@@ -75,7 +75,7 @@ scheme. Application can choose the PMU based implementation with
``CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU``.
The example below shows the steps to configure the PMU based cycle counter on
-an armv8 machine.
+an ARMv8 machine.
.. code-block:: console
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 0203f4f..1aec578 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2129,7 +2129,7 @@ as defined in the ``rte_flow_action_raw_decap``
This action modifies the payload of matched flows. The data supplied must
be a valid header, either holding layer 2 data in case of removing layer 2
-before eincapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
+before encapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
tunnel definition starting from layer 2 and moving to the tunnel item itself.
When applied to the original packet the resulting packet must be a
valid packet.
@@ -2279,7 +2279,7 @@ Action: ``DEC_TTL``
Decrease TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_dec_ttl:
@@ -2297,7 +2297,7 @@ Action: ``SET_TTL``
Assigns a new TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_set_ttl:
diff --git a/doc/guides/prog_guide/rte_security.rst b/doc/guides/prog_guide/rte_security.rst
index cb70caa..7d0734a 100644
--- a/doc/guides/prog_guide/rte_security.rst
+++ b/doc/guides/prog_guide/rte_security.rst
@@ -40,7 +40,7 @@ Inline Crypto
~~~~~~~~~~~~~
RTE_SECURITY_ACTION_TYPE_INLINE_CRYPTO:
-The crypto processing for security protocol (e.g. IPSec) is processed
+The crypto processing for security protocol (e.g. IPsec) is processed
inline during receive and transmission on NIC port. The flow based
security action should be configured on the port.
@@ -48,7 +48,7 @@ Ingress Data path - The packet is decrypted in RX path and relevant
crypto status is set in Rx descriptors. After the successful inline
crypto processing the packet is presented to host as a regular Rx packet
however all security protocol related headers are still attached to the
-packet. e.g. In case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. In case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will remain in the packet but the received packet
contains the decrypted data where the encrypted data was when the packet
arrived. The driver Rx path check the descriptors and and based on the
@@ -111,7 +111,7 @@ Inline protocol offload
~~~~~~~~~~~~~~~~~~~~~~~
RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL:
-The crypto and protocol processing for security protocol (e.g. IPSec)
+The crypto and protocol processing for security protocol (e.g. IPsec)
is processed inline during receive and transmission. The flow based
security action should be configured on the port.
@@ -119,7 +119,7 @@ Ingress Data path - The packet is decrypted in the RX path and relevant
crypto status is set in the Rx descriptors. After the successful inline
crypto processing the packet is presented to the host as a regular Rx packet
but all security protocol related headers are optionally removed from the
-packet. e.g. in the case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. in the case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will be removed from the packet and the received packet
will contains the decrypted packet only. The driver Rx path checks the
descriptors and based on the crypto status sets additional flags in
@@ -132,7 +132,7 @@ to identify the security processing done on the packet.
The underlying device in this case is stateful. It is expected that
the device shall support crypto processing for all kind of packets matching
to a given flow, this includes fragmented packets (post reassembly).
- E.g. in case of IPSec the device may internally manage anti-replay etc.
+ E.g. in case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in the descriptor.
@@ -150,7 +150,7 @@ to cross the MTU size.
.. note::
The underlying device will manage state information required for egress
- processing. E.g. in case of IPSec, the seq number will be added to the
+ processing. E.g. in case of IPsec, the seq number will be added to the
packet, however the device shall provide indication when the sequence number
is about to overflow. The underlying device may support post encryption TSO.
@@ -199,13 +199,13 @@ crypto device.
Decryption: The packet is sent to the crypto device for security
protocol processing. The device will decrypt the packet and it will also
optionally remove additional security headers from the packet.
-E.g. in case of IPSec, IPSec tunnel headers (if any), ESP/AH headers
+E.g. in case of IPsec, IPsec tunnel headers (if any), ESP/AH headers
will be removed from the packet and the decrypted packet may contain
plain data only.
.. note::
- In case of IPSec the device may internally manage anti-replay etc.
+ In case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in descriptor.
@@ -217,7 +217,7 @@ for any protocol header addition.
.. note::
- In the case of IPSec, the seq number will be added to the packet,
+ In the case of IPsec, the seq number will be added to the packet,
It shall provide an indication when the sequence number is about to
overflow.
@@ -549,7 +549,7 @@ IPsec related configuration parameters are defined in ``rte_security_ipsec_xform
struct rte_security_ipsec_sa_options options;
/**< various SA options */
enum rte_security_ipsec_sa_direction direction;
- /**< IPSec SA Direction - Egress/Ingress */
+ /**< IPsec SA Direction - Egress/Ingress */
enum rte_security_ipsec_sa_protocol proto;
/**< IPsec SA Protocol - AH/ESP */
enum rte_security_ipsec_sa_mode mode;
diff --git a/doc/guides/prog_guide/traffic_management.rst b/doc/guides/prog_guide/traffic_management.rst
index 98ac431..05b34d9 100644
--- a/doc/guides/prog_guide/traffic_management.rst
+++ b/doc/guides/prog_guide/traffic_management.rst
@@ -39,7 +39,7 @@ whether a specific implementation does meet the needs to the user application.
At the TM level, users can get high level idea with the help of various
parameters such as maximum number of nodes, maximum number of hierarchical
levels, maximum number of shapers, maximum number of private shapers, type of
-scheduling algorithm (Strict Priority, Weighted Fair Queueing , etc.), etc.,
+scheduling algorithm (Strict Priority, Weighted Fair Queuing , etc.), etc.,
supported by the implementation.
Likewise, users can query the capability of the TM at the hierarchical level to
diff --git a/doc/guides/prog_guide/vhost_lib.rst b/doc/guides/prog_guide/vhost_lib.rst
index a86c07a..fc3ee43 100644
--- a/doc/guides/prog_guide/vhost_lib.rst
+++ b/doc/guides/prog_guide/vhost_lib.rst
@@ -63,7 +63,7 @@ The following is an overview of some key Vhost API functions:
512).
* zero copy is really good for VM2VM case. For iperf between two VMs, the
- boost could be above 70% (when TSO is enableld).
+ boost could be above 70% (when TSO is enabled).
* For zero copy in VM2NIC case, guest Tx used vring may be starved if the
PMD driver consume the mbuf but not release them timely.
diff --git a/doc/guides/rawdevs/ifpga_rawdev.rst b/doc/guides/rawdevs/ifpga_rawdev.rst
index d400db6..a3d92a6 100644
--- a/doc/guides/rawdevs/ifpga_rawdev.rst
+++ b/doc/guides/rawdevs/ifpga_rawdev.rst
@@ -91,7 +91,7 @@ Run-time parameters
-------------------
This driver is invoked automatically in systems added with Intel FPGA,
-but PR and IFPGA Bus scan is trigged by command line using
+but PR and IFPGA Bus scan is triggered by command line using
``--vdev 'ifpga_rawdev_cfg`` EAL option.
The following device parameters are supported:
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 358dfa3..276327c 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -676,7 +676,7 @@ igb uio legacy mode can not be used in X710/XL710/XXV710
**Description**:
X710/XL710/XXV710 NICs lack support for indicating INTx is asserted via the interrupt
- bit in the PCI status register. Linux delected them from INTx support table. The related
+ bit in the PCI status register. Linux deleted them from INTx support table. The related
`commit <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/pci/quirks.c?id=8bcf4525c5d43306c5fd07e132bc8650e3491aec>`_.
**Implication**:
@@ -722,9 +722,9 @@ Linux kernel 4.10.0 iommu attribute read error
**Description**:
When VT-d is enabled (``iommu=pt intel_iommu=on``), reading IOMMU attributes from
/sys/devices/virtual/iommu/dmarXXX/intel-iommu/cap on Linux kernel 4.10.0 error.
- This bug is fixed in `Linux commmit a7fdb6e648fb
+ This bug is fixed in `Linux commit a7fdb6e648fb
<https://patchwork.kernel.org/patch/9595727/>`_,
- This bug is introduced in `Linux commmit 39ab9555c241
+ This bug is introduced in `Linux commit 39ab9555c241
<https://patchwork.kernel.org/patch/9554403/>`_,
**Implication**:
@@ -842,7 +842,7 @@ AVX-512 support disabled
drop.
On DPDK v19.02 ``AVX-512`` disable scope is reduced to ``GCC`` and ``binutils version 2.30`` based
- on information accured from the GCC community defect.
+ on information accrued from the GCC community defect.
**Reason**:
Generated ``AVX-512`` code cause crash:
diff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/release_17_11.rst
index 2a93af3..6448b6c 100644
--- a/doc/guides/rel_notes/release_17_11.rst
+++ b/doc/guides/rel_notes/release_17_11.rst
@@ -168,7 +168,7 @@ New Features
* The DES CBC algorithm.
* The DES DOCSIS BPI algorithm.
- This change requires version 0.47 of the IPSec Multi-buffer library. For
+ This change requires version 0.47 of the IPsec Multi-buffer library. For
more details see the :doc:`../cryptodevs/aesni_mb` documentation.
* **Updated the OpenSSL PMD.**
@@ -198,7 +198,7 @@ New Features
* **Added the Security Offload Library.**
Added an experimental library - ``rte_security``. This provide security APIs
- for protocols like IPSec using inline ipsec offload to ethernet devices or
+ for protocols like IPsec using inline ipsec offload to ethernet devices or
full protocol offload with lookaside crypto devices.
See the :doc:`../prog_guide/rte_security` section of the DPDK Programmers
@@ -207,11 +207,11 @@ New Features
* **Updated the DPAA2_SEC crypto driver to support rte_security.**
Updated the ``dpaa2_sec`` crypto PMD to support ``rte_security`` lookaside
- protocol offload for IPSec.
+ protocol offload for IPsec.
* **Updated the IXGBE ethernet driver to support rte_security.**
- Updated ixgbe ethernet PMD to support ``rte_security`` inline IPSec offload.
+ Updated ixgbe ethernet PMD to support ``rte_security`` inline IPsec offload.
* **Updated i40e driver to support GTP-C/GTP-U.**
@@ -509,7 +509,7 @@ ABI Changes
* **New parameter added to rte_eth_dev.**
A new parameter ``security_ctx`` has been added to ``rte_eth_dev`` to
- support security operations like IPSec inline.
+ support security operations like IPsec inline.
* **New parameter added to rte_cryptodev.**
diff --git a/doc/guides/sample_app_ug/bbdev_app.rst b/doc/guides/sample_app_ug/bbdev_app.rst
index 40a3264..405e706 100644
--- a/doc/guides/sample_app_ug/bbdev_app.rst
+++ b/doc/guides/sample_app_ug/bbdev_app.rst
@@ -68,7 +68,7 @@ The application accepts a number of command line options:
where:
-* ``e ENCODING_CORES``: hexmask for encoding lcored (default = 0x2)
+* ``e ENCODING_CORES``: hexmask for encoding lcores (default = 0x2)
* ``d DECODING_CORES``: hexmask for decoding lcores (default = 0x4)
* ``p ETH_PORT_ID``: ethernet port ID (default = 0)
* ``b BBDEV_ID``: BBDev ID (default = 0)
@@ -87,7 +87,7 @@ issue the command:
$ ./build/bbdev --vdev='baseband_turbo_sw' -w <NIC0PCIADDR> -c 0x38 --socket-mem=2,2 \
--file-prefix=bbdev -- -e 0x10 -d 0x20
-where, NIC0PCIADDR is the PCI addresse of the Rx port
+where, NIC0PCIADDR is the PCI address of the Rx port
This command creates one virtual bbdev devices ``baseband_turbo_sw`` where the
device gets linked to a corresponding ethernet port as whitelisted by
diff --git a/doc/guides/sample_app_ug/eventdev_pipeline.rst b/doc/guides/sample_app_ug/eventdev_pipeline.rst
index 0ec0290..dc7972a 100644
--- a/doc/guides/sample_app_ug/eventdev_pipeline.rst
+++ b/doc/guides/sample_app_ug/eventdev_pipeline.rst
@@ -49,7 +49,7 @@ these settings is shown below:
./build/eventdev_pipeline --vdev event_sw0 -- -r1 -t1 -e4 -w FF00 -s4 -n0 -c32 -W1000 -D
The application has some sanity checking built-in, so if there is a function
-(eg; the RX core) which doesn't have a cpu core mask assigned, the application
+(e.g.; the RX core) which doesn't have a cpu core mask assigned, the application
will print an error message:
.. code-block:: console
diff --git a/doc/guides/sample_app_ug/flow_classify.rst b/doc/guides/sample_app_ug/flow_classify.rst
index a6383b3..1c765a5 100644
--- a/doc/guides/sample_app_ug/flow_classify.rst
+++ b/doc/guides/sample_app_ug/flow_classify.rst
@@ -64,7 +64,7 @@ ACL field definitions for the IPv4 5 tuple rule
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The following field definitions are used when creating the ACL table during
-initialisation of the ``Flow Classify`` application..
+initialization of the ``Flow Classify`` application..
.. code-block:: c
@@ -222,13 +222,13 @@ table`` to the flow classifier.
rte_exit(EXIT_FAILURE, "Cannot create classifier\n");
}
- /* initialise ACL table params */
+ /* initialize ACL table params */
table_acl_params.name = "table_acl_ipv4_5tuple";
table_acl_params.n_rule_fields = RTE_DIM(ipv4_defs);
table_acl_params.n_rules = FLOW_CLASSIFY_MAX_RULE_NUM;
memcpy(table_acl_params.field_format, ipv4_defs, sizeof(ipv4_defs));
- /* initialise table create params */
+ /* initialize table create params */
cls_table_params.ops = &rte_table_acl_ops,
cls_table_params.arg_create = &table_acl_params,
cls_table_params.type = RTE_FLOW_CLASSIFY_TABLE_ACL_IP4_5TUPLE;
@@ -240,7 +240,7 @@ table`` to the flow classifier.
rte_exit(EXIT_FAILURE, "Failed to create classifier table\n");
}
-It then reads the ipv4_rules_file.txt file and initialises the parameters for
+It then reads the ipv4_rules_file.txt file and initializes the parameters for
the ``rte_flow_classify_table_entry_add`` API.
This API adds a rule to the ACL table.
diff --git a/doc/guides/sample_app_ug/intro.rst b/doc/guides/sample_app_ug/intro.rst
index 159bcf7..9070419 100644
--- a/doc/guides/sample_app_ug/intro.rst
+++ b/doc/guides/sample_app_ug/intro.rst
@@ -106,7 +106,7 @@ examples are highlighted below.
(packet arrival) and TX (packet transmission) by adding callbacks to the RX
and TX packet processing functions.
-* :doc:`IPSec Security Gateway<ipsec_secgw>`: The IPSec Security
+* :doc:`IPsec Security Gateway<ipsec_secgw>`: The IPsec Security
Gateway application is minimal example of something closer to a real world
example. This is also a good example of an application using the DPDK
Cryptodev framework.
diff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst
index 447a544..d7a05b7 100644
--- a/doc/guides/sample_app_ug/ip_pipeline.rst
+++ b/doc/guides/sample_app_ug/ip_pipeline.rst
@@ -113,7 +113,7 @@ Application stages
Initialization
~~~~~~~~~~~~~~
-During this stage, EAL layer is initialised and application specific arguments are parsed. Furthermore, the data strcutures
+During this stage, EAL layer is initialized and application specific arguments are parsed. Furthermore, the data structures
(i.e. linked lists) for application objects are initialized. In case of any initialization error, an error message
is displayed and the application is terminated.
@@ -185,7 +185,7 @@ Examples
+-----------------------+----------------------+----------------+------------------------------------+
| IP routing | LPM (IPv4) | Forward | 1. Mempool Create |
| | | | 2. Link create |
- | | * Key = IP dest addr | | 3. Pipeline creat |
+ | | * Key = IP dest addr | | 3. Pipeline create |
| | * Offset = 286 | | 4. Pipeline port in/out |
| | * Table size = 4K | | 5. Pipeline table |
| | | | 6. Pipeline port in table |
diff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_app_ug/ipsec_secgw.rst
index 3d784e7..ac118c1 100644
--- a/doc/guides/sample_app_ug/ipsec_secgw.rst
+++ b/doc/guides/sample_app_ug/ipsec_secgw.rst
@@ -25,8 +25,8 @@ The application classifies the ports as *Protected* and *Unprotected*.
Thus, traffic received on an Unprotected or Protected port is consider
Inbound or Outbound respectively.
-The application also supports complete IPSec protocol offload to hardware
-(Look aside crypto accelarator or using ethernet device). It also support
+The application also supports complete IPsec protocol offload to hardware
+(Look aside crypto accelerator or using ethernet device). It also support
inline ipsec processing by the supported ethernet device during transmission.
These modes can be selected during the SA creation configuration.
@@ -124,7 +124,7 @@ Where:
* ``-e``: enables Security Association extended sequence number processing
(available only with librte_ipsec code path).
-* ``-a``: enables Security Association sequence number atomic behaviour
+* ``-a``: enables Security Association sequence number atomic behavior
(available only with librte_ipsec code path).
* ``--config (port,queue,lcore)[,(port,queue,lcore)]``: determines which queues
@@ -752,7 +752,7 @@ DUT OS(NIC1)--(IPsec)-->(NIC1)ipsec-secgw(TAP)--(plain)-->(TAP)SUT OS
SUT OS(TAP)--(plain)-->(TAP)psec-secgw(NIC1)--(IPsec)-->(NIC1)DUT OS
-It then tries to perform some data transfer using the scheme decribed above.
+It then tries to perform some data transfer using the scheme described above.
usage
~~~~~
diff --git a/doc/guides/sample_app_ug/performance_thread.rst b/doc/guides/sample_app_ug/performance_thread.rst
index e2c04ef..ac6ee8a 100644
--- a/doc/guides/sample_app_ug/performance_thread.rst
+++ b/doc/guides/sample_app_ug/performance_thread.rst
@@ -500,8 +500,8 @@ An application may save and retrieve a single pointer to application data in
the L-thread struct.
For legacy and backward compatibility reasons two alternative methods are also
-offered, the first is modelled directly on the pthread get/set specific APIs,
-the second approach is modelled on the ``RTE_PER_LCORE`` macros, whereby
+offered, the first is modeled directly on the pthread get/set specific APIs,
+the second approach is modeled on the ``RTE_PER_LCORE`` macros, whereby
``PER_LTHREAD`` macros are introduced, in both cases the storage is local to
the L-thread.
diff --git a/doc/guides/sample_app_ug/qos_metering.rst b/doc/guides/sample_app_ug/qos_metering.rst
index 2e8e017..d75f7da 100644
--- a/doc/guides/sample_app_ug/qos_metering.rst
+++ b/doc/guides/sample_app_ug/qos_metering.rst
@@ -151,5 +151,5 @@ In this particular case:
* For the rest of the cases, the color is changed to red.
.. note::
- * In color blind mode, first row GREEN colour is only valid.
+ * In color blind mode, first row GREEN color is only valid.
* To drop the packet, policer_table action has to be set to DROP.
diff --git a/doc/guides/sample_app_ug/test_pipeline.rst b/doc/guides/sample_app_ug/test_pipeline.rst
index 5f313c5..5aefd8d 100644
--- a/doc/guides/sample_app_ug/test_pipeline.rst
+++ b/doc/guides/sample_app_ug/test_pipeline.rst
@@ -32,7 +32,7 @@ Compiling the Application
-------------------------
To compile the sample application see :doc:`compiling`
-The application is located in the ``$RTE_SDK/app/test-pipline`` directory.
+The application is located in the ``$RTE_SDK/app/test-pipeline`` directory.
Running the Application
diff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst
index df4d6f9..a71ada6 100644
--- a/doc/guides/sample_app_ug/vhost.rst
+++ b/doc/guides/sample_app_ug/vhost.rst
@@ -116,7 +116,7 @@ will create it. Put simply, it's the server to create the socket file.
The vm2vm parameter sets the mode of packet switching between guests in
the host.
-- 0 disables vm2vm, impling that VM's packets will always go to the NIC port.
+- 0 disables vm2vm, implying that VM's packets will always go to the NIC port.
- 1 means a normal mac lookup packet routing.
- 2 means hardware mode packet forwarding between guests, it allows packets
go to the NIC port, hardware L2 switch will determine which guest the
@@ -148,7 +148,7 @@ default value is 15.
**--dequeue-zero-copy**
Dequeue zero copy will be enabled when this option is given. it is worth to
-note that if NIC is binded to driver with iommu enabled, dequeue zero copy
+note that if NIC is bound to driver with iommu enabled, dequeue zero copy
cannot work at VM2NIC mode (vm2vm=0) due to currently we don't setup iommu
dma mapping for guest memory.
diff --git a/doc/guides/sample_app_ug/vhost_scsi.rst b/doc/guides/sample_app_ug/vhost_scsi.rst
index 7ab7d0d..6b9bf62 100644
--- a/doc/guides/sample_app_ug/vhost_scsi.rst
+++ b/doc/guides/sample_app_ug/vhost_scsi.rst
@@ -63,7 +63,7 @@ Vhost_scsi Common Issues
* vhost_scsi can not start with block size 512 Bytes:
- Currently DPDK vhost library was designed for NET device(althrough the APIs
+ Currently DPDK vhost library was designed for NET device(although the APIs
are generic now), for 512 Bytes block device, Qemu BIOS(x86 BIOS Enhanced
Disk Device) will enumerate all block device and do some IOs to those block
devices with 512 Bytes sector size. DPDK vhost library can not process such
diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst
index 14d432e..7d73de3 100644
--- a/doc/guides/sample_app_ug/vm_power_management.rst
+++ b/doc/guides/sample_app_ug/vm_power_management.rst
@@ -53,8 +53,8 @@ The solution is comprised of two high-level components:
application below for more information on setting the policy values.
- Out-of-band monitoring of workloads via cores hardware event counters:
- The host application can manage power for an application in a virtualised
- OR non-virtualised environment by looking at the event counters of the
+ The host application can manage power for an application in a virtualized
+ OR non-virtualized environment by looking at the event counters of the
cores and taking action based on the branch hit/miss ratio. See the host
application '--core-list' command line parameter below.
@@ -344,7 +344,7 @@ monitoring of branch ratio on cores doing busy polling via PMDs.
When this parameter is used, the list of cores specified will monitor the ratio
between branch hits and branch misses. A tightly polling PMD thread will have a
- very low branch ratio, so the core frequency will be scaled down to the minimim
+ very low branch ratio, so the core frequency will be scaled down to the minimum
allowed value. When packets are received, the code path will alter, causing the
branch ratio to increase. When the ratio goes above the ratio threshold, the
core frequency will be scaled up to the maximum allowed value.
@@ -384,7 +384,7 @@ the file.
The fifo is at /tmp/powermonitor/fifo
-The jason string can be a policy or instruction, and takes the following
+The JSON string can be a policy or instruction, and takes the following
format:
.. code-block:: javascript
@@ -734,7 +734,7 @@ policy down to the host application. These parameters are as follows:
A comma-separated list of cores in the VM that the user wants the host application to
monitor. The list of cores in any vm starts at zero, and these are mapped to the
physical cores by the host application once the policy is passed down.
- Valid syntax includes individial cores '2,3,4', or a range of cores '2-4', or a
+ Valid syntax includes individual cores '2,3,4', or a range of cores '2-4', or a
combination of both '1,3,5-7'
.. code-block:: console
@@ -742,7 +742,7 @@ policy down to the host application. These parameters are as follows:
--busy-hours {list of busy hours}
A comma-separated list of hours within which to set the core frequency to maximum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console
@@ -750,7 +750,7 @@ policy down to the host application. These parameters are as follows:
--quiet-hours {list of quiet hours}
A comma-separated list of hours within which to set the core frequency to minimum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console
diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
index b717b8c..eb632e2 100644
--- a/doc/guides/testpmd_app_ug/run_app.rst
+++ b/doc/guides/testpmd_app_ug/run_app.rst
@@ -369,7 +369,7 @@ The commandline options are:
* ``--hot-plug``
- Enable device event monitor machenism for hotplug.
+ Enable device event monitor mechanism for hotplug.
* ``--vxlan-gpe-port=N``
@@ -409,21 +409,21 @@ The commandline options are:
* ``--noisy-lkup-memory=N``
- Set the size of the noisy neighbour simulation memory buffer in MB to N.
+ Set the size of the noisy neighbor simulation memory buffer in MB to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-reads=N``
- Set the number of reads to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of reads to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-writes=N``
- Set the number of writes to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of writes to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-reads-writes=N``
- Set the number of r/w accesses to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of r/w accesses to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index 06c8b2a..8eb39cd 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -302,7 +302,7 @@ The available information categories are:
This is the default mode.
* ``mac``: Changes the source and the destination Ethernet addresses of packets before forwarding them.
- Default application behaviour is to set source Ethernet address to that of the transmitting interface, and destination
+ Default application behavior is to set source Ethernet address to that of the transmitting interface, and destination
address to a dummy value (set during init). The user may specify a target destination Ethernet address via the 'eth-peer' or
'eth-peers-configfile' command-line options. It is not currently possible to specify a specific source Ethernet address.
@@ -323,9 +323,9 @@ The available information categories are:
* ``ieee1588``: Demonstrate L2 IEEE1588 V2 PTP timestamping for RX and TX. Requires ``CONFIG_RTE_LIBRTE_IEEE1588=y``.
* ``softnic``: Demonstrates the softnic forwarding operation. In this mode, packet forwarding is
- similar to I/O mode except for the fact that packets are loopback to the softnic ports only. Therefore, portmask parameter should be set to softnic port only. The various software based custom NIC pipelines specified through the softnic firmware (DPDK packet framework script) can be tested in this mode. Furthermore, it allows to build 5-level hierarchical QoS scheduler as a default option that can be enabled through CLI once testpmd application is initialised. The user can modify the default scheduler hierarchy or can specify the new QoS Scheduler hierarchy through CLI. Requires ``CONFIG_RTE_LIBRTE_PMD_SOFTNIC=y``.
+ similar to I/O mode except for the fact that packets are loopback to the softnic ports only. Therefore, portmask parameter should be set to softnic port only. The various software based custom NIC pipelines specified through the softnic firmware (DPDK packet framework script) can be tested in this mode. Furthermore, it allows to build 5-level hierarchical QoS scheduler as a default option that can be enabled through CLI once testpmd application is initialized. The user can modify the default scheduler hierarchy or can specify the new QoS Scheduler hierarchy through CLI. Requires ``CONFIG_RTE_LIBRTE_PMD_SOFTNIC=y``.
-* ``noisy``: Noisy neighbour simulation.
+* ``noisy``: Noisy neighbor simulation.
Simulate more realistic behavior of a guest machine engaged in receiving
and sending packets performing Virtual Network Function (VNF).
@@ -2286,7 +2286,7 @@ set bonding lacp dedicated_queue
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enable dedicated tx/rx queues on bonding devices slaves to handle LACP control plane traffic
-when in mode 4 (link-aggregration-802.3ad)::
+when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding lacp dedicated_queues (port_id) (enable|disable)
@@ -2294,7 +2294,7 @@ when in mode 4 (link-aggregration-802.3ad)::
set bonding agg_mode
~~~~~~~~~~~~~~~~~~~~
-Enable one of the specific aggregators mode when in mode 4 (link-aggregration-802.3ad)::
+Enable one of the specific aggregators mode when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding agg_mode (port_id) (bandwidth|count|stable)
@@ -2688,8 +2688,8 @@ where:
* ``shared_shaper_id``: Shared shaper ID to be deleted.
-Set port traffic management hiearchy node private shaper
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Set port traffic management hierarchy node private shaper
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
set the port traffic management hierarchy node private shaper::
@@ -2740,7 +2740,7 @@ Delete the WRED profile::
Add port traffic management hierarchy nonleaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add nonleaf node to port traffic management hiearchy::
+Add nonleaf node to port traffic management hierarchy::
testpmd> add port tm nonleaf node (port_id) (node_id) (parent_node_id) \
(priority) (weight) (level_id) (shaper_profile_id) \
@@ -2755,7 +2755,7 @@ where:
* ``weight``: Node weight (lowest weight is one). The node weight is relative
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
* ``n_sp_priorities``: Number of strict priorities.
@@ -2766,7 +2766,7 @@ where:
Add port traffic management hierarchy leaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add leaf node to port traffic management hiearchy::
+Add leaf node to port traffic management hierarchy::
testpmd> add port tm leaf node (port_id) (node_id) (parent_node_id) \
(priority) (weight) (level_id) (shaper_profile_id) \
@@ -2781,7 +2781,7 @@ where:
* ``weight``: Node weight (lowest weight is one). The node weight is relative
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
* ``cman_mode``: Congestion management mode to be enabled for this node.
@@ -2793,7 +2793,7 @@ where:
Delete port traffic management hierarchy node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Delete node from port traffic management hiearchy::
+Delete node from port traffic management hierarchy::
testpmd> del port tm node (port_id) (node_id)
@@ -3986,7 +3986,7 @@ This section lists supported actions and their attributes, if any.
- ``dec_ttl``: Performs a decrease TTL value action
-- ``set_ttl``: Set TTL value with specificed value
+- ``set_ttl``: Set TTL value with specified value
- ``ttl_value {unsigned}``: The new TTL value to be set
- ``set_mac_src``: set source MAC address
@@ -4519,7 +4519,7 @@ The following sections show functions to load/unload eBPF based filters.
bpf-load
~~~~~~~~
-Load an eBPF program as a callback for partciular RX/TX queue::
+Load an eBPF program as a callback for particular RX/TX queue::
testpmd> bpf-load rx|tx (portid) (queueid) (load-flags) (bpf-prog-filename)
@@ -4557,7 +4557,7 @@ To load (not JITed) t1.o at TX queue 0, port 0::
bpf-unload
~~~~~~~~~~
-Unload previously loaded eBPF program for partciular RX/TX queue::
+Unload previously loaded eBPF program for particular RX/TX queue::
testpmd> bpf-unload rx|tx (portid) (queueid)
diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst
index c366af4..2fc6544 100644
--- a/doc/guides/tools/cryptoperf.rst
+++ b/doc/guides/tools/cryptoperf.rst
@@ -59,7 +59,7 @@ To set on the linearization options add below definition to the
**Step 3: Build the application**
Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the
-``dpdk-test-crypto-perf`` applcation.
+``dpdk-test-crypto-perf`` application.
Initially, the user must select a DPDK target to choose the correct target type
and compiler options to use when building the libraries.
@@ -80,7 +80,7 @@ EAL Options
~~~~~~~~~~~
The following are the EAL command-line options that can be used in conjunction
-with the ``dpdk-test-crypto-perf`` applcation.
+with the ``dpdk-test-crypto-perf`` application.
See the DPDK Getting Started Guides for more information on these options.
* ``-c <COREMASK>`` or ``-l <CORELIST>``
@@ -96,10 +96,10 @@ See the DPDK Getting Started Guides for more information on these options.
Add a virtual device.
-Appication Options
-~~~~~~~~~~~~~~~~~~
+Application Options
+~~~~~~~~~~~~~~~~~~~
-The following are the appication command-line options:
+The following are the application command-line options:
* ``--ptest type``
@@ -338,13 +338,13 @@ Test Vector File
The test vector file is a text file contain information about test vectors.
The file is made of the sections. The first section doesn't have header.
It contain global information used in each test variant vectors -
-typically information about plaintext, ciphertext, cipher key, aut key,
+typically information about plaintext, ciphertext, cipher key, auth key,
initial vector. All other sections begin header.
The sections contain particular information typically digest.
**Format of the file:**
-Each line beginig with sign '#' contain comment and it is ignored by parser::
+Each line beginning with sign '#' contain comment and it is ignored by parser::
# <comment>
@@ -352,16 +352,16 @@ Header line is just name in square bracket::
[<section name>]
-Data line contain information tocken then sign '=' and
+Data line contain information token then sign '=' and
a string of bytes in C byte array format::
- <tocken> = <C byte array>
+ <token> = <C byte array>
-**Tockens list:**
+**Tokens list:**
* ``plaintext``
- Original plaintext to be crypted.
+ Original plaintext to be encrypted.
* ``ciphertext``
diff --git a/doc/guides/tools/proc_info.rst b/doc/guides/tools/proc_info.rst
index 6bdf5a8..2ea1b59 100644
--- a/doc/guides/tools/proc_info.rst
+++ b/doc/guides/tools/proc_info.rst
@@ -44,7 +44,7 @@ If no port mask is specified xstats are reset for all DPDK ports.
**-m**: Print DPDK memory information.
**--show-port**
-The show-port parameter displays port level various configuration informationi
+The show-port parameter displays port level various configuration information
associated to RX port queue pair.
**--show-tm**
@@ -56,7 +56,7 @@ The show-crypto parameter displays available cryptodev configurations,
settings and stats per node.
**--show-ring[=name]**
-The show-ring pararmeter display current allocation of all ring with
+The show-ring parameter display current allocation of all ring with
debug information. Specifying the name allows to display details for specific
ring. For invalid or no ring name, whole list is dump.
@@ -76,7 +76,7 @@ Limitations
* When running ``dpdk-procinfo`` with shared library mode, it is required to
pass the same NIC PMD libraries as used for the primary application. Any
- mismatch in PMD library arguments can lead to undefined behaviour and results
+ mismatch in PMD library arguments can lead to undefined behavior and results
affecting primary application too.
* Stats retrieval using ``dpdk-procinfo`` is not supported for virtual devices like PCAP and TAP.
diff --git a/doc/guides/tools/testbbdev.rst b/doc/guides/tools/testbbdev.rst
index f338647..0001a0d 100644
--- a/doc/guides/tools/testbbdev.rst
+++ b/doc/guides/tools/testbbdev.rst
@@ -139,7 +139,7 @@ There are 6 main test cases that can be executed using testbbdev tool:
* Latency measurement [-c latency]
- Measures the time consumed from the first enqueue until the first
appearance of a dequeued result
- - This measurment represents the full latency of a bbdev operation
+ - This measurement represents the full latency of a bbdev operation
(encode or decode) to execute
* Poll-mode Throughput measurement [-c throughput]
--
2.7.5
^ permalink raw reply [relevance 3%]
* [dpdk-dev] [PATCH v2 1/2] doc: fix spelling errors reported by aspell
@ 2019-04-26 15:14 3% John McNamara
2019-04-26 15:14 3% ` John McNamara
0 siblings, 1 reply; 140+ results
From: John McNamara @ 2019-04-26 15:14 UTC (permalink / raw)
To: dev; +Cc: John McNamara
Fix spelling errors in the guide docs.
Signed-off-by: John McNamara <john.mcnamara@intel.com>
---
doc/guides/compressdevs/overview.rst | 2 +-
doc/guides/contributing/patches.rst | 2 +-
doc/guides/cryptodevs/aesni_mb.rst | 2 +-
doc/guides/cryptodevs/overview.rst | 2 +-
doc/guides/cryptodevs/scheduler.rst | 2 +-
doc/guides/eventdevs/opdl.rst | 2 +-
doc/guides/eventdevs/sw.rst | 4 ++--
doc/guides/howto/lm_bond_virtio_sriov.rst | 2 +-
doc/guides/howto/lm_virtio_vhost_user.rst | 4 ++--
doc/guides/howto/rte_flow.rst | 6 ++---
doc/guides/howto/telemetry.rst | 2 +-
.../howto/virtio_user_as_exceptional_path.rst | 8 +++----
doc/guides/nics/af_packet.rst | 4 ++--
doc/guides/nics/atlantic.rst | 2 +-
doc/guides/nics/cxgbe.rst | 4 ++--
doc/guides/nics/dpaa.rst | 2 +-
doc/guides/nics/dpaa2.rst | 2 +-
doc/guides/nics/ena.rst | 2 +-
doc/guides/nics/enetc.rst | 2 +-
doc/guides/nics/enic.rst | 2 +-
doc/guides/nics/features.rst | 2 +-
doc/guides/nics/i40e.rst | 2 +-
doc/guides/nics/ixgbe.rst | 4 ++--
doc/guides/nics/kni.rst | 2 +-
doc/guides/nics/mlx4.rst | 2 +-
doc/guides/nics/mlx5.rst | 4 ++--
doc/guides/nics/mvpp2.rst | 2 +-
doc/guides/nics/netvsc.rst | 2 +-
doc/guides/nics/nfb.rst | 2 +-
doc/guides/nics/nfp.rst | 4 ++--
doc/guides/nics/sfc_efx.rst | 14 +++++------
doc/guides/nics/szedata2.rst | 2 +-
doc/guides/nics/tap.rst | 2 +-
doc/guides/platform/dpaa.rst | 4 ++--
doc/guides/platform/dpaa2.rst | 4 ++--
doc/guides/prog_guide/bbdev.rst | 4 ++--
doc/guides/prog_guide/compressdev.rst | 6 ++---
doc/guides/prog_guide/cryptodev_lib.rst | 12 +++++-----
doc/guides/prog_guide/dev_kit_build_system.rst | 2 +-
doc/guides/prog_guide/efd_lib.rst | 2 +-
doc/guides/prog_guide/env_abstraction_layer.rst | 2 +-
.../prog_guide/event_ethernet_rx_adapter.rst | 6 ++---
doc/guides/prog_guide/eventdev.rst | 6 ++---
doc/guides/prog_guide/ipsec_lib.rst | 16 ++++++-------
doc/guides/prog_guide/kernel_nic_interface.rst | 2 +-
doc/guides/prog_guide/metrics_lib.rst | 2 +-
doc/guides/prog_guide/multi_proc_support.rst | 2 +-
doc/guides/prog_guide/profile_app.rst | 4 ++--
doc/guides/prog_guide/rte_flow.rst | 8 +++----
doc/guides/prog_guide/rte_security.rst | 20 ++++++++--------
doc/guides/prog_guide/traffic_management.rst | 2 +-
doc/guides/prog_guide/vhost_lib.rst | 2 +-
doc/guides/rawdevs/ifpga_rawdev.rst | 2 +-
doc/guides/rel_notes/known_issues.rst | 8 +++----
doc/guides/rel_notes/release_17_11.rst | 10 ++++----
doc/guides/sample_app_ug/bbdev_app.rst | 4 ++--
doc/guides/sample_app_ug/eventdev_pipeline.rst | 2 +-
doc/guides/sample_app_ug/intro.rst | 2 +-
doc/guides/sample_app_ug/ip_pipeline.rst | 4 ++--
doc/guides/sample_app_ug/ipsec_secgw.rst | 8 +++----
doc/guides/sample_app_ug/performance_thread.rst | 4 ++--
doc/guides/sample_app_ug/qos_metering.rst | 2 +-
doc/guides/sample_app_ug/test_pipeline.rst | 2 +-
doc/guides/sample_app_ug/vhost.rst | 4 ++--
doc/guides/sample_app_ug/vhost_scsi.rst | 2 +-
doc/guides/sample_app_ug/vm_power_management.rst | 10 ++++----
doc/guides/testpmd_app_ug/run_app.rst | 10 ++++----
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 28 +++++++++++-----------
doc/guides/tools/cryptoperf.rst | 22 ++++++++---------
doc/guides/tools/proc_info.rst | 6 ++---
doc/guides/tools/testbbdev.rst | 2 +-
71 files changed, 170 insertions(+), 170 deletions(-)
diff --git a/doc/guides/compressdevs/overview.rst b/doc/guides/compressdevs/overview.rst
index 70bbe82..809e4e6 100644
--- a/doc/guides/compressdevs/overview.rst
+++ b/doc/guides/compressdevs/overview.rst
@@ -18,7 +18,7 @@ Supported Feature Flags
without making any modifications to it (no compression done).
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means PMD supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index d8404e6..3b2b174 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -8,7 +8,7 @@ Contributing Code to DPDK
This document outlines the guidelines for submitting code to DPDK.
-The DPDK development process is modelled (loosely) on the Linux Kernel development model so it is worth reading the
+The DPDK development process is modeled (loosely) on the Linux Kernel development model so it is worth reading the
Linux kernel guide on submitting patches:
`How to Get Your Change Into the Linux Kernel <https://www.kernel.org/doc/html/latest/process/submitting-patches.html>`_.
The rationale for many of the DPDK guidelines is explained in greater detail in the kernel guidelines.
diff --git a/doc/guides/cryptodevs/aesni_mb.rst b/doc/guides/cryptodevs/aesni_mb.rst
index 8915201..1eff2b0 100644
--- a/doc/guides/cryptodevs/aesni_mb.rst
+++ b/doc/guides/cryptodevs/aesni_mb.rst
@@ -129,7 +129,7 @@ Extra notes
For AES Counter mode (AES-CTR), the library supports two different sizes for Initialization
Vector (IV):
-* 12 bytes: used mainly for IPSec, as it requires 12 bytes from the user, which internally
+* 12 bytes: used mainly for IPsec, as it requires 12 bytes from the user, which internally
are appended the counter block (4 bytes), which is set to 1 for the first block
(no padding required from the user)
diff --git a/doc/guides/cryptodevs/overview.rst b/doc/guides/cryptodevs/overview.rst
index 12f342b..a972c79 100644
--- a/doc/guides/cryptodevs/overview.rst
+++ b/doc/guides/cryptodevs/overview.rst
@@ -18,7 +18,7 @@ Supported Feature Flags
being the operation in-place (input address = output address).
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means pmd supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/cryptodevs/scheduler.rst b/doc/guides/cryptodevs/scheduler.rst
index a754a27..7004ca4 100644
--- a/doc/guides/cryptodevs/scheduler.rst
+++ b/doc/guides/cryptodevs/scheduler.rst
@@ -165,7 +165,7 @@ operation:
For pure small packet size (64 bytes) traffic however the multi-core mode is not
an optimal solution, as it doesn't give significant per-core performance improvement.
For mixed traffic (IMIX) the optimal number of worker cores is around 2-3.
- For large packets (1.5 Kbytes) scheduler shows linear scaling in performance
+ For large packets (1.5 kbytes) scheduler shows linear scaling in performance
up to eight cores.
Each worker uses its own slave cryptodev. Only software cryptodevs
are supported. Only the same type of cryptodevs should be used concurrently.
diff --git a/doc/guides/eventdevs/opdl.rst b/doc/guides/eventdevs/opdl.rst
index 0262a33..979f6cd 100644
--- a/doc/guides/eventdevs/opdl.rst
+++ b/doc/guides/eventdevs/opdl.rst
@@ -8,7 +8,7 @@ The OPDL (Ordered Packet Distribution Library) eventdev is a specific\
implementation of the eventdev API. It is particularly suited to packet\
processing workloads that have high throughput and low latency requirements.\
All packets follow the same path through the device. The order in which\
-packets follow is determinted by the order in which queues are set up.\
+packets follow is determined by the order in which queues are set up.\
Events are left on the ring until they are transmitted. As a result packets\
do not go out of order
diff --git a/doc/guides/eventdevs/sw.rst b/doc/guides/eventdevs/sw.rst
index afdcad7..04c8b03 100644
--- a/doc/guides/eventdevs/sw.rst
+++ b/doc/guides/eventdevs/sw.rst
@@ -70,7 +70,7 @@ Credit Quanta
The credit quanta is the number of credits that a port will fetch at a time from
the instance's credit pool. Higher numbers will cause less overhead in the
atomic credit fetch code, however it also reduces the overall number of credits
-in the system faster. A balanced number (eg 32) ensures that only small numbers
+in the system faster. A balanced number (e.g. 32) ensures that only small numbers
of credits are pre-allocated at a time, while also mitigating performance impact
of the atomics.
@@ -100,7 +100,7 @@ feature would be significant.
~~~~~~~~~~~~~~~~~~
The software eventdev does not support creating queues that handle all types of
-traffic. An eventdev with this capability allows enqueueing Atomic, Ordered and
+traffic. An eventdev with this capability allows enqueuing Atomic, Ordered and
Parallel traffic to the same queue, but scheduling each of them appropriately.
The reason to not allow Atomic, Ordered and Parallel event types in the
diff --git a/doc/guides/howto/lm_bond_virtio_sriov.rst b/doc/guides/howto/lm_bond_virtio_sriov.rst
index ee8ccda..07563b3 100644
--- a/doc/guides/howto/lm_bond_virtio_sriov.rst
+++ b/doc/guides/howto/lm_bond_virtio_sriov.rst
@@ -328,7 +328,7 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
testpmd> show bonding config 2
testpmd> port attach 0000:00:04.0
diff --git a/doc/guides/howto/lm_virtio_vhost_user.rst b/doc/guides/howto/lm_virtio_vhost_user.rst
index 6ebc10f..ecb7832 100644
--- a/doc/guides/howto/lm_virtio_vhost_user.rst
+++ b/doc/guides/howto/lm_virtio_vhost_user.rst
@@ -243,7 +243,7 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
Virtio traffic is seen at P0 and P1.
@@ -338,7 +338,7 @@ reset_vf_on_212_131.sh
#!/bin/sh
# This script is run on the host 10.237.212.131 to reset SRIOV
- # BDF for Ninatic NIC is 0000:06:00.0
+ # BDF for Niantic NIC is 0000:06:00.0
cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
echo 0 > /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
diff --git a/doc/guides/howto/rte_flow.rst b/doc/guides/howto/rte_flow.rst
index 3dcda6c..e197376 100644
--- a/doc/guides/howto/rte_flow.rst
+++ b/doc/guides/howto/rte_flow.rst
@@ -23,7 +23,7 @@ In this example we will create a simple rule that drops packets whose IPv4
destination equals 192.168.3.2. This code is equivalent to the following
testpmd command (wrapped for clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst is 192.168.3.2 / end actions drop / end
Code
@@ -118,7 +118,7 @@ a mask.
This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst spec 192.168.3.0 dst mask 255.255.255.0 /
end actions drop / end
@@ -219,7 +219,7 @@ In this example we will create a rule that routes all vlan id 123 to queue 3.
This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
+ testpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
end actions queue index 3 / end
Code
diff --git a/doc/guides/howto/telemetry.rst b/doc/guides/howto/telemetry.rst
index 00f8f7a..e10804d 100644
--- a/doc/guides/howto/telemetry.rst
+++ b/doc/guides/howto/telemetry.rst
@@ -18,7 +18,7 @@ which acts as the client.
In DPDK, applications are used to initialize the ``telemetry``. To view incoming
traffic on featured ports, the application should be run first (ie. after ports
are configured). Once the application is running, the service assurance agent
-(for example the collectd plugin) should be run to begin querying the API.
+(for example the CollectD plugin) should be run to begin querying the API.
A client connects their Service Assurance application to the DPDK application
via a UNIX socket. Once a connection is established, a client can send JSON
diff --git a/doc/guides/howto/virtio_user_as_exceptional_path.rst b/doc/guides/howto/virtio_user_as_exceptional_path.rst
index 4910c12..ec021af 100644
--- a/doc/guides/howto/virtio_user_as_exceptional_path.rst
+++ b/doc/guides/howto/virtio_user_as_exceptional_path.rst
@@ -1,7 +1,7 @@
.. SPDX-License-Identifier: BSD-3-Clause
Copyright(c) 2016 Intel Corporation.
-.. _virtio_user_as_excpetional_path:
+.. _virtio_user_as_exceptional_path:
Virtio_user as Exceptional Path
===============================
@@ -22,7 +22,7 @@ solution is very promising in:
* Features
vhost-net is born to be a networking solution, which has lots of networking
- related featuers, like multi queue, tso, multi-seg mbuf, etc.
+ related features, like multi queue, tso, multi-seg mbuf, etc.
* Performance
@@ -38,7 +38,7 @@ in :numref:`figure_virtio_user_as_exceptional_path`.
.. figure:: img/virtio_user_as_exceptional_path.*
- Overview of a DPDK app using virtio-user as excpetional path
+ Overview of a DPDK app using virtio-user as exceptional path
Sample Usage
@@ -75,7 +75,7 @@ compiling the kernel and those kernel modules should be inserted.
* ``queues``
- Number of multi-queues. Each qeueue will be served by a kthread. For example:
+ Number of multi-queues. Each queue will be served by a kthread. For example:
.. code-block:: console
diff --git a/doc/guides/nics/af_packet.rst b/doc/guides/nics/af_packet.rst
index 1260bb2..efd6f1c 100644
--- a/doc/guides/nics/af_packet.rst
+++ b/doc/guides/nics/af_packet.rst
@@ -13,13 +13,13 @@ PACKET_MMAP, which provides a mmap'ed ring buffer, shared between user space
and kernel, that's used to send and receive packets. This helps reducing system
calls and the copies needed between user space and Kernel.
-The PACKET_FANOUT_HASH behaviour of AF_PACKET is used for frame reception.
+The PACKET_FANOUT_HASH behavior of AF_PACKET is used for frame reception.
Options and inherent limitations
--------------------------------
The following options can be provided to set up an af_packet port in DPDK.
-Some of these, in turn, will be used to configure the PAKET_MMAP settings.
+Some of these, in turn, will be used to configure the PACKET_MMAP settings.
* ``iface`` - name of the Kernel interface to attach to (required);
* ``qpairs`` - number of Rx and Tx queues (optional, default 1);
diff --git a/doc/guides/nics/atlantic.rst b/doc/guides/nics/atlantic.rst
index 22f2410..3f3f294 100644
--- a/doc/guides/nics/atlantic.rst
+++ b/doc/guides/nics/atlantic.rst
@@ -18,7 +18,7 @@ Supported features
- Port statistics
- RSS (Receive Side Scaling)
- Checksum offload
-- Jumbo Frame upto 16K
+- Jumbo Frame up to 16K
- MACSEC offload
Experimental API features
diff --git a/doc/guides/nics/cxgbe.rst b/doc/guides/nics/cxgbe.rst
index f3e6115..7a893cc 100644
--- a/doc/guides/nics/cxgbe.rst
+++ b/doc/guides/nics/cxgbe.rst
@@ -126,7 +126,7 @@ enabling debugging options may affect system performance.
- ``CONFIG_RTE_LIBRTE_CXGBE_TPUT`` (default **y**)
- Toggle behaviour to prefer Throughput or Latency.
+ Toggle behavior to prefer Throughput or Latency.
Runtime Options
~~~~~~~~~~~~~~~
@@ -140,7 +140,7 @@ be passed as part of EAL arguments. For example,
- ``keep_ovlan`` (default **0**)
- Toggle behaviour to keep/strip outer VLAN in Q-in-Q packets. If
+ Toggle behavior to keep/strip outer VLAN in Q-in-Q packets. If
enabled, the outer VLAN tag is preserved in Q-in-Q packets. Otherwise,
the outer VLAN tag is stripped in Q-in-Q packets.
diff --git a/doc/guides/nics/dpaa.rst b/doc/guides/nics/dpaa.rst
index fb7bc7d..2243a4a 100644
--- a/doc/guides/nics/dpaa.rst
+++ b/doc/guides/nics/dpaa.rst
@@ -251,7 +251,7 @@ state during application initialization:
automatically be assigned from the these high perf PUSH queues. Any queue
configuration beyond that will be standard Rx queues. The application can
choose to change their number if HW portals are limited.
- The valid values are from '0' to '4'. The valuse shall be set to '0' if the
+ The valid values are from '0' to '4'. The values shall be set to '0' if the
application want to use eventdev with DPAA device.
diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst
index d74d8f8..b3b7678 100644
--- a/doc/guides/nics/dpaa2.rst
+++ b/doc/guides/nics/dpaa2.rst
@@ -379,7 +379,7 @@ active -- Ethernet, crypto, compression, etc.
DPBP based Mempool driver
~~~~~~~~~~~~~~~~~~~~~~~~~
-The DPBP driver is bound to a DPBP objects and provides sevices to
+The DPBP driver is bound to a DPBP objects and provides services to
create a hardware offloaded packet buffer mempool.
DPAA2 NIC Driver
diff --git a/doc/guides/nics/ena.rst b/doc/guides/nics/ena.rst
index 80da4b6..d44f3cd 100644
--- a/doc/guides/nics/ena.rst
+++ b/doc/guides/nics/ena.rst
@@ -189,7 +189,7 @@ Prerequisites
reduces the latency of the packets by pushing the header directly through
the PCI to the device, before the DMA is even triggered. For proper work
kernel PCI driver must support write combining (WC). In mainline version of
- ``igb_uio`` (in DPDK repo) it must be enabled by loding module with
+ ``igb_uio`` (in DPDK repo) it must be enabled by loading module with
``wc_activate=1`` flag (example below). However, mainline's vfio-pci
driver in kernel doesn't have WC support yet (planed to be added).
If vfio-pci used user should be either turn off ENAv2 (to avoid performance
diff --git a/doc/guides/nics/enetc.rst b/doc/guides/nics/enetc.rst
index 2620460..3c896ee 100644
--- a/doc/guides/nics/enetc.rst
+++ b/doc/guides/nics/enetc.rst
@@ -76,7 +76,7 @@ Supported ENETC SoCs
Prerequisites
~~~~~~~~~~~~~
-There are three main pre-requisities for executing ENETC PMD on a ENETC
+There are three main pre-requisites for executing ENETC PMD on a ENETC
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/nics/enic.rst b/doc/guides/nics/enic.rst
index 726a69e..cdb55e0 100644
--- a/doc/guides/nics/enic.rst
+++ b/doc/guides/nics/enic.rst
@@ -224,7 +224,7 @@ the use of SR-IOV.
passthrough devices do not require libvirt, port profiles, and VM-FEX.
-.. _enic-genic-flow-api:
+.. _enic-generic-flow-api:
Generic Flow API support
------------------------
diff --git a/doc/guides/nics/features.rst b/doc/guides/nics/features.rst
index c5bf322..d57ddc2 100644
--- a/doc/guides/nics/features.rst
+++ b/doc/guides/nics/features.rst
@@ -495,7 +495,7 @@ Supports adding traffic mirroring rules.
Inline crypto
-------------
-Supports inline crypto processing (eg. inline IPsec). See Security library and PMD documentation for more details.
+Supports inline crypto processing (e.g. inline IPsec). See Security library and PMD documentation for more details.
* **[uses] rte_eth_rxconf,rte_eth_rxmode**: ``offloads:DEV_RX_OFFLOAD_SECURITY``,
* **[uses] rte_eth_txconf,rte_eth_txmode**: ``offloads:DEV_TX_OFFLOAD_SECURITY``.
diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 9680a92..2e9ec79 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -580,7 +580,7 @@ bandwidth setting.
TC TX scheduling mode setting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-There're 2 TX scheduling modes for TCs, round robin and strict priority mode.
+There are 2 TX scheduling modes for TCs, round robin and strict priority mode.
If a TC is set to strict priority mode, it can consume unlimited bandwidth.
It means if APP has set the max bandwidth for that TC, it comes to no
effect.
diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
index 1c294b0..975143f 100644
--- a/doc/guides/nics/ixgbe.rst
+++ b/doc/guides/nics/ixgbe.rst
@@ -203,8 +203,8 @@ as a workaround.
X550 does not support legacy interrupt mode
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Desccription
-^^^^^^^^^^^^
+Description
+^^^^^^^^^^^
X550 cannot get interrupts if using ``uio_pci_generic`` module or using legacy
interrupt mode of ``igb_uio`` or ``vfio``. Because the errata of X550 states
that the Interrupt Status bit is not implemented. The errata is the item #22
diff --git a/doc/guides/nics/kni.rst b/doc/guides/nics/kni.rst
index a66c595..602a06b 100644
--- a/doc/guides/nics/kni.rst
+++ b/doc/guides/nics/kni.rst
@@ -65,7 +65,7 @@ backend device by default.
PMD arguments
-------------
-``no_request_thread``, by default PMD creates a phtread for each KNI interface
+``no_request_thread``, by default PMD creates a pthread for each KNI interface
to handle Linux network interface control commands, like ``ifconfig kni0 up``
With ``no_request_thread`` option, pthread is not created and control commands
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index aaf1907..f6d7a16 100644
--- a/doc/guides/nics/mlx4.rst
+++ b/doc/guides/nics/mlx4.rst
@@ -83,7 +83,7 @@ These options can be modified in the ``.config`` file.
- ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
- Embed static flavour of the dependencies **libibverbs** and **libmlx4**
+ Embed static flavor of the dependencies **libibverbs** and **libmlx4**
in the PMD shared library or the executable static binary.
- ``CONFIG_RTE_LIBRTE_MLX4_DEBUG`` (default **n**)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 5fa6b62..af1e408 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -168,7 +168,7 @@ Limitations
- must specify the VXLAN item with tunnel outer parameters.
- must specify the tunnel outer VNI in the VXLAN item.
- must specify the tunnel outer remote (destination) UDP port in the VXLAN item.
- - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interace, wildcards not allowed.
+ - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interface, wildcards not allowed.
- must specify the tunnel outer remote (destination) IPv4 or IPv6 in the VXLAN item, group IPs allowed.
- must specify the tunnel outer destination MAC address in the VXLAN item, this address will be used to create neigh rule.
@@ -216,7 +216,7 @@ These options can be modified in the ``.config`` file.
- ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
- Embed static flavour of the dependencies **libibverbs** and **libmlx5**
+ Embed static flavor of the dependencies **libibverbs** and **libmlx5**
in the PMD shared library or the executable static binary.
- ``CONFIG_RTE_LIBRTE_MLX5_DEBUG`` (default **n**)
diff --git a/doc/guides/nics/mvpp2.rst b/doc/guides/nics/mvpp2.rst
index 09e2f2a..bacc013 100644
--- a/doc/guides/nics/mvpp2.rst
+++ b/doc/guides/nics/mvpp2.rst
@@ -91,7 +91,7 @@ Limitations
chance to start in a sane state.
- MUSDK architecture does not support changing configuration in run time.
- All nessesary configurations should be done before first dev_start().
+ All necessary configurations should be done before first dev_start().
- RX queue start/stop is not supported.
diff --git a/doc/guides/nics/netvsc.rst b/doc/guides/nics/netvsc.rst
index 87fabf5..6dbb9a5 100644
--- a/doc/guides/nics/netvsc.rst
+++ b/doc/guides/nics/netvsc.rst
@@ -89,7 +89,7 @@ operations:
.. Note::
- The dpkd-devbind.py script can not be used since it only handles PCI devices.
+ The dpdk-devbind.py script can not be used since it only handles PCI devices.
Prerequisites
diff --git a/doc/guides/nics/nfb.rst b/doc/guides/nics/nfb.rst
index a7fb963..8df76c0 100644
--- a/doc/guides/nics/nfb.rst
+++ b/doc/guides/nics/nfb.rst
@@ -81,7 +81,7 @@ The NFB cards are multi-port multi-queue cards, where (generally) data from any
Ethernet port may be sent to any queue.
They are represented in DPDK as a single port.
-NFB-200G2QL card employs an addon cable which allows to connect it to two
+NFB-200G2QL card employs an add-on cable which allows to connect it to two
physical PCI-E slots at the same time (see the diagram below).
This is done to allow 200 Gbps of traffic to be transferred through the PCI-E
bus (note that a single PCI-E 3.0 x16 slot provides only 125 Gbps theoretical
diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst
index 09a8529..309fa5d 100644
--- a/doc/guides/nics/nfp.rst
+++ b/doc/guides/nics/nfp.rst
@@ -149,8 +149,8 @@ PF multiprocess support
-----------------------
Due to how the driver needs to access the NFP through a CPP interface, which implies
-to use specific registers inside the chip, the number of secondary proceses with PF
-ports is limitted to only one.
+to use specific registers inside the chip, the number of secondary processes with PF
+ports is limited to only one.
This limitation will be solved in future versions but having basic multiprocess support
is important for allowing development and debugging through the PF using a secondary
diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst
index eb47f25..6d01d05 100644
--- a/doc/guides/nics/sfc_efx.rst
+++ b/doc/guides/nics/sfc_efx.rst
@@ -96,7 +96,7 @@ Non-supported Features
The features not yet supported include:
-- Receive queue interupts
+- Receive queue interrupts
- Priority-based flow control
@@ -209,12 +209,12 @@ Validating flow rules depends on the firmware variant.
The :ref:`flow_isolated_mode` is supported.
-Ethernet destinaton individual/group match
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Ethernet destination individual/group match
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ethernet item supports I/G matching, if only the corresponding bit is set
-in the mask of destination address. If destinaton address in the spec is
-multicast, it matches all multicast (and broadcast) packets, oherwise it
+in the mask of destination address. If destination address in the spec is
+multicast, it matches all multicast (and broadcast) packets, otherwise it
matches unicast packets that are not filtered by other flow rules.
Exceptions to flow rules
@@ -348,10 +348,10 @@ boolean parameters value.
- ``perf_profile`` [auto|throughput|low-latency] (default **throughput**)
- Choose hardware tunning to be optimized for either throughput or
+ Choose hardware tuning to be optimized for either throughput or
low-latency.
**auto** allows NIC firmware to make a choice based on
- installed licences and firmware variant configured using **sfboot**.
+ installed licenses and firmware variant configured using **sfboot**.
- ``stats_update_period_ms`` [long] (default **1000**)
diff --git a/doc/guides/nics/szedata2.rst b/doc/guides/nics/szedata2.rst
index a2092f9..94dba82 100644
--- a/doc/guides/nics/szedata2.rst
+++ b/doc/guides/nics/szedata2.rst
@@ -89,7 +89,7 @@ The NFB cards are multi-port multi-queue cards, where (generally) data from any
Ethernet port may be sent to any queue.
They were historically represented in DPDK as a single port.
-However, the new NFB-200G2QL card employs an addon cable which allows to connect
+However, the new NFB-200G2QL card employs an add-on cable which allows to connect
it to two physical PCI-E slots at the same time (see the diagram below).
This is done to allow 200 Gbps of traffic to be transferred through the PCI-E
bus (note that a single PCI-E 3.0 x16 slot provides only 125 Gbps theoretical
diff --git a/doc/guides/nics/tap.rst b/doc/guides/nics/tap.rst
index 063bd0b..4b6d77d 100644
--- a/doc/guides/nics/tap.rst
+++ b/doc/guides/nics/tap.rst
@@ -40,7 +40,7 @@ actual MAC address: ``00:64:74:61:70:[00-FF]``.
--vdev=net_tap0,mac="00:64:74:61:70:11"
The MAC address will have a user value passed as string. The MAC address is in
-format with delimeter ``:``. The string is byte converted to hex and you get
+format with delimiter ``:``. The string is byte converted to hex and you get
the actual MAC address: ``00:64:74:61:70:11``.
It is possible to specify a remote netdevice to capture packets from by adding
diff --git a/doc/guides/platform/dpaa.rst b/doc/guides/platform/dpaa.rst
index 3904871..6005f22 100644
--- a/doc/guides/platform/dpaa.rst
+++ b/doc/guides/platform/dpaa.rst
@@ -4,7 +4,7 @@
NXP QorIQ DPAA Board Support Package
====================================
-This doc has information about steps to setup QorIq dpaa
+This doc has information about steps to setup QorIQ dpaa
based layerscape platform and information about common offload
hw block drivers of **NXP QorIQ DPAA** SoC family.
@@ -38,7 +38,7 @@ Common Offload HW Block Drivers
Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA PMD on a DPAA
+There are four main pre-requisites for executing DPAA PMD on a DPAA
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/platform/dpaa2.rst b/doc/guides/platform/dpaa2.rst
index 5a64406..2586af0 100644
--- a/doc/guides/platform/dpaa2.rst
+++ b/doc/guides/platform/dpaa2.rst
@@ -4,7 +4,7 @@
NXP QorIQ DPAA2 Board Support Package
=====================================
-This doc has information about steps to setup NXP QoriQ DPAA2 platform
+This doc has information about steps to setup NXP QorIQ DPAA2 platform
and information about common offload hw block drivers of
**NXP QorIQ DPAA2** SoC family.
@@ -48,7 +48,7 @@ Common Offload HW Block Drivers
Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA2 PMD on a DPAA2
+There are four main pre-requisites for executing DPAA2 PMD on a DPAA2
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index 9de1444..658ffd4 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -78,7 +78,7 @@ From the application point of view, each instance of a bbdev device consists of
one or more queues identified by queue IDs. While different devices may have
different capabilities (e.g. support different operation types), all queues on
a device support identical configuration possibilities. A queue is configured
-for only one type of operation and is configured at initializations time.
+for only one type of operation and is configured at initialization time.
When an operation is enqueued to a specific queue ID, the result is dequeued
from the same queue ID.
@@ -678,7 +678,7 @@ bbdev framework, by giving a sample code performing a loop-back operation with a
baseband processor capable of transceiving data packets.
The following sample C-like pseudo-code shows the basic steps to encode several
-buffers using (**sw_trubo**) bbdev PMD.
+buffers using (**sw_turbo**) bbdev PMD.
.. code-block:: c
diff --git a/doc/guides/prog_guide/compressdev.rst b/doc/guides/prog_guide/compressdev.rst
index ad97037..a06c835 100644
--- a/doc/guides/prog_guide/compressdev.rst
+++ b/doc/guides/prog_guide/compressdev.rst
@@ -17,7 +17,7 @@ Device Creation
Physical compression devices are discovered during the bus probe of the EAL function
which is executed at DPDK initialization, based on their unique device identifier.
-For eg. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
+For e.g. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
Specific physical compression devices, like other physical devices in DPDK can be
white-listed or black-listed using the EAL command line options.
@@ -379,7 +379,7 @@ using priv_xform would look like:
setup op->m_src and op->m_dst;
}
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, comp_ops, NUM_OPS);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deque = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, NUM_OPS);
} while (num_dqud < num_enqd);
@@ -526,7 +526,7 @@ An example pseudocode to set up and process a stream having NUM_CHUNKS with each
op->src.length = CHUNK_LEN;
op->input_chksum = 0;
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, &op[i], 1);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deqd = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, 1);
} while (num_deqd < num_enqd);
diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst
index 74a930b..23fa5bc 100644
--- a/doc/guides/prog_guide/cryptodev_lib.rst
+++ b/doc/guides/prog_guide/cryptodev_lib.rst
@@ -14,7 +14,7 @@ and AEAD symmetric and asymmetric Crypto operations.
Design Principles
-----------------
-The cryptodev library follows the same basic principles as those used in DPDKs
+The cryptodev library follows the same basic principles as those used in DPDK's
Ethernet Device framework. The Crypto framework provides a generic Crypto device
framework which supports both physical (hardware) and virtual (software) Crypto
devices as well as a generic Crypto API which allows Crypto devices to be
@@ -48,7 +48,7 @@ From the command line using the --vdev EAL option
* If DPDK application requires multiple software crypto PMD devices then required
number of ``--vdev`` with appropriate libraries are to be added.
- * An Application with crypto PMD instaces sharing the same library requires unique ID.
+ * An Application with crypto PMD instances sharing the same library requires unique ID.
Example: ``--vdev 'crypto_aesni_mb0' --vdev 'crypto_aesni_mb1'``
@@ -396,7 +396,7 @@ Operation Management and Allocation
The cryptodev library provides an API set for managing Crypto operations which
utilize the Mempool Library to allocate operation buffers. Therefore, it ensures
-that the crytpo operation is interleaved optimally across the channels and
+that the crypto operation is interleaved optimally across the channels and
ranks for optimal processing.
A ``rte_crypto_op`` contains a field indicating the pool that it originated from.
When calling ``rte_crypto_op_free(op)``, the operation returns to its original pool.
@@ -602,7 +602,7 @@ Sample code
There are various sample applications that show how to use the cryptodev library,
such as the L2fwd with Crypto sample application (L2fwd-crypto) and
-the IPSec Security Gateway application (ipsec-secgw).
+the IPsec Security Gateway application (ipsec-secgw).
While these applications demonstrate how an application can be created to perform
generic crypto operation, the required complexity hides the basic steps of
@@ -807,7 +807,7 @@ using one of the crypto PMDs available in DPDK.
/*
* Dequeue the crypto operations until all the operations
- * are proccessed in the crypto device.
+ * are processed in the crypto device.
*/
uint16_t num_dequeued_ops, total_num_dequeued_ops = 0;
do {
@@ -886,7 +886,7 @@ the order in which the transforms are passed indicates the order of the chaining
Not all asymmetric crypto xforms are supported for chaining. Currently supported
asymmetric crypto chaining is Diffie-Hellman private key generation followed by
public generation. Also, currently API does not support chaining of symmetric and
-asymmetric crypto xfroms.
+asymmetric crypto xforms.
Each xform defines specific asymmetric crypto algo. Currently supported are:
* RSA
diff --git a/doc/guides/prog_guide/dev_kit_build_system.rst b/doc/guides/prog_guide/dev_kit_build_system.rst
index 96dbf30..74dba4d 100644
--- a/doc/guides/prog_guide/dev_kit_build_system.rst
+++ b/doc/guides/prog_guide/dev_kit_build_system.rst
@@ -204,7 +204,7 @@ Creates the following symbol:
Which ``dpdk-pmdinfogen`` scans for. Using this information other relevant
bits of data can be exported from the object file and used to produce a
hardware support description, that ``dpdk-pmdinfogen`` then encodes into a
-json formatted string in the following format:
+JSON formatted string in the following format:
.. code-block:: c
diff --git a/doc/guides/prog_guide/efd_lib.rst b/doc/guides/prog_guide/efd_lib.rst
index cb1a1df..2b355ff 100644
--- a/doc/guides/prog_guide/efd_lib.rst
+++ b/doc/guides/prog_guide/efd_lib.rst
@@ -423,6 +423,6 @@ References
1- EFD is based on collaborative research work between Intel and
Carnegie Mellon University (CMU), interested readers can refer to the paper
-“Scaling Up Clustered Network Appliances with ScaleBricks;” Dong Zhou et al.
+"Scaling Up Clustered Network Appliances with ScaleBricks" Dong Zhou et al.
at SIGCOMM 2015 (`http://conferences.sigcomm.org/sigcomm/2015/pdf/papers/p241.pdf`)
for more information.
diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index fa8afdb..c27f730 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -733,7 +733,7 @@ The most important fields in the structure and how they are used are described b
Malloc heap is a doubly-linked list, where each element keeps track of its
previous and next elements. Due to the fact that hugepage memory can come and
-go, neighbouring malloc elements may not necessarily be adjacent in memory.
+go, neighboring malloc elements may not necessarily be adjacent in memory.
Also, since a malloc element may span multiple pages, its contents may not
necessarily be IOVA-contiguous either - each malloc element is only guaranteed
to be virtually contiguous.
diff --git a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
index e955299..c7dda92 100644
--- a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
+++ b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
@@ -162,7 +162,7 @@ The servicing_weight member of struct rte_event_eth_rx_adapter_queue_conf
is applicable when the adapter uses a service core function. The application
has to enable Rx queue interrupts when configuring the ethernet device
using the ``rte_eth_dev_configure()`` function and then use a servicing_weight
-of zero when addding the Rx queue to the adapter.
+of zero when adding the Rx queue to the adapter.
The adapter creates a thread blocked on the interrupt, on an interrupt this
thread enqueues the port id and the queue id to a ring buffer. The adapter
@@ -180,9 +180,9 @@ Rx Callback for SW Rx Adapter
For SW based packet transfers, i.e., when the
``RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT`` is not set in the adapter's
capabilities flags for a particular ethernet device, the service function
-temporarily enqueues mbufs to an event buffer before batch enqueueing these
+temporarily enqueues mbufs to an event buffer before batch enqueuing these
to the event device. If the buffer fills up, the service function stops
-dequeueing packets from the ethernet device. The application may want to
+dequeuing packets from the ethernet device. The application may want to
monitor the buffer fill level and instruct the service function to selectively
enqueue packets to the event device. The application may also use some other
criteria to decide which packets should enter the event device even when
diff --git a/doc/guides/prog_guide/eventdev.rst b/doc/guides/prog_guide/eventdev.rst
index dcdfeb7..7ea14ba 100644
--- a/doc/guides/prog_guide/eventdev.rst
+++ b/doc/guides/prog_guide/eventdev.rst
@@ -42,7 +42,7 @@ The rte_event structure contains the following metadata fields, which the
application fills in to have the event scheduled as required:
* ``flow_id`` - The targeted flow identifier for the enq/deq operation.
-* ``event_type`` - The source of this event, eg RTE_EVENT_TYPE_ETHDEV or CPU.
+* ``event_type`` - The source of this event, e.g. RTE_EVENT_TYPE_ETHDEV or CPU.
* ``sub_event_type`` - Distinguishes events inside the application, that have
the same event_type (see above)
* ``op`` - This field takes one of the RTE_EVENT_OP_* values, and tells the
@@ -265,7 +265,7 @@ Linking Queues and Ports
The final step is to "wire up" the ports to the queues. After this, the
eventdev is capable of scheduling events, and when cores request work to do,
the correct events are provided to that core. Note that the RX core takes input
-from eg: a NIC so it is not linked to any eventdev queues.
+from e.g.: a NIC so it is not linked to any eventdev queues.
Linking all workers to atomic queues, and the TX core to the single-link queue
can be achieved like this:
@@ -276,7 +276,7 @@ can be achieved like this:
uint8_t tx_port_id = 5;
uint8_t atomic_qs[] = {0, 1};
uint8_t single_link_q = 2;
- uin8t_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
+ uint8t_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
for(int worker_port_id = 1; worker_port_id <= 4; worker_port_id++) {
int links_made = rte_event_port_link(dev_id, worker_port_id, atomic_qs, NULL, 2);
diff --git a/doc/guides/prog_guide/ipsec_lib.rst b/doc/guides/prog_guide/ipsec_lib.rst
index 84696d4..6fc0888 100644
--- a/doc/guides/prog_guide/ipsec_lib.rst
+++ b/doc/guides/prog_guide/ipsec_lib.rst
@@ -65,7 +65,7 @@ In that mode the library functions perform
- check SQN
- prepare *rte_crypto_op* structure for each input packet
- - verify that integity check and decryption performed by crypto device
+ - verify that integrity check and decryption performed by crypto device
completed successfully
- check padding data
- remove outer IP header (tunnel mode) / update IP header (transport mode)
@@ -88,7 +88,7 @@ In that mode the library functions perform
* for inbound packets:
- - verify that integity check and decryption performed by *rte_security*
+ - verify that integrity check and decryption performed by *rte_security*
device completed successfully
- check SQN
- check padding data
@@ -101,10 +101,10 @@ In that mode the library functions perform
- generate SQN and IV
- add outer IP header (tunnel mode) / update IP header (transport mode)
- add ESP header and trailer, padding and IV data
- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
inline-crypto processing has to be performed by HW on this packet
- invoke *rte_security* device specific *set_pkt_metadata()* to associate
- secuirty device specific data with the packet
+ security device specific data with the packet
RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -113,15 +113,15 @@ In that mode the library functions perform
* for inbound packets:
- - verify that integity check and decryption performed by *rte_security*
+ - verify that integrity check and decryption performed by *rte_security*
device completed successfully
* for outbound packets:
- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
inline-crypto processing has to be performed by HW on this packet
- invoke *rte_security* device specific *set_pkt_metadata()* to associate
- secuirty device specific data with the packet
+ security device specific data with the packet
RTE_SECURITY_ACTION_TYPE_LOOKASIDE_PROTOCOL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -131,7 +131,7 @@ In that mode the library functions perform
* for inbound packets:
- prepare *rte_crypto_op* structure for each input packet
- - verify that integity check and decryption performed by crypto device
+ - verify that integrity check and decryption performed by crypto device
completed successfully
* for outbound packets:
diff --git a/doc/guides/prog_guide/kernel_nic_interface.rst b/doc/guides/prog_guide/kernel_nic_interface.rst
index 7fcbd93..daf87f4 100644
--- a/doc/guides/prog_guide/kernel_nic_interface.rst
+++ b/doc/guides/prog_guide/kernel_nic_interface.rst
@@ -227,7 +227,7 @@ application functions:
``config_promiscusity``:
- Called when the user changes the promiscusity state of the KNI
+ Called when the user changes the promiscuity state of the KNI
interface. For example, when the user runs ``ip link set promisc
[on|off] dev <ifaceX>``. If the user sets this callback function to
NULL, but sets the ``port_id`` field to a value other than -1, a default
diff --git a/doc/guides/prog_guide/metrics_lib.rst b/doc/guides/prog_guide/metrics_lib.rst
index e68e4e7..89bc7d6 100644
--- a/doc/guides/prog_guide/metrics_lib.rst
+++ b/doc/guides/prog_guide/metrics_lib.rst
@@ -25,7 +25,7 @@ individual device. Since the metrics library is self-contained, the only
restriction on port numbers is that they are less than ``RTE_MAX_ETHPORTS``
- there is no requirement for the ports to actually exist.
-Initialising the library
+Initializing the library
------------------------
Before the library can be used, it has to be initialized by calling
diff --git a/doc/guides/prog_guide/multi_proc_support.rst b/doc/guides/prog_guide/multi_proc_support.rst
index 1384fe3..6196d3f 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -273,7 +273,7 @@ will be populated by IPC are as follows:
those peer processes that were active at the time of request, how many have
replied)
* ``msgs`` - pointer to where all of the responses are stored. The order in
- which responses appear is undefined. Whendoing sycnrhonous requests, this
+ which responses appear is undefined. When doing synchronous requests, this
memory must be freed by the requestor after request completes!
For asynchronous requests, a function pointer to the callback function must be
diff --git a/doc/guides/prog_guide/profile_app.rst b/doc/guides/prog_guide/profile_app.rst
index 5af795c..a36ebef 100644
--- a/doc/guides/prog_guide/profile_app.rst
+++ b/doc/guides/prog_guide/profile_app.rst
@@ -64,7 +64,7 @@ The default ``cntvct_el0`` based ``rte_rdtsc()`` provides a portable means to
get a wall clock counter in user space. Typically it runs at <= 100MHz.
The alternative method to enable ``rte_rdtsc()`` for a high resolution wall
-clock counter is through the armv8 PMU subsystem. The PMU cycle counter runs
+clock counter is through the ARMv8 PMU subsystem. The PMU cycle counter runs
at CPU frequency. However, access to the PMU cycle counter from user space is
not enabled by default in the arm64 linux kernel. It is possible to enable
cycle counter for user space access by configuring the PMU from the privileged
@@ -75,7 +75,7 @@ scheme. Application can choose the PMU based implementation with
``CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU``.
The example below shows the steps to configure the PMU based cycle counter on
-an armv8 machine.
+an ARMv8 machine.
.. code-block:: console
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 0203f4f..937f52b 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2129,7 +2129,7 @@ as defined in the ``rte_flow_action_raw_decap``
This action modifies the payload of matched flows. The data supplied must
be a valid header, either holding layer 2 data in case of removing layer 2
-before eincapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
+before encapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
tunnel definition starting from layer 2 and moving to the tunnel item itself.
When applied to the original packet the resulting packet must be a
valid packet.
@@ -2279,7 +2279,7 @@ Action: ``DEC_TTL``
Decrease TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_dec_ttl:
@@ -2297,7 +2297,7 @@ Action: ``SET_TTL``
Assigns a new TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_set_ttl:
@@ -2725,7 +2725,7 @@ Caveats
- API operations are synchronous and blocking (``EAGAIN`` cannot be
returned).
-- There is no provision for reentrancy/multi-thread safety, although nothing
+- There is no provision for re-entrancy/multi-thread safety, although nothing
should prevent different devices from being configured at the same
time. PMDs may protect their control path functions accordingly.
diff --git a/doc/guides/prog_guide/rte_security.rst b/doc/guides/prog_guide/rte_security.rst
index cb70caa..7d0734a 100644
--- a/doc/guides/prog_guide/rte_security.rst
+++ b/doc/guides/prog_guide/rte_security.rst
@@ -40,7 +40,7 @@ Inline Crypto
~~~~~~~~~~~~~
RTE_SECURITY_ACTION_TYPE_INLINE_CRYPTO:
-The crypto processing for security protocol (e.g. IPSec) is processed
+The crypto processing for security protocol (e.g. IPsec) is processed
inline during receive and transmission on NIC port. The flow based
security action should be configured on the port.
@@ -48,7 +48,7 @@ Ingress Data path - The packet is decrypted in RX path and relevant
crypto status is set in Rx descriptors. After the successful inline
crypto processing the packet is presented to host as a regular Rx packet
however all security protocol related headers are still attached to the
-packet. e.g. In case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. In case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will remain in the packet but the received packet
contains the decrypted data where the encrypted data was when the packet
arrived. The driver Rx path check the descriptors and and based on the
@@ -111,7 +111,7 @@ Inline protocol offload
~~~~~~~~~~~~~~~~~~~~~~~
RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL:
-The crypto and protocol processing for security protocol (e.g. IPSec)
+The crypto and protocol processing for security protocol (e.g. IPsec)
is processed inline during receive and transmission. The flow based
security action should be configured on the port.
@@ -119,7 +119,7 @@ Ingress Data path - The packet is decrypted in the RX path and relevant
crypto status is set in the Rx descriptors. After the successful inline
crypto processing the packet is presented to the host as a regular Rx packet
but all security protocol related headers are optionally removed from the
-packet. e.g. in the case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. in the case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will be removed from the packet and the received packet
will contains the decrypted packet only. The driver Rx path checks the
descriptors and based on the crypto status sets additional flags in
@@ -132,7 +132,7 @@ to identify the security processing done on the packet.
The underlying device in this case is stateful. It is expected that
the device shall support crypto processing for all kind of packets matching
to a given flow, this includes fragmented packets (post reassembly).
- E.g. in case of IPSec the device may internally manage anti-replay etc.
+ E.g. in case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in the descriptor.
@@ -150,7 +150,7 @@ to cross the MTU size.
.. note::
The underlying device will manage state information required for egress
- processing. E.g. in case of IPSec, the seq number will be added to the
+ processing. E.g. in case of IPsec, the seq number will be added to the
packet, however the device shall provide indication when the sequence number
is about to overflow. The underlying device may support post encryption TSO.
@@ -199,13 +199,13 @@ crypto device.
Decryption: The packet is sent to the crypto device for security
protocol processing. The device will decrypt the packet and it will also
optionally remove additional security headers from the packet.
-E.g. in case of IPSec, IPSec tunnel headers (if any), ESP/AH headers
+E.g. in case of IPsec, IPsec tunnel headers (if any), ESP/AH headers
will be removed from the packet and the decrypted packet may contain
plain data only.
.. note::
- In case of IPSec the device may internally manage anti-replay etc.
+ In case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in descriptor.
@@ -217,7 +217,7 @@ for any protocol header addition.
.. note::
- In the case of IPSec, the seq number will be added to the packet,
+ In the case of IPsec, the seq number will be added to the packet,
It shall provide an indication when the sequence number is about to
overflow.
@@ -549,7 +549,7 @@ IPsec related configuration parameters are defined in ``rte_security_ipsec_xform
struct rte_security_ipsec_sa_options options;
/**< various SA options */
enum rte_security_ipsec_sa_direction direction;
- /**< IPSec SA Direction - Egress/Ingress */
+ /**< IPsec SA Direction - Egress/Ingress */
enum rte_security_ipsec_sa_protocol proto;
/**< IPsec SA Protocol - AH/ESP */
enum rte_security_ipsec_sa_mode mode;
diff --git a/doc/guides/prog_guide/traffic_management.rst b/doc/guides/prog_guide/traffic_management.rst
index 98ac431..05b34d9 100644
--- a/doc/guides/prog_guide/traffic_management.rst
+++ b/doc/guides/prog_guide/traffic_management.rst
@@ -39,7 +39,7 @@ whether a specific implementation does meet the needs to the user application.
At the TM level, users can get high level idea with the help of various
parameters such as maximum number of nodes, maximum number of hierarchical
levels, maximum number of shapers, maximum number of private shapers, type of
-scheduling algorithm (Strict Priority, Weighted Fair Queueing , etc.), etc.,
+scheduling algorithm (Strict Priority, Weighted Fair Queuing , etc.), etc.,
supported by the implementation.
Likewise, users can query the capability of the TM at the hierarchical level to
diff --git a/doc/guides/prog_guide/vhost_lib.rst b/doc/guides/prog_guide/vhost_lib.rst
index a86c07a..fc3ee43 100644
--- a/doc/guides/prog_guide/vhost_lib.rst
+++ b/doc/guides/prog_guide/vhost_lib.rst
@@ -63,7 +63,7 @@ The following is an overview of some key Vhost API functions:
512).
* zero copy is really good for VM2VM case. For iperf between two VMs, the
- boost could be above 70% (when TSO is enableld).
+ boost could be above 70% (when TSO is enabled).
* For zero copy in VM2NIC case, guest Tx used vring may be starved if the
PMD driver consume the mbuf but not release them timely.
diff --git a/doc/guides/rawdevs/ifpga_rawdev.rst b/doc/guides/rawdevs/ifpga_rawdev.rst
index d400db6..a3d92a6 100644
--- a/doc/guides/rawdevs/ifpga_rawdev.rst
+++ b/doc/guides/rawdevs/ifpga_rawdev.rst
@@ -91,7 +91,7 @@ Run-time parameters
-------------------
This driver is invoked automatically in systems added with Intel FPGA,
-but PR and IFPGA Bus scan is trigged by command line using
+but PR and IFPGA Bus scan is triggered by command line using
``--vdev 'ifpga_rawdev_cfg`` EAL option.
The following device parameters are supported:
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 358dfa3..276327c 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -676,7 +676,7 @@ igb uio legacy mode can not be used in X710/XL710/XXV710
**Description**:
X710/XL710/XXV710 NICs lack support for indicating INTx is asserted via the interrupt
- bit in the PCI status register. Linux delected them from INTx support table. The related
+ bit in the PCI status register. Linux deleted them from INTx support table. The related
`commit <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/pci/quirks.c?id=8bcf4525c5d43306c5fd07e132bc8650e3491aec>`_.
**Implication**:
@@ -722,9 +722,9 @@ Linux kernel 4.10.0 iommu attribute read error
**Description**:
When VT-d is enabled (``iommu=pt intel_iommu=on``), reading IOMMU attributes from
/sys/devices/virtual/iommu/dmarXXX/intel-iommu/cap on Linux kernel 4.10.0 error.
- This bug is fixed in `Linux commmit a7fdb6e648fb
+ This bug is fixed in `Linux commit a7fdb6e648fb
<https://patchwork.kernel.org/patch/9595727/>`_,
- This bug is introduced in `Linux commmit 39ab9555c241
+ This bug is introduced in `Linux commit 39ab9555c241
<https://patchwork.kernel.org/patch/9554403/>`_,
**Implication**:
@@ -842,7 +842,7 @@ AVX-512 support disabled
drop.
On DPDK v19.02 ``AVX-512`` disable scope is reduced to ``GCC`` and ``binutils version 2.30`` based
- on information accured from the GCC community defect.
+ on information accrued from the GCC community defect.
**Reason**:
Generated ``AVX-512`` code cause crash:
diff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/release_17_11.rst
index 2a93af3..6448b6c 100644
--- a/doc/guides/rel_notes/release_17_11.rst
+++ b/doc/guides/rel_notes/release_17_11.rst
@@ -168,7 +168,7 @@ New Features
* The DES CBC algorithm.
* The DES DOCSIS BPI algorithm.
- This change requires version 0.47 of the IPSec Multi-buffer library. For
+ This change requires version 0.47 of the IPsec Multi-buffer library. For
more details see the :doc:`../cryptodevs/aesni_mb` documentation.
* **Updated the OpenSSL PMD.**
@@ -198,7 +198,7 @@ New Features
* **Added the Security Offload Library.**
Added an experimental library - ``rte_security``. This provide security APIs
- for protocols like IPSec using inline ipsec offload to ethernet devices or
+ for protocols like IPsec using inline ipsec offload to ethernet devices or
full protocol offload with lookaside crypto devices.
See the :doc:`../prog_guide/rte_security` section of the DPDK Programmers
@@ -207,11 +207,11 @@ New Features
* **Updated the DPAA2_SEC crypto driver to support rte_security.**
Updated the ``dpaa2_sec`` crypto PMD to support ``rte_security`` lookaside
- protocol offload for IPSec.
+ protocol offload for IPsec.
* **Updated the IXGBE ethernet driver to support rte_security.**
- Updated ixgbe ethernet PMD to support ``rte_security`` inline IPSec offload.
+ Updated ixgbe ethernet PMD to support ``rte_security`` inline IPsec offload.
* **Updated i40e driver to support GTP-C/GTP-U.**
@@ -509,7 +509,7 @@ ABI Changes
* **New parameter added to rte_eth_dev.**
A new parameter ``security_ctx`` has been added to ``rte_eth_dev`` to
- support security operations like IPSec inline.
+ support security operations like IPsec inline.
* **New parameter added to rte_cryptodev.**
diff --git a/doc/guides/sample_app_ug/bbdev_app.rst b/doc/guides/sample_app_ug/bbdev_app.rst
index 40a3264..405e706 100644
--- a/doc/guides/sample_app_ug/bbdev_app.rst
+++ b/doc/guides/sample_app_ug/bbdev_app.rst
@@ -68,7 +68,7 @@ The application accepts a number of command line options:
where:
-* ``e ENCODING_CORES``: hexmask for encoding lcored (default = 0x2)
+* ``e ENCODING_CORES``: hexmask for encoding lcores (default = 0x2)
* ``d DECODING_CORES``: hexmask for decoding lcores (default = 0x4)
* ``p ETH_PORT_ID``: ethernet port ID (default = 0)
* ``b BBDEV_ID``: BBDev ID (default = 0)
@@ -87,7 +87,7 @@ issue the command:
$ ./build/bbdev --vdev='baseband_turbo_sw' -w <NIC0PCIADDR> -c 0x38 --socket-mem=2,2 \
--file-prefix=bbdev -- -e 0x10 -d 0x20
-where, NIC0PCIADDR is the PCI addresse of the Rx port
+where, NIC0PCIADDR is the PCI address of the Rx port
This command creates one virtual bbdev devices ``baseband_turbo_sw`` where the
device gets linked to a corresponding ethernet port as whitelisted by
diff --git a/doc/guides/sample_app_ug/eventdev_pipeline.rst b/doc/guides/sample_app_ug/eventdev_pipeline.rst
index 0ec0290..dc7972a 100644
--- a/doc/guides/sample_app_ug/eventdev_pipeline.rst
+++ b/doc/guides/sample_app_ug/eventdev_pipeline.rst
@@ -49,7 +49,7 @@ these settings is shown below:
./build/eventdev_pipeline --vdev event_sw0 -- -r1 -t1 -e4 -w FF00 -s4 -n0 -c32 -W1000 -D
The application has some sanity checking built-in, so if there is a function
-(eg; the RX core) which doesn't have a cpu core mask assigned, the application
+(e.g.; the RX core) which doesn't have a cpu core mask assigned, the application
will print an error message:
.. code-block:: console
diff --git a/doc/guides/sample_app_ug/intro.rst b/doc/guides/sample_app_ug/intro.rst
index 159bcf7..9070419 100644
--- a/doc/guides/sample_app_ug/intro.rst
+++ b/doc/guides/sample_app_ug/intro.rst
@@ -106,7 +106,7 @@ examples are highlighted below.
(packet arrival) and TX (packet transmission) by adding callbacks to the RX
and TX packet processing functions.
-* :doc:`IPSec Security Gateway<ipsec_secgw>`: The IPSec Security
+* :doc:`IPsec Security Gateway<ipsec_secgw>`: The IPsec Security
Gateway application is minimal example of something closer to a real world
example. This is also a good example of an application using the DPDK
Cryptodev framework.
diff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst
index 447a544..4da0fcf 100644
--- a/doc/guides/sample_app_ug/ip_pipeline.rst
+++ b/doc/guides/sample_app_ug/ip_pipeline.rst
@@ -113,7 +113,7 @@ Application stages
Initialization
~~~~~~~~~~~~~~
-During this stage, EAL layer is initialised and application specific arguments are parsed. Furthermore, the data strcutures
+During this stage, EAL layer is initialised and application specific arguments are parsed. Furthermore, the data structures
(i.e. linked lists) for application objects are initialized. In case of any initialization error, an error message
is displayed and the application is terminated.
@@ -185,7 +185,7 @@ Examples
+-----------------------+----------------------+----------------+------------------------------------+
| IP routing | LPM (IPv4) | Forward | 1. Mempool Create |
| | | | 2. Link create |
- | | * Key = IP dest addr | | 3. Pipeline creat |
+ | | * Key = IP dest addr | | 3. Pipeline create |
| | * Offset = 286 | | 4. Pipeline port in/out |
| | * Table size = 4K | | 5. Pipeline table |
| | | | 6. Pipeline port in table |
diff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_app_ug/ipsec_secgw.rst
index 3d784e7..ac118c1 100644
--- a/doc/guides/sample_app_ug/ipsec_secgw.rst
+++ b/doc/guides/sample_app_ug/ipsec_secgw.rst
@@ -25,8 +25,8 @@ The application classifies the ports as *Protected* and *Unprotected*.
Thus, traffic received on an Unprotected or Protected port is consider
Inbound or Outbound respectively.
-The application also supports complete IPSec protocol offload to hardware
-(Look aside crypto accelarator or using ethernet device). It also support
+The application also supports complete IPsec protocol offload to hardware
+(Look aside crypto accelerator or using ethernet device). It also support
inline ipsec processing by the supported ethernet device during transmission.
These modes can be selected during the SA creation configuration.
@@ -124,7 +124,7 @@ Where:
* ``-e``: enables Security Association extended sequence number processing
(available only with librte_ipsec code path).
-* ``-a``: enables Security Association sequence number atomic behaviour
+* ``-a``: enables Security Association sequence number atomic behavior
(available only with librte_ipsec code path).
* ``--config (port,queue,lcore)[,(port,queue,lcore)]``: determines which queues
@@ -752,7 +752,7 @@ DUT OS(NIC1)--(IPsec)-->(NIC1)ipsec-secgw(TAP)--(plain)-->(TAP)SUT OS
SUT OS(TAP)--(plain)-->(TAP)psec-secgw(NIC1)--(IPsec)-->(NIC1)DUT OS
-It then tries to perform some data transfer using the scheme decribed above.
+It then tries to perform some data transfer using the scheme described above.
usage
~~~~~
diff --git a/doc/guides/sample_app_ug/performance_thread.rst b/doc/guides/sample_app_ug/performance_thread.rst
index e2c04ef..ac6ee8a 100644
--- a/doc/guides/sample_app_ug/performance_thread.rst
+++ b/doc/guides/sample_app_ug/performance_thread.rst
@@ -500,8 +500,8 @@ An application may save and retrieve a single pointer to application data in
the L-thread struct.
For legacy and backward compatibility reasons two alternative methods are also
-offered, the first is modelled directly on the pthread get/set specific APIs,
-the second approach is modelled on the ``RTE_PER_LCORE`` macros, whereby
+offered, the first is modeled directly on the pthread get/set specific APIs,
+the second approach is modeled on the ``RTE_PER_LCORE`` macros, whereby
``PER_LTHREAD`` macros are introduced, in both cases the storage is local to
the L-thread.
diff --git a/doc/guides/sample_app_ug/qos_metering.rst b/doc/guides/sample_app_ug/qos_metering.rst
index 2e8e017..d75f7da 100644
--- a/doc/guides/sample_app_ug/qos_metering.rst
+++ b/doc/guides/sample_app_ug/qos_metering.rst
@@ -151,5 +151,5 @@ In this particular case:
* For the rest of the cases, the color is changed to red.
.. note::
- * In color blind mode, first row GREEN colour is only valid.
+ * In color blind mode, first row GREEN color is only valid.
* To drop the packet, policer_table action has to be set to DROP.
diff --git a/doc/guides/sample_app_ug/test_pipeline.rst b/doc/guides/sample_app_ug/test_pipeline.rst
index 5f313c5..5aefd8d 100644
--- a/doc/guides/sample_app_ug/test_pipeline.rst
+++ b/doc/guides/sample_app_ug/test_pipeline.rst
@@ -32,7 +32,7 @@ Compiling the Application
-------------------------
To compile the sample application see :doc:`compiling`
-The application is located in the ``$RTE_SDK/app/test-pipline`` directory.
+The application is located in the ``$RTE_SDK/app/test-pipeline`` directory.
Running the Application
diff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst
index df4d6f9..a71ada6 100644
--- a/doc/guides/sample_app_ug/vhost.rst
+++ b/doc/guides/sample_app_ug/vhost.rst
@@ -116,7 +116,7 @@ will create it. Put simply, it's the server to create the socket file.
The vm2vm parameter sets the mode of packet switching between guests in
the host.
-- 0 disables vm2vm, impling that VM's packets will always go to the NIC port.
+- 0 disables vm2vm, implying that VM's packets will always go to the NIC port.
- 1 means a normal mac lookup packet routing.
- 2 means hardware mode packet forwarding between guests, it allows packets
go to the NIC port, hardware L2 switch will determine which guest the
@@ -148,7 +148,7 @@ default value is 15.
**--dequeue-zero-copy**
Dequeue zero copy will be enabled when this option is given. it is worth to
-note that if NIC is binded to driver with iommu enabled, dequeue zero copy
+note that if NIC is bound to driver with iommu enabled, dequeue zero copy
cannot work at VM2NIC mode (vm2vm=0) due to currently we don't setup iommu
dma mapping for guest memory.
diff --git a/doc/guides/sample_app_ug/vhost_scsi.rst b/doc/guides/sample_app_ug/vhost_scsi.rst
index 7ab7d0d..6b9bf62 100644
--- a/doc/guides/sample_app_ug/vhost_scsi.rst
+++ b/doc/guides/sample_app_ug/vhost_scsi.rst
@@ -63,7 +63,7 @@ Vhost_scsi Common Issues
* vhost_scsi can not start with block size 512 Bytes:
- Currently DPDK vhost library was designed for NET device(althrough the APIs
+ Currently DPDK vhost library was designed for NET device(although the APIs
are generic now), for 512 Bytes block device, Qemu BIOS(x86 BIOS Enhanced
Disk Device) will enumerate all block device and do some IOs to those block
devices with 512 Bytes sector size. DPDK vhost library can not process such
diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst
index 14d432e..109d109 100644
--- a/doc/guides/sample_app_ug/vm_power_management.rst
+++ b/doc/guides/sample_app_ug/vm_power_management.rst
@@ -344,7 +344,7 @@ monitoring of branch ratio on cores doing busy polling via PMDs.
When this parameter is used, the list of cores specified will monitor the ratio
between branch hits and branch misses. A tightly polling PMD thread will have a
- very low branch ratio, so the core frequency will be scaled down to the minimim
+ very low branch ratio, so the core frequency will be scaled down to the minimum
allowed value. When packets are received, the code path will alter, causing the
branch ratio to increase. When the ratio goes above the ratio threshold, the
core frequency will be scaled up to the maximum allowed value.
@@ -384,7 +384,7 @@ the file.
The fifo is at /tmp/powermonitor/fifo
-The jason string can be a policy or instruction, and takes the following
+The JSON string can be a policy or instruction, and takes the following
format:
.. code-block:: javascript
@@ -734,7 +734,7 @@ policy down to the host application. These parameters are as follows:
A comma-separated list of cores in the VM that the user wants the host application to
monitor. The list of cores in any vm starts at zero, and these are mapped to the
physical cores by the host application once the policy is passed down.
- Valid syntax includes individial cores '2,3,4', or a range of cores '2-4', or a
+ Valid syntax includes individual cores '2,3,4', or a range of cores '2-4', or a
combination of both '1,3,5-7'
.. code-block:: console
@@ -742,7 +742,7 @@ policy down to the host application. These parameters are as follows:
--busy-hours {list of busy hours}
A comma-separated list of hours within which to set the core frequency to maximum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console
@@ -750,7 +750,7 @@ policy down to the host application. These parameters are as follows:
--quiet-hours {list of quiet hours}
A comma-separated list of hours within which to set the core frequency to minimum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console
diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
index fdf6ec7..e7db520 100644
--- a/doc/guides/testpmd_app_ug/run_app.rst
+++ b/doc/guides/testpmd_app_ug/run_app.rst
@@ -381,7 +381,7 @@ The command line options are:
* ``--hot-plug``
- Enable device event monitor mechanism for hot plug.
+ Enable device event monitor mechanism for hotplug.
* ``--vxlan-gpe-port=N``
@@ -421,23 +421,23 @@ The command line options are:
* ``--noisy-lkup-memory=N``
- Set the size of the noisy neighbour simulation memory buffer in MB to N.
+ Set the size of the noisy neighbor simulation memory buffer in MB to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-reads=N``
- Set the number of reads to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of reads to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-writes=N``
- Set the number of writes to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of writes to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-reads-writes=N``
- Set the number of r/w accesses to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of r/w accesses to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--no-iova-contig``
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index 5d4dc6f..e602df5 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -303,7 +303,7 @@ The available information categories are:
This is the default mode.
* ``mac``: Changes the source and the destination Ethernet addresses of packets before forwarding them.
- Default application behaviour is to set source Ethernet address to that of the transmitting interface, and destination
+ Default application behavior is to set source Ethernet address to that of the transmitting interface, and destination
address to a dummy value (set during init). The user may specify a target destination Ethernet address via the 'eth-peer' or
'eth-peers-configfile' command-line options. It is not currently possible to specify a specific source Ethernet address.
@@ -326,7 +326,7 @@ The available information categories are:
* ``softnic``: Demonstrates the softnic forwarding operation. In this mode, packet forwarding is
similar to I/O mode except for the fact that packets are loopback to the softnic ports only. Therefore, portmask parameter should be set to softnic port only. The various software based custom NIC pipelines specified through the softnic firmware (DPDK packet framework script) can be tested in this mode. Furthermore, it allows to build 5-level hierarchical QoS scheduler as a default option that can be enabled through CLI once testpmd application is initialised. The user can modify the default scheduler hierarchy or can specify the new QoS Scheduler hierarchy through CLI. Requires ``CONFIG_RTE_LIBRTE_PMD_SOFTNIC=y``.
-* ``noisy``: Noisy neighbour simulation.
+* ``noisy``: Noisy neighbor simulation.
Simulate more realistic behavior of a guest machine engaged in receiving
and sending packets performing Virtual Network Function (VNF).
@@ -2289,7 +2289,7 @@ set bonding lacp dedicated_queue
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enable dedicated tx/rx queues on bonding devices slaves to handle LACP control plane traffic
-when in mode 4 (link-aggregration-802.3ad)::
+when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding lacp dedicated_queues (port_id) (enable|disable)
@@ -2297,7 +2297,7 @@ when in mode 4 (link-aggregration-802.3ad)::
set bonding agg_mode
~~~~~~~~~~~~~~~~~~~~
-Enable one of the specific aggregators mode when in mode 4 (link-aggregration-802.3ad)::
+Enable one of the specific aggregators mode when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding agg_mode (port_id) (bandwidth|count|stable)
@@ -2691,8 +2691,8 @@ where:
* ``shared_shaper_id``: Shared shaper ID to be deleted.
-Set port traffic management hiearchy node private shaper
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Set port traffic management hierarchy node private shaper
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
set the port traffic management hierarchy node private shaper::
@@ -2743,7 +2743,7 @@ Delete the WRED profile::
Add port traffic management hierarchy nonleaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add nonleaf node to port traffic management hiearchy::
+Add nonleaf node to port traffic management hierarchy::
testpmd> add port tm nonleaf node (port_id) (node_id) (parent_node_id) \
(priority) (weight) (level_id) (shaper_profile_id) \
@@ -2758,7 +2758,7 @@ where:
* ``weight``: Node weight (lowest weight is one). The node weight is relative
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
* ``n_sp_priorities``: Number of strict priorities.
@@ -2769,7 +2769,7 @@ where:
Add port traffic management hierarchy leaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add leaf node to port traffic management hiearchy::
+Add leaf node to port traffic management hierarchy::
testpmd> add port tm leaf node (port_id) (node_id) (parent_node_id) \
(priority) (weight) (level_id) (shaper_profile_id) \
@@ -2784,7 +2784,7 @@ where:
* ``weight``: Node weight (lowest weight is one). The node weight is relative
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
* ``cman_mode``: Congestion management mode to be enabled for this node.
@@ -2796,7 +2796,7 @@ where:
Delete port traffic management hierarchy node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Delete node from port traffic management hiearchy::
+Delete node from port traffic management hierarchy::
testpmd> del port tm node (port_id) (node_id)
@@ -3989,7 +3989,7 @@ This section lists supported actions and their attributes, if any.
- ``dec_ttl``: Performs a decrease TTL value action
-- ``set_ttl``: Set TTL value with specificed value
+- ``set_ttl``: Set TTL value with specified value
- ``ttl_value {unsigned}``: The new TTL value to be set
- ``set_mac_src``: set source MAC address
@@ -4522,7 +4522,7 @@ The following sections show functions to load/unload eBPF based filters.
bpf-load
~~~~~~~~
-Load an eBPF program as a callback for partciular RX/TX queue::
+Load an eBPF program as a callback for particular RX/TX queue::
testpmd> bpf-load rx|tx (portid) (queueid) (load-flags) (bpf-prog-filename)
@@ -4560,7 +4560,7 @@ To load (not JITed) t1.o at TX queue 0, port 0::
bpf-unload
~~~~~~~~~~
-Unload previously loaded eBPF program for partciular RX/TX queue::
+Unload previously loaded eBPF program for particular RX/TX queue::
testpmd> bpf-unload rx|tx (portid) (queueid)
diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst
index c366af4..2fc6544 100644
--- a/doc/guides/tools/cryptoperf.rst
+++ b/doc/guides/tools/cryptoperf.rst
@@ -59,7 +59,7 @@ To set on the linearization options add below definition to the
**Step 3: Build the application**
Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the
-``dpdk-test-crypto-perf`` applcation.
+``dpdk-test-crypto-perf`` application.
Initially, the user must select a DPDK target to choose the correct target type
and compiler options to use when building the libraries.
@@ -80,7 +80,7 @@ EAL Options
~~~~~~~~~~~
The following are the EAL command-line options that can be used in conjunction
-with the ``dpdk-test-crypto-perf`` applcation.
+with the ``dpdk-test-crypto-perf`` application.
See the DPDK Getting Started Guides for more information on these options.
* ``-c <COREMASK>`` or ``-l <CORELIST>``
@@ -96,10 +96,10 @@ See the DPDK Getting Started Guides for more information on these options.
Add a virtual device.
-Appication Options
-~~~~~~~~~~~~~~~~~~
+Application Options
+~~~~~~~~~~~~~~~~~~~
-The following are the appication command-line options:
+The following are the application command-line options:
* ``--ptest type``
@@ -338,13 +338,13 @@ Test Vector File
The test vector file is a text file contain information about test vectors.
The file is made of the sections. The first section doesn't have header.
It contain global information used in each test variant vectors -
-typically information about plaintext, ciphertext, cipher key, aut key,
+typically information about plaintext, ciphertext, cipher key, auth key,
initial vector. All other sections begin header.
The sections contain particular information typically digest.
**Format of the file:**
-Each line beginig with sign '#' contain comment and it is ignored by parser::
+Each line beginning with sign '#' contain comment and it is ignored by parser::
# <comment>
@@ -352,16 +352,16 @@ Header line is just name in square bracket::
[<section name>]
-Data line contain information tocken then sign '=' and
+Data line contain information token then sign '=' and
a string of bytes in C byte array format::
- <tocken> = <C byte array>
+ <token> = <C byte array>
-**Tockens list:**
+**Tokens list:**
* ``plaintext``
- Original plaintext to be crypted.
+ Original plaintext to be encrypted.
* ``ciphertext``
diff --git a/doc/guides/tools/proc_info.rst b/doc/guides/tools/proc_info.rst
index 6bdf5a8..2ea1b59 100644
--- a/doc/guides/tools/proc_info.rst
+++ b/doc/guides/tools/proc_info.rst
@@ -44,7 +44,7 @@ If no port mask is specified xstats are reset for all DPDK ports.
**-m**: Print DPDK memory information.
**--show-port**
-The show-port parameter displays port level various configuration informationi
+The show-port parameter displays port level various configuration information
associated to RX port queue pair.
**--show-tm**
@@ -56,7 +56,7 @@ The show-crypto parameter displays available cryptodev configurations,
settings and stats per node.
**--show-ring[=name]**
-The show-ring pararmeter display current allocation of all ring with
+The show-ring parameter display current allocation of all ring with
debug information. Specifying the name allows to display details for specific
ring. For invalid or no ring name, whole list is dump.
@@ -76,7 +76,7 @@ Limitations
* When running ``dpdk-procinfo`` with shared library mode, it is required to
pass the same NIC PMD libraries as used for the primary application. Any
- mismatch in PMD library arguments can lead to undefined behaviour and results
+ mismatch in PMD library arguments can lead to undefined behavior and results
affecting primary application too.
* Stats retrieval using ``dpdk-procinfo`` is not supported for virtual devices like PCAP and TAP.
diff --git a/doc/guides/tools/testbbdev.rst b/doc/guides/tools/testbbdev.rst
index 07da35e..7e6a4db 100644
--- a/doc/guides/tools/testbbdev.rst
+++ b/doc/guides/tools/testbbdev.rst
@@ -139,7 +139,7 @@ There are 6 main test cases that can be executed using testbbdev tool:
* Latency measurement [-c latency]
- Measures the time consumed from the first enqueue until the first
appearance of a dequeued result
- - This measurment represents the full latency of a bbdev operation
+ - This measurement represents the full latency of a bbdev operation
(encode or decode) to execute
* Poll-mode Throughput measurement [-c throughput]
--
2.7.5
^ permalink raw reply [relevance 3%]
* [dpdk-dev] [PATCH v2 1/2] doc: fix spelling errors reported by aspell
2019-04-26 15:14 3% [dpdk-dev] [PATCH v2 1/2] " John McNamara
@ 2019-04-26 15:14 3% ` John McNamara
0 siblings, 0 replies; 140+ results
From: John McNamara @ 2019-04-26 15:14 UTC (permalink / raw)
To: dev; +Cc: John McNamara
Fix spelling errors in the guide docs.
Signed-off-by: John McNamara <john.mcnamara@intel.com>
---
doc/guides/compressdevs/overview.rst | 2 +-
doc/guides/contributing/patches.rst | 2 +-
doc/guides/cryptodevs/aesni_mb.rst | 2 +-
doc/guides/cryptodevs/overview.rst | 2 +-
doc/guides/cryptodevs/scheduler.rst | 2 +-
doc/guides/eventdevs/opdl.rst | 2 +-
doc/guides/eventdevs/sw.rst | 4 ++--
doc/guides/howto/lm_bond_virtio_sriov.rst | 2 +-
doc/guides/howto/lm_virtio_vhost_user.rst | 4 ++--
doc/guides/howto/rte_flow.rst | 6 ++---
doc/guides/howto/telemetry.rst | 2 +-
.../howto/virtio_user_as_exceptional_path.rst | 8 +++----
doc/guides/nics/af_packet.rst | 4 ++--
doc/guides/nics/atlantic.rst | 2 +-
doc/guides/nics/cxgbe.rst | 4 ++--
doc/guides/nics/dpaa.rst | 2 +-
doc/guides/nics/dpaa2.rst | 2 +-
doc/guides/nics/ena.rst | 2 +-
doc/guides/nics/enetc.rst | 2 +-
doc/guides/nics/enic.rst | 2 +-
doc/guides/nics/features.rst | 2 +-
doc/guides/nics/i40e.rst | 2 +-
doc/guides/nics/ixgbe.rst | 4 ++--
doc/guides/nics/kni.rst | 2 +-
doc/guides/nics/mlx4.rst | 2 +-
doc/guides/nics/mlx5.rst | 4 ++--
doc/guides/nics/mvpp2.rst | 2 +-
doc/guides/nics/netvsc.rst | 2 +-
doc/guides/nics/nfb.rst | 2 +-
doc/guides/nics/nfp.rst | 4 ++--
doc/guides/nics/sfc_efx.rst | 14 +++++------
doc/guides/nics/szedata2.rst | 2 +-
doc/guides/nics/tap.rst | 2 +-
doc/guides/platform/dpaa.rst | 4 ++--
doc/guides/platform/dpaa2.rst | 4 ++--
doc/guides/prog_guide/bbdev.rst | 4 ++--
doc/guides/prog_guide/compressdev.rst | 6 ++---
doc/guides/prog_guide/cryptodev_lib.rst | 12 +++++-----
doc/guides/prog_guide/dev_kit_build_system.rst | 2 +-
doc/guides/prog_guide/efd_lib.rst | 2 +-
doc/guides/prog_guide/env_abstraction_layer.rst | 2 +-
.../prog_guide/event_ethernet_rx_adapter.rst | 6 ++---
doc/guides/prog_guide/eventdev.rst | 6 ++---
doc/guides/prog_guide/ipsec_lib.rst | 16 ++++++-------
doc/guides/prog_guide/kernel_nic_interface.rst | 2 +-
doc/guides/prog_guide/metrics_lib.rst | 2 +-
doc/guides/prog_guide/multi_proc_support.rst | 2 +-
doc/guides/prog_guide/profile_app.rst | 4 ++--
doc/guides/prog_guide/rte_flow.rst | 8 +++----
doc/guides/prog_guide/rte_security.rst | 20 ++++++++--------
doc/guides/prog_guide/traffic_management.rst | 2 +-
doc/guides/prog_guide/vhost_lib.rst | 2 +-
doc/guides/rawdevs/ifpga_rawdev.rst | 2 +-
doc/guides/rel_notes/known_issues.rst | 8 +++----
doc/guides/rel_notes/release_17_11.rst | 10 ++++----
doc/guides/sample_app_ug/bbdev_app.rst | 4 ++--
doc/guides/sample_app_ug/eventdev_pipeline.rst | 2 +-
doc/guides/sample_app_ug/intro.rst | 2 +-
doc/guides/sample_app_ug/ip_pipeline.rst | 4 ++--
doc/guides/sample_app_ug/ipsec_secgw.rst | 8 +++----
doc/guides/sample_app_ug/performance_thread.rst | 4 ++--
doc/guides/sample_app_ug/qos_metering.rst | 2 +-
doc/guides/sample_app_ug/test_pipeline.rst | 2 +-
doc/guides/sample_app_ug/vhost.rst | 4 ++--
doc/guides/sample_app_ug/vhost_scsi.rst | 2 +-
doc/guides/sample_app_ug/vm_power_management.rst | 10 ++++----
doc/guides/testpmd_app_ug/run_app.rst | 10 ++++----
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 28 +++++++++++-----------
doc/guides/tools/cryptoperf.rst | 22 ++++++++---------
doc/guides/tools/proc_info.rst | 6 ++---
doc/guides/tools/testbbdev.rst | 2 +-
71 files changed, 170 insertions(+), 170 deletions(-)
diff --git a/doc/guides/compressdevs/overview.rst b/doc/guides/compressdevs/overview.rst
index 70bbe82..809e4e6 100644
--- a/doc/guides/compressdevs/overview.rst
+++ b/doc/guides/compressdevs/overview.rst
@@ -18,7 +18,7 @@ Supported Feature Flags
without making any modifications to it (no compression done).
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means PMD supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index d8404e6..3b2b174 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -8,7 +8,7 @@ Contributing Code to DPDK
This document outlines the guidelines for submitting code to DPDK.
-The DPDK development process is modelled (loosely) on the Linux Kernel development model so it is worth reading the
+The DPDK development process is modeled (loosely) on the Linux Kernel development model so it is worth reading the
Linux kernel guide on submitting patches:
`How to Get Your Change Into the Linux Kernel <https://www.kernel.org/doc/html/latest/process/submitting-patches.html>`_.
The rationale for many of the DPDK guidelines is explained in greater detail in the kernel guidelines.
diff --git a/doc/guides/cryptodevs/aesni_mb.rst b/doc/guides/cryptodevs/aesni_mb.rst
index 8915201..1eff2b0 100644
--- a/doc/guides/cryptodevs/aesni_mb.rst
+++ b/doc/guides/cryptodevs/aesni_mb.rst
@@ -129,7 +129,7 @@ Extra notes
For AES Counter mode (AES-CTR), the library supports two different sizes for Initialization
Vector (IV):
-* 12 bytes: used mainly for IPSec, as it requires 12 bytes from the user, which internally
+* 12 bytes: used mainly for IPsec, as it requires 12 bytes from the user, which internally
are appended the counter block (4 bytes), which is set to 1 for the first block
(no padding required from the user)
diff --git a/doc/guides/cryptodevs/overview.rst b/doc/guides/cryptodevs/overview.rst
index 12f342b..a972c79 100644
--- a/doc/guides/cryptodevs/overview.rst
+++ b/doc/guides/cryptodevs/overview.rst
@@ -18,7 +18,7 @@ Supported Feature Flags
being the operation in-place (input address = output address).
- "OOP SGL In SGL Out" feature flag stands for
- "Out-of-place Scatter-gather list Input, Scatter-gater list Output",
+ "Out-of-place Scatter-gather list Input, Scatter-gather list Output",
which means pmd supports different scatter-gather styled input and output buffers
(i.e. both can consists of multiple segments).
diff --git a/doc/guides/cryptodevs/scheduler.rst b/doc/guides/cryptodevs/scheduler.rst
index a754a27..7004ca4 100644
--- a/doc/guides/cryptodevs/scheduler.rst
+++ b/doc/guides/cryptodevs/scheduler.rst
@@ -165,7 +165,7 @@ operation:
For pure small packet size (64 bytes) traffic however the multi-core mode is not
an optimal solution, as it doesn't give significant per-core performance improvement.
For mixed traffic (IMIX) the optimal number of worker cores is around 2-3.
- For large packets (1.5 Kbytes) scheduler shows linear scaling in performance
+ For large packets (1.5 kbytes) scheduler shows linear scaling in performance
up to eight cores.
Each worker uses its own slave cryptodev. Only software cryptodevs
are supported. Only the same type of cryptodevs should be used concurrently.
diff --git a/doc/guides/eventdevs/opdl.rst b/doc/guides/eventdevs/opdl.rst
index 0262a33..979f6cd 100644
--- a/doc/guides/eventdevs/opdl.rst
+++ b/doc/guides/eventdevs/opdl.rst
@@ -8,7 +8,7 @@ The OPDL (Ordered Packet Distribution Library) eventdev is a specific\
implementation of the eventdev API. It is particularly suited to packet\
processing workloads that have high throughput and low latency requirements.\
All packets follow the same path through the device. The order in which\
-packets follow is determinted by the order in which queues are set up.\
+packets follow is determined by the order in which queues are set up.\
Events are left on the ring until they are transmitted. As a result packets\
do not go out of order
diff --git a/doc/guides/eventdevs/sw.rst b/doc/guides/eventdevs/sw.rst
index afdcad7..04c8b03 100644
--- a/doc/guides/eventdevs/sw.rst
+++ b/doc/guides/eventdevs/sw.rst
@@ -70,7 +70,7 @@ Credit Quanta
The credit quanta is the number of credits that a port will fetch at a time from
the instance's credit pool. Higher numbers will cause less overhead in the
atomic credit fetch code, however it also reduces the overall number of credits
-in the system faster. A balanced number (eg 32) ensures that only small numbers
+in the system faster. A balanced number (e.g. 32) ensures that only small numbers
of credits are pre-allocated at a time, while also mitigating performance impact
of the atomics.
@@ -100,7 +100,7 @@ feature would be significant.
~~~~~~~~~~~~~~~~~~
The software eventdev does not support creating queues that handle all types of
-traffic. An eventdev with this capability allows enqueueing Atomic, Ordered and
+traffic. An eventdev with this capability allows enqueuing Atomic, Ordered and
Parallel traffic to the same queue, but scheduling each of them appropriately.
The reason to not allow Atomic, Ordered and Parallel event types in the
diff --git a/doc/guides/howto/lm_bond_virtio_sriov.rst b/doc/guides/howto/lm_bond_virtio_sriov.rst
index ee8ccda..07563b3 100644
--- a/doc/guides/howto/lm_bond_virtio_sriov.rst
+++ b/doc/guides/howto/lm_bond_virtio_sriov.rst
@@ -328,7 +328,7 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
testpmd> show bonding config 2
testpmd> port attach 0000:00:04.0
diff --git a/doc/guides/howto/lm_virtio_vhost_user.rst b/doc/guides/howto/lm_virtio_vhost_user.rst
index 6ebc10f..ecb7832 100644
--- a/doc/guides/howto/lm_virtio_vhost_user.rst
+++ b/doc/guides/howto/lm_virtio_vhost_user.rst
@@ -243,7 +243,7 @@ On host_server_2: Terminal 1
.. code-block:: console
- testomd> show port info all
+ testpmd> show port info all
testpmd> show port stats all
Virtio traffic is seen at P0 and P1.
@@ -338,7 +338,7 @@ reset_vf_on_212_131.sh
#!/bin/sh
# This script is run on the host 10.237.212.131 to reset SRIOV
- # BDF for Ninatic NIC is 0000:06:00.0
+ # BDF for Niantic NIC is 0000:06:00.0
cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
echo 0 > /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
diff --git a/doc/guides/howto/rte_flow.rst b/doc/guides/howto/rte_flow.rst
index 3dcda6c..e197376 100644
--- a/doc/guides/howto/rte_flow.rst
+++ b/doc/guides/howto/rte_flow.rst
@@ -23,7 +23,7 @@ In this example we will create a simple rule that drops packets whose IPv4
destination equals 192.168.3.2. This code is equivalent to the following
testpmd command (wrapped for clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst is 192.168.3.2 / end actions drop / end
Code
@@ -118,7 +118,7 @@ a mask.
This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan /
+ testpmd> flow create 0 ingress pattern eth / vlan /
ipv4 dst spec 192.168.3.0 dst mask 255.255.255.0 /
end actions drop / end
@@ -219,7 +219,7 @@ In this example we will create a rule that routes all vlan id 123 to queue 3.
This code is equivalent to the following testpmd command (wrapped for
clarity)::
- tpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
+ testpmd> flow create 0 ingress pattern eth / vlan vid spec 123 /
end actions queue index 3 / end
Code
diff --git a/doc/guides/howto/telemetry.rst b/doc/guides/howto/telemetry.rst
index 00f8f7a..e10804d 100644
--- a/doc/guides/howto/telemetry.rst
+++ b/doc/guides/howto/telemetry.rst
@@ -18,7 +18,7 @@ which acts as the client.
In DPDK, applications are used to initialize the ``telemetry``. To view incoming
traffic on featured ports, the application should be run first (ie. after ports
are configured). Once the application is running, the service assurance agent
-(for example the collectd plugin) should be run to begin querying the API.
+(for example the CollectD plugin) should be run to begin querying the API.
A client connects their Service Assurance application to the DPDK application
via a UNIX socket. Once a connection is established, a client can send JSON
diff --git a/doc/guides/howto/virtio_user_as_exceptional_path.rst b/doc/guides/howto/virtio_user_as_exceptional_path.rst
index 4910c12..ec021af 100644
--- a/doc/guides/howto/virtio_user_as_exceptional_path.rst
+++ b/doc/guides/howto/virtio_user_as_exceptional_path.rst
@@ -1,7 +1,7 @@
.. SPDX-License-Identifier: BSD-3-Clause
Copyright(c) 2016 Intel Corporation.
-.. _virtio_user_as_excpetional_path:
+.. _virtio_user_as_exceptional_path:
Virtio_user as Exceptional Path
===============================
@@ -22,7 +22,7 @@ solution is very promising in:
* Features
vhost-net is born to be a networking solution, which has lots of networking
- related featuers, like multi queue, tso, multi-seg mbuf, etc.
+ related features, like multi queue, tso, multi-seg mbuf, etc.
* Performance
@@ -38,7 +38,7 @@ in :numref:`figure_virtio_user_as_exceptional_path`.
.. figure:: img/virtio_user_as_exceptional_path.*
- Overview of a DPDK app using virtio-user as excpetional path
+ Overview of a DPDK app using virtio-user as exceptional path
Sample Usage
@@ -75,7 +75,7 @@ compiling the kernel and those kernel modules should be inserted.
* ``queues``
- Number of multi-queues. Each qeueue will be served by a kthread. For example:
+ Number of multi-queues. Each queue will be served by a kthread. For example:
.. code-block:: console
diff --git a/doc/guides/nics/af_packet.rst b/doc/guides/nics/af_packet.rst
index 1260bb2..efd6f1c 100644
--- a/doc/guides/nics/af_packet.rst
+++ b/doc/guides/nics/af_packet.rst
@@ -13,13 +13,13 @@ PACKET_MMAP, which provides a mmap'ed ring buffer, shared between user space
and kernel, that's used to send and receive packets. This helps reducing system
calls and the copies needed between user space and Kernel.
-The PACKET_FANOUT_HASH behaviour of AF_PACKET is used for frame reception.
+The PACKET_FANOUT_HASH behavior of AF_PACKET is used for frame reception.
Options and inherent limitations
--------------------------------
The following options can be provided to set up an af_packet port in DPDK.
-Some of these, in turn, will be used to configure the PAKET_MMAP settings.
+Some of these, in turn, will be used to configure the PACKET_MMAP settings.
* ``iface`` - name of the Kernel interface to attach to (required);
* ``qpairs`` - number of Rx and Tx queues (optional, default 1);
diff --git a/doc/guides/nics/atlantic.rst b/doc/guides/nics/atlantic.rst
index 22f2410..3f3f294 100644
--- a/doc/guides/nics/atlantic.rst
+++ b/doc/guides/nics/atlantic.rst
@@ -18,7 +18,7 @@ Supported features
- Port statistics
- RSS (Receive Side Scaling)
- Checksum offload
-- Jumbo Frame upto 16K
+- Jumbo Frame up to 16K
- MACSEC offload
Experimental API features
diff --git a/doc/guides/nics/cxgbe.rst b/doc/guides/nics/cxgbe.rst
index f3e6115..7a893cc 100644
--- a/doc/guides/nics/cxgbe.rst
+++ b/doc/guides/nics/cxgbe.rst
@@ -126,7 +126,7 @@ enabling debugging options may affect system performance.
- ``CONFIG_RTE_LIBRTE_CXGBE_TPUT`` (default **y**)
- Toggle behaviour to prefer Throughput or Latency.
+ Toggle behavior to prefer Throughput or Latency.
Runtime Options
~~~~~~~~~~~~~~~
@@ -140,7 +140,7 @@ be passed as part of EAL arguments. For example,
- ``keep_ovlan`` (default **0**)
- Toggle behaviour to keep/strip outer VLAN in Q-in-Q packets. If
+ Toggle behavior to keep/strip outer VLAN in Q-in-Q packets. If
enabled, the outer VLAN tag is preserved in Q-in-Q packets. Otherwise,
the outer VLAN tag is stripped in Q-in-Q packets.
diff --git a/doc/guides/nics/dpaa.rst b/doc/guides/nics/dpaa.rst
index fb7bc7d..2243a4a 100644
--- a/doc/guides/nics/dpaa.rst
+++ b/doc/guides/nics/dpaa.rst
@@ -251,7 +251,7 @@ state during application initialization:
automatically be assigned from the these high perf PUSH queues. Any queue
configuration beyond that will be standard Rx queues. The application can
choose to change their number if HW portals are limited.
- The valid values are from '0' to '4'. The valuse shall be set to '0' if the
+ The valid values are from '0' to '4'. The values shall be set to '0' if the
application want to use eventdev with DPAA device.
diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst
index d74d8f8..b3b7678 100644
--- a/doc/guides/nics/dpaa2.rst
+++ b/doc/guides/nics/dpaa2.rst
@@ -379,7 +379,7 @@ active -- Ethernet, crypto, compression, etc.
DPBP based Mempool driver
~~~~~~~~~~~~~~~~~~~~~~~~~
-The DPBP driver is bound to a DPBP objects and provides sevices to
+The DPBP driver is bound to a DPBP objects and provides services to
create a hardware offloaded packet buffer mempool.
DPAA2 NIC Driver
diff --git a/doc/guides/nics/ena.rst b/doc/guides/nics/ena.rst
index 80da4b6..d44f3cd 100644
--- a/doc/guides/nics/ena.rst
+++ b/doc/guides/nics/ena.rst
@@ -189,7 +189,7 @@ Prerequisites
reduces the latency of the packets by pushing the header directly through
the PCI to the device, before the DMA is even triggered. For proper work
kernel PCI driver must support write combining (WC). In mainline version of
- ``igb_uio`` (in DPDK repo) it must be enabled by loding module with
+ ``igb_uio`` (in DPDK repo) it must be enabled by loading module with
``wc_activate=1`` flag (example below). However, mainline's vfio-pci
driver in kernel doesn't have WC support yet (planed to be added).
If vfio-pci used user should be either turn off ENAv2 (to avoid performance
diff --git a/doc/guides/nics/enetc.rst b/doc/guides/nics/enetc.rst
index 2620460..3c896ee 100644
--- a/doc/guides/nics/enetc.rst
+++ b/doc/guides/nics/enetc.rst
@@ -76,7 +76,7 @@ Supported ENETC SoCs
Prerequisites
~~~~~~~~~~~~~
-There are three main pre-requisities for executing ENETC PMD on a ENETC
+There are three main pre-requisites for executing ENETC PMD on a ENETC
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/nics/enic.rst b/doc/guides/nics/enic.rst
index 726a69e..cdb55e0 100644
--- a/doc/guides/nics/enic.rst
+++ b/doc/guides/nics/enic.rst
@@ -224,7 +224,7 @@ the use of SR-IOV.
passthrough devices do not require libvirt, port profiles, and VM-FEX.
-.. _enic-genic-flow-api:
+.. _enic-generic-flow-api:
Generic Flow API support
------------------------
diff --git a/doc/guides/nics/features.rst b/doc/guides/nics/features.rst
index c5bf322..d57ddc2 100644
--- a/doc/guides/nics/features.rst
+++ b/doc/guides/nics/features.rst
@@ -495,7 +495,7 @@ Supports adding traffic mirroring rules.
Inline crypto
-------------
-Supports inline crypto processing (eg. inline IPsec). See Security library and PMD documentation for more details.
+Supports inline crypto processing (e.g. inline IPsec). See Security library and PMD documentation for more details.
* **[uses] rte_eth_rxconf,rte_eth_rxmode**: ``offloads:DEV_RX_OFFLOAD_SECURITY``,
* **[uses] rte_eth_txconf,rte_eth_txmode**: ``offloads:DEV_TX_OFFLOAD_SECURITY``.
diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 9680a92..2e9ec79 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -580,7 +580,7 @@ bandwidth setting.
TC TX scheduling mode setting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-There're 2 TX scheduling modes for TCs, round robin and strict priority mode.
+There are 2 TX scheduling modes for TCs, round robin and strict priority mode.
If a TC is set to strict priority mode, it can consume unlimited bandwidth.
It means if APP has set the max bandwidth for that TC, it comes to no
effect.
diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
index 1c294b0..975143f 100644
--- a/doc/guides/nics/ixgbe.rst
+++ b/doc/guides/nics/ixgbe.rst
@@ -203,8 +203,8 @@ as a workaround.
X550 does not support legacy interrupt mode
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Desccription
-^^^^^^^^^^^^
+Description
+^^^^^^^^^^^
X550 cannot get interrupts if using ``uio_pci_generic`` module or using legacy
interrupt mode of ``igb_uio`` or ``vfio``. Because the errata of X550 states
that the Interrupt Status bit is not implemented. The errata is the item #22
diff --git a/doc/guides/nics/kni.rst b/doc/guides/nics/kni.rst
index a66c595..602a06b 100644
--- a/doc/guides/nics/kni.rst
+++ b/doc/guides/nics/kni.rst
@@ -65,7 +65,7 @@ backend device by default.
PMD arguments
-------------
-``no_request_thread``, by default PMD creates a phtread for each KNI interface
+``no_request_thread``, by default PMD creates a pthread for each KNI interface
to handle Linux network interface control commands, like ``ifconfig kni0 up``
With ``no_request_thread`` option, pthread is not created and control commands
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index aaf1907..f6d7a16 100644
--- a/doc/guides/nics/mlx4.rst
+++ b/doc/guides/nics/mlx4.rst
@@ -83,7 +83,7 @@ These options can be modified in the ``.config`` file.
- ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
- Embed static flavour of the dependencies **libibverbs** and **libmlx4**
+ Embed static flavor of the dependencies **libibverbs** and **libmlx4**
in the PMD shared library or the executable static binary.
- ``CONFIG_RTE_LIBRTE_MLX4_DEBUG`` (default **n**)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 5fa6b62..af1e408 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -168,7 +168,7 @@ Limitations
- must specify the VXLAN item with tunnel outer parameters.
- must specify the tunnel outer VNI in the VXLAN item.
- must specify the tunnel outer remote (destination) UDP port in the VXLAN item.
- - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interace, wildcards not allowed.
+ - must specify the tunnel outer local (source) IPv4 or IPv6 in the , this address will locally (with scope link) assigned to the outer network interface, wildcards not allowed.
- must specify the tunnel outer remote (destination) IPv4 or IPv6 in the VXLAN item, group IPs allowed.
- must specify the tunnel outer destination MAC address in the VXLAN item, this address will be used to create neigh rule.
@@ -216,7 +216,7 @@ These options can be modified in the ``.config`` file.
- ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**)
- Embed static flavour of the dependencies **libibverbs** and **libmlx5**
+ Embed static flavor of the dependencies **libibverbs** and **libmlx5**
in the PMD shared library or the executable static binary.
- ``CONFIG_RTE_LIBRTE_MLX5_DEBUG`` (default **n**)
diff --git a/doc/guides/nics/mvpp2.rst b/doc/guides/nics/mvpp2.rst
index 09e2f2a..bacc013 100644
--- a/doc/guides/nics/mvpp2.rst
+++ b/doc/guides/nics/mvpp2.rst
@@ -91,7 +91,7 @@ Limitations
chance to start in a sane state.
- MUSDK architecture does not support changing configuration in run time.
- All nessesary configurations should be done before first dev_start().
+ All necessary configurations should be done before first dev_start().
- RX queue start/stop is not supported.
diff --git a/doc/guides/nics/netvsc.rst b/doc/guides/nics/netvsc.rst
index 87fabf5..6dbb9a5 100644
--- a/doc/guides/nics/netvsc.rst
+++ b/doc/guides/nics/netvsc.rst
@@ -89,7 +89,7 @@ operations:
.. Note::
- The dpkd-devbind.py script can not be used since it only handles PCI devices.
+ The dpdk-devbind.py script can not be used since it only handles PCI devices.
Prerequisites
diff --git a/doc/guides/nics/nfb.rst b/doc/guides/nics/nfb.rst
index a7fb963..8df76c0 100644
--- a/doc/guides/nics/nfb.rst
+++ b/doc/guides/nics/nfb.rst
@@ -81,7 +81,7 @@ The NFB cards are multi-port multi-queue cards, where (generally) data from any
Ethernet port may be sent to any queue.
They are represented in DPDK as a single port.
-NFB-200G2QL card employs an addon cable which allows to connect it to two
+NFB-200G2QL card employs an add-on cable which allows to connect it to two
physical PCI-E slots at the same time (see the diagram below).
This is done to allow 200 Gbps of traffic to be transferred through the PCI-E
bus (note that a single PCI-E 3.0 x16 slot provides only 125 Gbps theoretical
diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst
index 09a8529..309fa5d 100644
--- a/doc/guides/nics/nfp.rst
+++ b/doc/guides/nics/nfp.rst
@@ -149,8 +149,8 @@ PF multiprocess support
-----------------------
Due to how the driver needs to access the NFP through a CPP interface, which implies
-to use specific registers inside the chip, the number of secondary proceses with PF
-ports is limitted to only one.
+to use specific registers inside the chip, the number of secondary processes with PF
+ports is limited to only one.
This limitation will be solved in future versions but having basic multiprocess support
is important for allowing development and debugging through the PF using a secondary
diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst
index eb47f25..6d01d05 100644
--- a/doc/guides/nics/sfc_efx.rst
+++ b/doc/guides/nics/sfc_efx.rst
@@ -96,7 +96,7 @@ Non-supported Features
The features not yet supported include:
-- Receive queue interupts
+- Receive queue interrupts
- Priority-based flow control
@@ -209,12 +209,12 @@ Validating flow rules depends on the firmware variant.
The :ref:`flow_isolated_mode` is supported.
-Ethernet destinaton individual/group match
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Ethernet destination individual/group match
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ethernet item supports I/G matching, if only the corresponding bit is set
-in the mask of destination address. If destinaton address in the spec is
-multicast, it matches all multicast (and broadcast) packets, oherwise it
+in the mask of destination address. If destination address in the spec is
+multicast, it matches all multicast (and broadcast) packets, otherwise it
matches unicast packets that are not filtered by other flow rules.
Exceptions to flow rules
@@ -348,10 +348,10 @@ boolean parameters value.
- ``perf_profile`` [auto|throughput|low-latency] (default **throughput**)
- Choose hardware tunning to be optimized for either throughput or
+ Choose hardware tuning to be optimized for either throughput or
low-latency.
**auto** allows NIC firmware to make a choice based on
- installed licences and firmware variant configured using **sfboot**.
+ installed licenses and firmware variant configured using **sfboot**.
- ``stats_update_period_ms`` [long] (default **1000**)
diff --git a/doc/guides/nics/szedata2.rst b/doc/guides/nics/szedata2.rst
index a2092f9..94dba82 100644
--- a/doc/guides/nics/szedata2.rst
+++ b/doc/guides/nics/szedata2.rst
@@ -89,7 +89,7 @@ The NFB cards are multi-port multi-queue cards, where (generally) data from any
Ethernet port may be sent to any queue.
They were historically represented in DPDK as a single port.
-However, the new NFB-200G2QL card employs an addon cable which allows to connect
+However, the new NFB-200G2QL card employs an add-on cable which allows to connect
it to two physical PCI-E slots at the same time (see the diagram below).
This is done to allow 200 Gbps of traffic to be transferred through the PCI-E
bus (note that a single PCI-E 3.0 x16 slot provides only 125 Gbps theoretical
diff --git a/doc/guides/nics/tap.rst b/doc/guides/nics/tap.rst
index 063bd0b..4b6d77d 100644
--- a/doc/guides/nics/tap.rst
+++ b/doc/guides/nics/tap.rst
@@ -40,7 +40,7 @@ actual MAC address: ``00:64:74:61:70:[00-FF]``.
--vdev=net_tap0,mac="00:64:74:61:70:11"
The MAC address will have a user value passed as string. The MAC address is in
-format with delimeter ``:``. The string is byte converted to hex and you get
+format with delimiter ``:``. The string is byte converted to hex and you get
the actual MAC address: ``00:64:74:61:70:11``.
It is possible to specify a remote netdevice to capture packets from by adding
diff --git a/doc/guides/platform/dpaa.rst b/doc/guides/platform/dpaa.rst
index 3904871..6005f22 100644
--- a/doc/guides/platform/dpaa.rst
+++ b/doc/guides/platform/dpaa.rst
@@ -4,7 +4,7 @@
NXP QorIQ DPAA Board Support Package
====================================
-This doc has information about steps to setup QorIq dpaa
+This doc has information about steps to setup QorIQ dpaa
based layerscape platform and information about common offload
hw block drivers of **NXP QorIQ DPAA** SoC family.
@@ -38,7 +38,7 @@ Common Offload HW Block Drivers
Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA PMD on a DPAA
+There are four main pre-requisites for executing DPAA PMD on a DPAA
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/platform/dpaa2.rst b/doc/guides/platform/dpaa2.rst
index 5a64406..2586af0 100644
--- a/doc/guides/platform/dpaa2.rst
+++ b/doc/guides/platform/dpaa2.rst
@@ -4,7 +4,7 @@
NXP QorIQ DPAA2 Board Support Package
=====================================
-This doc has information about steps to setup NXP QoriQ DPAA2 platform
+This doc has information about steps to setup NXP QorIQ DPAA2 platform
and information about common offload hw block drivers of
**NXP QorIQ DPAA2** SoC family.
@@ -48,7 +48,7 @@ Common Offload HW Block Drivers
Steps To Setup Platform
-----------------------
-There are four main pre-requisities for executing DPAA2 PMD on a DPAA2
+There are four main pre-requisites for executing DPAA2 PMD on a DPAA2
compatible board:
1. **ARM 64 Tool Chain**
diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index 9de1444..658ffd4 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -78,7 +78,7 @@ From the application point of view, each instance of a bbdev device consists of
one or more queues identified by queue IDs. While different devices may have
different capabilities (e.g. support different operation types), all queues on
a device support identical configuration possibilities. A queue is configured
-for only one type of operation and is configured at initializations time.
+for only one type of operation and is configured at initialization time.
When an operation is enqueued to a specific queue ID, the result is dequeued
from the same queue ID.
@@ -678,7 +678,7 @@ bbdev framework, by giving a sample code performing a loop-back operation with a
baseband processor capable of transceiving data packets.
The following sample C-like pseudo-code shows the basic steps to encode several
-buffers using (**sw_trubo**) bbdev PMD.
+buffers using (**sw_turbo**) bbdev PMD.
.. code-block:: c
diff --git a/doc/guides/prog_guide/compressdev.rst b/doc/guides/prog_guide/compressdev.rst
index ad97037..a06c835 100644
--- a/doc/guides/prog_guide/compressdev.rst
+++ b/doc/guides/prog_guide/compressdev.rst
@@ -17,7 +17,7 @@ Device Creation
Physical compression devices are discovered during the bus probe of the EAL function
which is executed at DPDK initialization, based on their unique device identifier.
-For eg. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
+For e.g. PCI devices can be identified using PCI BDF (bus/bridge, device, function).
Specific physical compression devices, like other physical devices in DPDK can be
white-listed or black-listed using the EAL command line options.
@@ -379,7 +379,7 @@ using priv_xform would look like:
setup op->m_src and op->m_dst;
}
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, comp_ops, NUM_OPS);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deque = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, NUM_OPS);
} while (num_dqud < num_enqd);
@@ -526,7 +526,7 @@ An example pseudocode to set up and process a stream having NUM_CHUNKS with each
op->src.length = CHUNK_LEN;
op->input_chksum = 0;
num_enqd = rte_compressdev_enqueue_burst(cdev_id, 0, &op[i], 1);
- /* wait for this to complete before enqueing next*/
+ /* wait for this to complete before enqueuing next*/
do {
num_deqd = rte_compressdev_dequeue_burst(cdev_id, 0 , &processed_ops, 1);
} while (num_deqd < num_enqd);
diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst
index 74a930b..23fa5bc 100644
--- a/doc/guides/prog_guide/cryptodev_lib.rst
+++ b/doc/guides/prog_guide/cryptodev_lib.rst
@@ -14,7 +14,7 @@ and AEAD symmetric and asymmetric Crypto operations.
Design Principles
-----------------
-The cryptodev library follows the same basic principles as those used in DPDKs
+The cryptodev library follows the same basic principles as those used in DPDK's
Ethernet Device framework. The Crypto framework provides a generic Crypto device
framework which supports both physical (hardware) and virtual (software) Crypto
devices as well as a generic Crypto API which allows Crypto devices to be
@@ -48,7 +48,7 @@ From the command line using the --vdev EAL option
* If DPDK application requires multiple software crypto PMD devices then required
number of ``--vdev`` with appropriate libraries are to be added.
- * An Application with crypto PMD instaces sharing the same library requires unique ID.
+ * An Application with crypto PMD instances sharing the same library requires unique ID.
Example: ``--vdev 'crypto_aesni_mb0' --vdev 'crypto_aesni_mb1'``
@@ -396,7 +396,7 @@ Operation Management and Allocation
The cryptodev library provides an API set for managing Crypto operations which
utilize the Mempool Library to allocate operation buffers. Therefore, it ensures
-that the crytpo operation is interleaved optimally across the channels and
+that the crypto operation is interleaved optimally across the channels and
ranks for optimal processing.
A ``rte_crypto_op`` contains a field indicating the pool that it originated from.
When calling ``rte_crypto_op_free(op)``, the operation returns to its original pool.
@@ -602,7 +602,7 @@ Sample code
There are various sample applications that show how to use the cryptodev library,
such as the L2fwd with Crypto sample application (L2fwd-crypto) and
-the IPSec Security Gateway application (ipsec-secgw).
+the IPsec Security Gateway application (ipsec-secgw).
While these applications demonstrate how an application can be created to perform
generic crypto operation, the required complexity hides the basic steps of
@@ -807,7 +807,7 @@ using one of the crypto PMDs available in DPDK.
/*
* Dequeue the crypto operations until all the operations
- * are proccessed in the crypto device.
+ * are processed in the crypto device.
*/
uint16_t num_dequeued_ops, total_num_dequeued_ops = 0;
do {
@@ -886,7 +886,7 @@ the order in which the transforms are passed indicates the order of the chaining
Not all asymmetric crypto xforms are supported for chaining. Currently supported
asymmetric crypto chaining is Diffie-Hellman private key generation followed by
public generation. Also, currently API does not support chaining of symmetric and
-asymmetric crypto xfroms.
+asymmetric crypto xforms.
Each xform defines specific asymmetric crypto algo. Currently supported are:
* RSA
diff --git a/doc/guides/prog_guide/dev_kit_build_system.rst b/doc/guides/prog_guide/dev_kit_build_system.rst
index 96dbf30..74dba4d 100644
--- a/doc/guides/prog_guide/dev_kit_build_system.rst
+++ b/doc/guides/prog_guide/dev_kit_build_system.rst
@@ -204,7 +204,7 @@ Creates the following symbol:
Which ``dpdk-pmdinfogen`` scans for. Using this information other relevant
bits of data can be exported from the object file and used to produce a
hardware support description, that ``dpdk-pmdinfogen`` then encodes into a
-json formatted string in the following format:
+JSON formatted string in the following format:
.. code-block:: c
diff --git a/doc/guides/prog_guide/efd_lib.rst b/doc/guides/prog_guide/efd_lib.rst
index cb1a1df..2b355ff 100644
--- a/doc/guides/prog_guide/efd_lib.rst
+++ b/doc/guides/prog_guide/efd_lib.rst
@@ -423,6 +423,6 @@ References
1- EFD is based on collaborative research work between Intel and
Carnegie Mellon University (CMU), interested readers can refer to the paper
-“Scaling Up Clustered Network Appliances with ScaleBricks;” Dong Zhou et al.
+"Scaling Up Clustered Network Appliances with ScaleBricks" Dong Zhou et al.
at SIGCOMM 2015 (`http://conferences.sigcomm.org/sigcomm/2015/pdf/papers/p241.pdf`)
for more information.
diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index fa8afdb..c27f730 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -733,7 +733,7 @@ The most important fields in the structure and how they are used are described b
Malloc heap is a doubly-linked list, where each element keeps track of its
previous and next elements. Due to the fact that hugepage memory can come and
-go, neighbouring malloc elements may not necessarily be adjacent in memory.
+go, neighboring malloc elements may not necessarily be adjacent in memory.
Also, since a malloc element may span multiple pages, its contents may not
necessarily be IOVA-contiguous either - each malloc element is only guaranteed
to be virtually contiguous.
diff --git a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
index e955299..c7dda92 100644
--- a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
+++ b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
@@ -162,7 +162,7 @@ The servicing_weight member of struct rte_event_eth_rx_adapter_queue_conf
is applicable when the adapter uses a service core function. The application
has to enable Rx queue interrupts when configuring the ethernet device
using the ``rte_eth_dev_configure()`` function and then use a servicing_weight
-of zero when addding the Rx queue to the adapter.
+of zero when adding the Rx queue to the adapter.
The adapter creates a thread blocked on the interrupt, on an interrupt this
thread enqueues the port id and the queue id to a ring buffer. The adapter
@@ -180,9 +180,9 @@ Rx Callback for SW Rx Adapter
For SW based packet transfers, i.e., when the
``RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT`` is not set in the adapter's
capabilities flags for a particular ethernet device, the service function
-temporarily enqueues mbufs to an event buffer before batch enqueueing these
+temporarily enqueues mbufs to an event buffer before batch enqueuing these
to the event device. If the buffer fills up, the service function stops
-dequeueing packets from the ethernet device. The application may want to
+dequeuing packets from the ethernet device. The application may want to
monitor the buffer fill level and instruct the service function to selectively
enqueue packets to the event device. The application may also use some other
criteria to decide which packets should enter the event device even when
diff --git a/doc/guides/prog_guide/eventdev.rst b/doc/guides/prog_guide/eventdev.rst
index dcdfeb7..7ea14ba 100644
--- a/doc/guides/prog_guide/eventdev.rst
+++ b/doc/guides/prog_guide/eventdev.rst
@@ -42,7 +42,7 @@ The rte_event structure contains the following metadata fields, which the
application fills in to have the event scheduled as required:
* ``flow_id`` - The targeted flow identifier for the enq/deq operation.
-* ``event_type`` - The source of this event, eg RTE_EVENT_TYPE_ETHDEV or CPU.
+* ``event_type`` - The source of this event, e.g. RTE_EVENT_TYPE_ETHDEV or CPU.
* ``sub_event_type`` - Distinguishes events inside the application, that have
the same event_type (see above)
* ``op`` - This field takes one of the RTE_EVENT_OP_* values, and tells the
@@ -265,7 +265,7 @@ Linking Queues and Ports
The final step is to "wire up" the ports to the queues. After this, the
eventdev is capable of scheduling events, and when cores request work to do,
the correct events are provided to that core. Note that the RX core takes input
-from eg: a NIC so it is not linked to any eventdev queues.
+from e.g.: a NIC so it is not linked to any eventdev queues.
Linking all workers to atomic queues, and the TX core to the single-link queue
can be achieved like this:
@@ -276,7 +276,7 @@ can be achieved like this:
uint8_t tx_port_id = 5;
uint8_t atomic_qs[] = {0, 1};
uint8_t single_link_q = 2;
- uin8t_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
+ uint8t_t priority = RTE_EVENT_DEV_PRIORITY_NORMAL;
for(int worker_port_id = 1; worker_port_id <= 4; worker_port_id++) {
int links_made = rte_event_port_link(dev_id, worker_port_id, atomic_qs, NULL, 2);
diff --git a/doc/guides/prog_guide/ipsec_lib.rst b/doc/guides/prog_guide/ipsec_lib.rst
index 84696d4..6fc0888 100644
--- a/doc/guides/prog_guide/ipsec_lib.rst
+++ b/doc/guides/prog_guide/ipsec_lib.rst
@@ -65,7 +65,7 @@ In that mode the library functions perform
- check SQN
- prepare *rte_crypto_op* structure for each input packet
- - verify that integity check and decryption performed by crypto device
+ - verify that integrity check and decryption performed by crypto device
completed successfully
- check padding data
- remove outer IP header (tunnel mode) / update IP header (transport mode)
@@ -88,7 +88,7 @@ In that mode the library functions perform
* for inbound packets:
- - verify that integity check and decryption performed by *rte_security*
+ - verify that integrity check and decryption performed by *rte_security*
device completed successfully
- check SQN
- check padding data
@@ -101,10 +101,10 @@ In that mode the library functions perform
- generate SQN and IV
- add outer IP header (tunnel mode) / update IP header (transport mode)
- add ESP header and trailer, padding and IV data
- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
inline-crypto processing has to be performed by HW on this packet
- invoke *rte_security* device specific *set_pkt_metadata()* to associate
- secuirty device specific data with the packet
+ security device specific data with the packet
RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -113,15 +113,15 @@ In that mode the library functions perform
* for inbound packets:
- - verify that integity check and decryption performed by *rte_security*
+ - verify that integrity check and decryption performed by *rte_security*
device completed successfully
* for outbound packets:
- - update *ol_flags* inside *struct rte_mbuf* to inidicate that
+ - update *ol_flags* inside *struct rte_mbuf* to indicate that
inline-crypto processing has to be performed by HW on this packet
- invoke *rte_security* device specific *set_pkt_metadata()* to associate
- secuirty device specific data with the packet
+ security device specific data with the packet
RTE_SECURITY_ACTION_TYPE_LOOKASIDE_PROTOCOL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -131,7 +131,7 @@ In that mode the library functions perform
* for inbound packets:
- prepare *rte_crypto_op* structure for each input packet
- - verify that integity check and decryption performed by crypto device
+ - verify that integrity check and decryption performed by crypto device
completed successfully
* for outbound packets:
diff --git a/doc/guides/prog_guide/kernel_nic_interface.rst b/doc/guides/prog_guide/kernel_nic_interface.rst
index 7fcbd93..daf87f4 100644
--- a/doc/guides/prog_guide/kernel_nic_interface.rst
+++ b/doc/guides/prog_guide/kernel_nic_interface.rst
@@ -227,7 +227,7 @@ application functions:
``config_promiscusity``:
- Called when the user changes the promiscusity state of the KNI
+ Called when the user changes the promiscuity state of the KNI
interface. For example, when the user runs ``ip link set promisc
[on|off] dev <ifaceX>``. If the user sets this callback function to
NULL, but sets the ``port_id`` field to a value other than -1, a default
diff --git a/doc/guides/prog_guide/metrics_lib.rst b/doc/guides/prog_guide/metrics_lib.rst
index e68e4e7..89bc7d6 100644
--- a/doc/guides/prog_guide/metrics_lib.rst
+++ b/doc/guides/prog_guide/metrics_lib.rst
@@ -25,7 +25,7 @@ individual device. Since the metrics library is self-contained, the only
restriction on port numbers is that they are less than ``RTE_MAX_ETHPORTS``
- there is no requirement for the ports to actually exist.
-Initialising the library
+Initializing the library
------------------------
Before the library can be used, it has to be initialized by calling
diff --git a/doc/guides/prog_guide/multi_proc_support.rst b/doc/guides/prog_guide/multi_proc_support.rst
index 1384fe3..6196d3f 100644
--- a/doc/guides/prog_guide/multi_proc_support.rst
+++ b/doc/guides/prog_guide/multi_proc_support.rst
@@ -273,7 +273,7 @@ will be populated by IPC are as follows:
those peer processes that were active at the time of request, how many have
replied)
* ``msgs`` - pointer to where all of the responses are stored. The order in
- which responses appear is undefined. Whendoing sycnrhonous requests, this
+ which responses appear is undefined. When doing synchronous requests, this
memory must be freed by the requestor after request completes!
For asynchronous requests, a function pointer to the callback function must be
diff --git a/doc/guides/prog_guide/profile_app.rst b/doc/guides/prog_guide/profile_app.rst
index 5af795c..a36ebef 100644
--- a/doc/guides/prog_guide/profile_app.rst
+++ b/doc/guides/prog_guide/profile_app.rst
@@ -64,7 +64,7 @@ The default ``cntvct_el0`` based ``rte_rdtsc()`` provides a portable means to
get a wall clock counter in user space. Typically it runs at <= 100MHz.
The alternative method to enable ``rte_rdtsc()`` for a high resolution wall
-clock counter is through the armv8 PMU subsystem. The PMU cycle counter runs
+clock counter is through the ARMv8 PMU subsystem. The PMU cycle counter runs
at CPU frequency. However, access to the PMU cycle counter from user space is
not enabled by default in the arm64 linux kernel. It is possible to enable
cycle counter for user space access by configuring the PMU from the privileged
@@ -75,7 +75,7 @@ scheme. Application can choose the PMU based implementation with
``CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU``.
The example below shows the steps to configure the PMU based cycle counter on
-an armv8 machine.
+an ARMv8 machine.
.. code-block:: console
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 0203f4f..937f52b 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2129,7 +2129,7 @@ as defined in the ``rte_flow_action_raw_decap``
This action modifies the payload of matched flows. The data supplied must
be a valid header, either holding layer 2 data in case of removing layer 2
-before eincapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
+before encapsulation of layer 3 tunnel (for example MPLSoGRE) or complete
tunnel definition starting from layer 2 and moving to the tunnel item itself.
When applied to the original packet the resulting packet must be a
valid packet.
@@ -2279,7 +2279,7 @@ Action: ``DEC_TTL``
Decrease TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_dec_ttl:
@@ -2297,7 +2297,7 @@ Action: ``SET_TTL``
Assigns a new TTL value.
If there is no valid RTE_FLOW_ITEM_TYPE_IPV4 or RTE_FLOW_ITEM_TYPE_IPV6
-in pattern, Some PMDs will reject rule because behaviour will be undefined.
+in pattern, Some PMDs will reject rule because behavior will be undefined.
.. _table_rte_flow_action_set_ttl:
@@ -2725,7 +2725,7 @@ Caveats
- API operations are synchronous and blocking (``EAGAIN`` cannot be
returned).
-- There is no provision for reentrancy/multi-thread safety, although nothing
+- There is no provision for re-entrancy/multi-thread safety, although nothing
should prevent different devices from being configured at the same
time. PMDs may protect their control path functions accordingly.
diff --git a/doc/guides/prog_guide/rte_security.rst b/doc/guides/prog_guide/rte_security.rst
index cb70caa..7d0734a 100644
--- a/doc/guides/prog_guide/rte_security.rst
+++ b/doc/guides/prog_guide/rte_security.rst
@@ -40,7 +40,7 @@ Inline Crypto
~~~~~~~~~~~~~
RTE_SECURITY_ACTION_TYPE_INLINE_CRYPTO:
-The crypto processing for security protocol (e.g. IPSec) is processed
+The crypto processing for security protocol (e.g. IPsec) is processed
inline during receive and transmission on NIC port. The flow based
security action should be configured on the port.
@@ -48,7 +48,7 @@ Ingress Data path - The packet is decrypted in RX path and relevant
crypto status is set in Rx descriptors. After the successful inline
crypto processing the packet is presented to host as a regular Rx packet
however all security protocol related headers are still attached to the
-packet. e.g. In case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. In case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will remain in the packet but the received packet
contains the decrypted data where the encrypted data was when the packet
arrived. The driver Rx path check the descriptors and and based on the
@@ -111,7 +111,7 @@ Inline protocol offload
~~~~~~~~~~~~~~~~~~~~~~~
RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL:
-The crypto and protocol processing for security protocol (e.g. IPSec)
+The crypto and protocol processing for security protocol (e.g. IPsec)
is processed inline during receive and transmission. The flow based
security action should be configured on the port.
@@ -119,7 +119,7 @@ Ingress Data path - The packet is decrypted in the RX path and relevant
crypto status is set in the Rx descriptors. After the successful inline
crypto processing the packet is presented to the host as a regular Rx packet
but all security protocol related headers are optionally removed from the
-packet. e.g. in the case of IPSec, the IPSec tunnel headers (if any),
+packet. e.g. in the case of IPsec, the IPsec tunnel headers (if any),
ESP/AH headers will be removed from the packet and the received packet
will contains the decrypted packet only. The driver Rx path checks the
descriptors and based on the crypto status sets additional flags in
@@ -132,7 +132,7 @@ to identify the security processing done on the packet.
The underlying device in this case is stateful. It is expected that
the device shall support crypto processing for all kind of packets matching
to a given flow, this includes fragmented packets (post reassembly).
- E.g. in case of IPSec the device may internally manage anti-replay etc.
+ E.g. in case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in the descriptor.
@@ -150,7 +150,7 @@ to cross the MTU size.
.. note::
The underlying device will manage state information required for egress
- processing. E.g. in case of IPSec, the seq number will be added to the
+ processing. E.g. in case of IPsec, the seq number will be added to the
packet, however the device shall provide indication when the sequence number
is about to overflow. The underlying device may support post encryption TSO.
@@ -199,13 +199,13 @@ crypto device.
Decryption: The packet is sent to the crypto device for security
protocol processing. The device will decrypt the packet and it will also
optionally remove additional security headers from the packet.
-E.g. in case of IPSec, IPSec tunnel headers (if any), ESP/AH headers
+E.g. in case of IPsec, IPsec tunnel headers (if any), ESP/AH headers
will be removed from the packet and the decrypted packet may contain
plain data only.
.. note::
- In case of IPSec the device may internally manage anti-replay etc.
+ In case of IPsec the device may internally manage anti-replay etc.
It will provide a configuration option for anti-replay behavior i.e. to drop
the packets or pass them to driver with error flags set in descriptor.
@@ -217,7 +217,7 @@ for any protocol header addition.
.. note::
- In the case of IPSec, the seq number will be added to the packet,
+ In the case of IPsec, the seq number will be added to the packet,
It shall provide an indication when the sequence number is about to
overflow.
@@ -549,7 +549,7 @@ IPsec related configuration parameters are defined in ``rte_security_ipsec_xform
struct rte_security_ipsec_sa_options options;
/**< various SA options */
enum rte_security_ipsec_sa_direction direction;
- /**< IPSec SA Direction - Egress/Ingress */
+ /**< IPsec SA Direction - Egress/Ingress */
enum rte_security_ipsec_sa_protocol proto;
/**< IPsec SA Protocol - AH/ESP */
enum rte_security_ipsec_sa_mode mode;
diff --git a/doc/guides/prog_guide/traffic_management.rst b/doc/guides/prog_guide/traffic_management.rst
index 98ac431..05b34d9 100644
--- a/doc/guides/prog_guide/traffic_management.rst
+++ b/doc/guides/prog_guide/traffic_management.rst
@@ -39,7 +39,7 @@ whether a specific implementation does meet the needs to the user application.
At the TM level, users can get high level idea with the help of various
parameters such as maximum number of nodes, maximum number of hierarchical
levels, maximum number of shapers, maximum number of private shapers, type of
-scheduling algorithm (Strict Priority, Weighted Fair Queueing , etc.), etc.,
+scheduling algorithm (Strict Priority, Weighted Fair Queuing , etc.), etc.,
supported by the implementation.
Likewise, users can query the capability of the TM at the hierarchical level to
diff --git a/doc/guides/prog_guide/vhost_lib.rst b/doc/guides/prog_guide/vhost_lib.rst
index a86c07a..fc3ee43 100644
--- a/doc/guides/prog_guide/vhost_lib.rst
+++ b/doc/guides/prog_guide/vhost_lib.rst
@@ -63,7 +63,7 @@ The following is an overview of some key Vhost API functions:
512).
* zero copy is really good for VM2VM case. For iperf between two VMs, the
- boost could be above 70% (when TSO is enableld).
+ boost could be above 70% (when TSO is enabled).
* For zero copy in VM2NIC case, guest Tx used vring may be starved if the
PMD driver consume the mbuf but not release them timely.
diff --git a/doc/guides/rawdevs/ifpga_rawdev.rst b/doc/guides/rawdevs/ifpga_rawdev.rst
index d400db6..a3d92a6 100644
--- a/doc/guides/rawdevs/ifpga_rawdev.rst
+++ b/doc/guides/rawdevs/ifpga_rawdev.rst
@@ -91,7 +91,7 @@ Run-time parameters
-------------------
This driver is invoked automatically in systems added with Intel FPGA,
-but PR and IFPGA Bus scan is trigged by command line using
+but PR and IFPGA Bus scan is triggered by command line using
``--vdev 'ifpga_rawdev_cfg`` EAL option.
The following device parameters are supported:
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 358dfa3..276327c 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -676,7 +676,7 @@ igb uio legacy mode can not be used in X710/XL710/XXV710
**Description**:
X710/XL710/XXV710 NICs lack support for indicating INTx is asserted via the interrupt
- bit in the PCI status register. Linux delected them from INTx support table. The related
+ bit in the PCI status register. Linux deleted them from INTx support table. The related
`commit <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/pci/quirks.c?id=8bcf4525c5d43306c5fd07e132bc8650e3491aec>`_.
**Implication**:
@@ -722,9 +722,9 @@ Linux kernel 4.10.0 iommu attribute read error
**Description**:
When VT-d is enabled (``iommu=pt intel_iommu=on``), reading IOMMU attributes from
/sys/devices/virtual/iommu/dmarXXX/intel-iommu/cap on Linux kernel 4.10.0 error.
- This bug is fixed in `Linux commmit a7fdb6e648fb
+ This bug is fixed in `Linux commit a7fdb6e648fb
<https://patchwork.kernel.org/patch/9595727/>`_,
- This bug is introduced in `Linux commmit 39ab9555c241
+ This bug is introduced in `Linux commit 39ab9555c241
<https://patchwork.kernel.org/patch/9554403/>`_,
**Implication**:
@@ -842,7 +842,7 @@ AVX-512 support disabled
drop.
On DPDK v19.02 ``AVX-512`` disable scope is reduced to ``GCC`` and ``binutils version 2.30`` based
- on information accured from the GCC community defect.
+ on information accrued from the GCC community defect.
**Reason**:
Generated ``AVX-512`` code cause crash:
diff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/release_17_11.rst
index 2a93af3..6448b6c 100644
--- a/doc/guides/rel_notes/release_17_11.rst
+++ b/doc/guides/rel_notes/release_17_11.rst
@@ -168,7 +168,7 @@ New Features
* The DES CBC algorithm.
* The DES DOCSIS BPI algorithm.
- This change requires version 0.47 of the IPSec Multi-buffer library. For
+ This change requires version 0.47 of the IPsec Multi-buffer library. For
more details see the :doc:`../cryptodevs/aesni_mb` documentation.
* **Updated the OpenSSL PMD.**
@@ -198,7 +198,7 @@ New Features
* **Added the Security Offload Library.**
Added an experimental library - ``rte_security``. This provide security APIs
- for protocols like IPSec using inline ipsec offload to ethernet devices or
+ for protocols like IPsec using inline ipsec offload to ethernet devices or
full protocol offload with lookaside crypto devices.
See the :doc:`../prog_guide/rte_security` section of the DPDK Programmers
@@ -207,11 +207,11 @@ New Features
* **Updated the DPAA2_SEC crypto driver to support rte_security.**
Updated the ``dpaa2_sec`` crypto PMD to support ``rte_security`` lookaside
- protocol offload for IPSec.
+ protocol offload for IPsec.
* **Updated the IXGBE ethernet driver to support rte_security.**
- Updated ixgbe ethernet PMD to support ``rte_security`` inline IPSec offload.
+ Updated ixgbe ethernet PMD to support ``rte_security`` inline IPsec offload.
* **Updated i40e driver to support GTP-C/GTP-U.**
@@ -509,7 +509,7 @@ ABI Changes
* **New parameter added to rte_eth_dev.**
A new parameter ``security_ctx`` has been added to ``rte_eth_dev`` to
- support security operations like IPSec inline.
+ support security operations like IPsec inline.
* **New parameter added to rte_cryptodev.**
diff --git a/doc/guides/sample_app_ug/bbdev_app.rst b/doc/guides/sample_app_ug/bbdev_app.rst
index 40a3264..405e706 100644
--- a/doc/guides/sample_app_ug/bbdev_app.rst
+++ b/doc/guides/sample_app_ug/bbdev_app.rst
@@ -68,7 +68,7 @@ The application accepts a number of command line options:
where:
-* ``e ENCODING_CORES``: hexmask for encoding lcored (default = 0x2)
+* ``e ENCODING_CORES``: hexmask for encoding lcores (default = 0x2)
* ``d DECODING_CORES``: hexmask for decoding lcores (default = 0x4)
* ``p ETH_PORT_ID``: ethernet port ID (default = 0)
* ``b BBDEV_ID``: BBDev ID (default = 0)
@@ -87,7 +87,7 @@ issue the command:
$ ./build/bbdev --vdev='baseband_turbo_sw' -w <NIC0PCIADDR> -c 0x38 --socket-mem=2,2 \
--file-prefix=bbdev -- -e 0x10 -d 0x20
-where, NIC0PCIADDR is the PCI addresse of the Rx port
+where, NIC0PCIADDR is the PCI address of the Rx port
This command creates one virtual bbdev devices ``baseband_turbo_sw`` where the
device gets linked to a corresponding ethernet port as whitelisted by
diff --git a/doc/guides/sample_app_ug/eventdev_pipeline.rst b/doc/guides/sample_app_ug/eventdev_pipeline.rst
index 0ec0290..dc7972a 100644
--- a/doc/guides/sample_app_ug/eventdev_pipeline.rst
+++ b/doc/guides/sample_app_ug/eventdev_pipeline.rst
@@ -49,7 +49,7 @@ these settings is shown below:
./build/eventdev_pipeline --vdev event_sw0 -- -r1 -t1 -e4 -w FF00 -s4 -n0 -c32 -W1000 -D
The application has some sanity checking built-in, so if there is a function
-(eg; the RX core) which doesn't have a cpu core mask assigned, the application
+(e.g.; the RX core) which doesn't have a cpu core mask assigned, the application
will print an error message:
.. code-block:: console
diff --git a/doc/guides/sample_app_ug/intro.rst b/doc/guides/sample_app_ug/intro.rst
index 159bcf7..9070419 100644
--- a/doc/guides/sample_app_ug/intro.rst
+++ b/doc/guides/sample_app_ug/intro.rst
@@ -106,7 +106,7 @@ examples are highlighted below.
(packet arrival) and TX (packet transmission) by adding callbacks to the RX
and TX packet processing functions.
-* :doc:`IPSec Security Gateway<ipsec_secgw>`: The IPSec Security
+* :doc:`IPsec Security Gateway<ipsec_secgw>`: The IPsec Security
Gateway application is minimal example of something closer to a real world
example. This is also a good example of an application using the DPDK
Cryptodev framework.
diff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst
index 447a544..4da0fcf 100644
--- a/doc/guides/sample_app_ug/ip_pipeline.rst
+++ b/doc/guides/sample_app_ug/ip_pipeline.rst
@@ -113,7 +113,7 @@ Application stages
Initialization
~~~~~~~~~~~~~~
-During this stage, EAL layer is initialised and application specific arguments are parsed. Furthermore, the data strcutures
+During this stage, EAL layer is initialised and application specific arguments are parsed. Furthermore, the data structures
(i.e. linked lists) for application objects are initialized. In case of any initialization error, an error message
is displayed and the application is terminated.
@@ -185,7 +185,7 @@ Examples
+-----------------------+----------------------+----------------+------------------------------------+
| IP routing | LPM (IPv4) | Forward | 1. Mempool Create |
| | | | 2. Link create |
- | | * Key = IP dest addr | | 3. Pipeline creat |
+ | | * Key = IP dest addr | | 3. Pipeline create |
| | * Offset = 286 | | 4. Pipeline port in/out |
| | * Table size = 4K | | 5. Pipeline table |
| | | | 6. Pipeline port in table |
diff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_app_ug/ipsec_secgw.rst
index 3d784e7..ac118c1 100644
--- a/doc/guides/sample_app_ug/ipsec_secgw.rst
+++ b/doc/guides/sample_app_ug/ipsec_secgw.rst
@@ -25,8 +25,8 @@ The application classifies the ports as *Protected* and *Unprotected*.
Thus, traffic received on an Unprotected or Protected port is consider
Inbound or Outbound respectively.
-The application also supports complete IPSec protocol offload to hardware
-(Look aside crypto accelarator or using ethernet device). It also support
+The application also supports complete IPsec protocol offload to hardware
+(Look aside crypto accelerator or using ethernet device). It also support
inline ipsec processing by the supported ethernet device during transmission.
These modes can be selected during the SA creation configuration.
@@ -124,7 +124,7 @@ Where:
* ``-e``: enables Security Association extended sequence number processing
(available only with librte_ipsec code path).
-* ``-a``: enables Security Association sequence number atomic behaviour
+* ``-a``: enables Security Association sequence number atomic behavior
(available only with librte_ipsec code path).
* ``--config (port,queue,lcore)[,(port,queue,lcore)]``: determines which queues
@@ -752,7 +752,7 @@ DUT OS(NIC1)--(IPsec)-->(NIC1)ipsec-secgw(TAP)--(plain)-->(TAP)SUT OS
SUT OS(TAP)--(plain)-->(TAP)psec-secgw(NIC1)--(IPsec)-->(NIC1)DUT OS
-It then tries to perform some data transfer using the scheme decribed above.
+It then tries to perform some data transfer using the scheme described above.
usage
~~~~~
diff --git a/doc/guides/sample_app_ug/performance_thread.rst b/doc/guides/sample_app_ug/performance_thread.rst
index e2c04ef..ac6ee8a 100644
--- a/doc/guides/sample_app_ug/performance_thread.rst
+++ b/doc/guides/sample_app_ug/performance_thread.rst
@@ -500,8 +500,8 @@ An application may save and retrieve a single pointer to application data in
the L-thread struct.
For legacy and backward compatibility reasons two alternative methods are also
-offered, the first is modelled directly on the pthread get/set specific APIs,
-the second approach is modelled on the ``RTE_PER_LCORE`` macros, whereby
+offered, the first is modeled directly on the pthread get/set specific APIs,
+the second approach is modeled on the ``RTE_PER_LCORE`` macros, whereby
``PER_LTHREAD`` macros are introduced, in both cases the storage is local to
the L-thread.
diff --git a/doc/guides/sample_app_ug/qos_metering.rst b/doc/guides/sample_app_ug/qos_metering.rst
index 2e8e017..d75f7da 100644
--- a/doc/guides/sample_app_ug/qos_metering.rst
+++ b/doc/guides/sample_app_ug/qos_metering.rst
@@ -151,5 +151,5 @@ In this particular case:
* For the rest of the cases, the color is changed to red.
.. note::
- * In color blind mode, first row GREEN colour is only valid.
+ * In color blind mode, first row GREEN color is only valid.
* To drop the packet, policer_table action has to be set to DROP.
diff --git a/doc/guides/sample_app_ug/test_pipeline.rst b/doc/guides/sample_app_ug/test_pipeline.rst
index 5f313c5..5aefd8d 100644
--- a/doc/guides/sample_app_ug/test_pipeline.rst
+++ b/doc/guides/sample_app_ug/test_pipeline.rst
@@ -32,7 +32,7 @@ Compiling the Application
-------------------------
To compile the sample application see :doc:`compiling`
-The application is located in the ``$RTE_SDK/app/test-pipline`` directory.
+The application is located in the ``$RTE_SDK/app/test-pipeline`` directory.
Running the Application
diff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst
index df4d6f9..a71ada6 100644
--- a/doc/guides/sample_app_ug/vhost.rst
+++ b/doc/guides/sample_app_ug/vhost.rst
@@ -116,7 +116,7 @@ will create it. Put simply, it's the server to create the socket file.
The vm2vm parameter sets the mode of packet switching between guests in
the host.
-- 0 disables vm2vm, impling that VM's packets will always go to the NIC port.
+- 0 disables vm2vm, implying that VM's packets will always go to the NIC port.
- 1 means a normal mac lookup packet routing.
- 2 means hardware mode packet forwarding between guests, it allows packets
go to the NIC port, hardware L2 switch will determine which guest the
@@ -148,7 +148,7 @@ default value is 15.
**--dequeue-zero-copy**
Dequeue zero copy will be enabled when this option is given. it is worth to
-note that if NIC is binded to driver with iommu enabled, dequeue zero copy
+note that if NIC is bound to driver with iommu enabled, dequeue zero copy
cannot work at VM2NIC mode (vm2vm=0) due to currently we don't setup iommu
dma mapping for guest memory.
diff --git a/doc/guides/sample_app_ug/vhost_scsi.rst b/doc/guides/sample_app_ug/vhost_scsi.rst
index 7ab7d0d..6b9bf62 100644
--- a/doc/guides/sample_app_ug/vhost_scsi.rst
+++ b/doc/guides/sample_app_ug/vhost_scsi.rst
@@ -63,7 +63,7 @@ Vhost_scsi Common Issues
* vhost_scsi can not start with block size 512 Bytes:
- Currently DPDK vhost library was designed for NET device(althrough the APIs
+ Currently DPDK vhost library was designed for NET device(although the APIs
are generic now), for 512 Bytes block device, Qemu BIOS(x86 BIOS Enhanced
Disk Device) will enumerate all block device and do some IOs to those block
devices with 512 Bytes sector size. DPDK vhost library can not process such
diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst
index 14d432e..109d109 100644
--- a/doc/guides/sample_app_ug/vm_power_management.rst
+++ b/doc/guides/sample_app_ug/vm_power_management.rst
@@ -344,7 +344,7 @@ monitoring of branch ratio on cores doing busy polling via PMDs.
When this parameter is used, the list of cores specified will monitor the ratio
between branch hits and branch misses. A tightly polling PMD thread will have a
- very low branch ratio, so the core frequency will be scaled down to the minimim
+ very low branch ratio, so the core frequency will be scaled down to the minimum
allowed value. When packets are received, the code path will alter, causing the
branch ratio to increase. When the ratio goes above the ratio threshold, the
core frequency will be scaled up to the maximum allowed value.
@@ -384,7 +384,7 @@ the file.
The fifo is at /tmp/powermonitor/fifo
-The jason string can be a policy or instruction, and takes the following
+The JSON string can be a policy or instruction, and takes the following
format:
.. code-block:: javascript
@@ -734,7 +734,7 @@ policy down to the host application. These parameters are as follows:
A comma-separated list of cores in the VM that the user wants the host application to
monitor. The list of cores in any vm starts at zero, and these are mapped to the
physical cores by the host application once the policy is passed down.
- Valid syntax includes individial cores '2,3,4', or a range of cores '2-4', or a
+ Valid syntax includes individual cores '2,3,4', or a range of cores '2-4', or a
combination of both '1,3,5-7'
.. code-block:: console
@@ -742,7 +742,7 @@ policy down to the host application. These parameters are as follows:
--busy-hours {list of busy hours}
A comma-separated list of hours within which to set the core frequency to maximum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console
@@ -750,7 +750,7 @@ policy down to the host application. These parameters are as follows:
--quiet-hours {list of quiet hours}
A comma-separated list of hours within which to set the core frequency to minimum.
- Valid syntax includes individial hours '2,3,4', or a range of hours '2-4', or a
+ Valid syntax includes individual hours '2,3,4', or a range of hours '2-4', or a
combination of both '1,3,5-7'. Valid hours are 0 to 23.
.. code-block:: console
diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
index fdf6ec7..e7db520 100644
--- a/doc/guides/testpmd_app_ug/run_app.rst
+++ b/doc/guides/testpmd_app_ug/run_app.rst
@@ -381,7 +381,7 @@ The command line options are:
* ``--hot-plug``
- Enable device event monitor mechanism for hot plug.
+ Enable device event monitor mechanism for hotplug.
* ``--vxlan-gpe-port=N``
@@ -421,23 +421,23 @@ The command line options are:
* ``--noisy-lkup-memory=N``
- Set the size of the noisy neighbour simulation memory buffer in MB to N.
+ Set the size of the noisy neighbor simulation memory buffer in MB to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-reads=N``
- Set the number of reads to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of reads to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-writes=N``
- Set the number of writes to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of writes to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--noisy-lkup-num-reads-writes=N``
- Set the number of r/w accesses to be done in noisy neighbour simulation memory buffer to N.
+ Set the number of r/w accesses to be done in noisy neighbor simulation memory buffer to N.
Only available with the noisy forwarding mode. The default value is 0.
* ``--no-iova-contig``
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index 5d4dc6f..e602df5 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -303,7 +303,7 @@ The available information categories are:
This is the default mode.
* ``mac``: Changes the source and the destination Ethernet addresses of packets before forwarding them.
- Default application behaviour is to set source Ethernet address to that of the transmitting interface, and destination
+ Default application behavior is to set source Ethernet address to that of the transmitting interface, and destination
address to a dummy value (set during init). The user may specify a target destination Ethernet address via the 'eth-peer' or
'eth-peers-configfile' command-line options. It is not currently possible to specify a specific source Ethernet address.
@@ -326,7 +326,7 @@ The available information categories are:
* ``softnic``: Demonstrates the softnic forwarding operation. In this mode, packet forwarding is
similar to I/O mode except for the fact that packets are loopback to the softnic ports only. Therefore, portmask parameter should be set to softnic port only. The various software based custom NIC pipelines specified through the softnic firmware (DPDK packet framework script) can be tested in this mode. Furthermore, it allows to build 5-level hierarchical QoS scheduler as a default option that can be enabled through CLI once testpmd application is initialised. The user can modify the default scheduler hierarchy or can specify the new QoS Scheduler hierarchy through CLI. Requires ``CONFIG_RTE_LIBRTE_PMD_SOFTNIC=y``.
-* ``noisy``: Noisy neighbour simulation.
+* ``noisy``: Noisy neighbor simulation.
Simulate more realistic behavior of a guest machine engaged in receiving
and sending packets performing Virtual Network Function (VNF).
@@ -2289,7 +2289,7 @@ set bonding lacp dedicated_queue
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enable dedicated tx/rx queues on bonding devices slaves to handle LACP control plane traffic
-when in mode 4 (link-aggregration-802.3ad)::
+when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding lacp dedicated_queues (port_id) (enable|disable)
@@ -2297,7 +2297,7 @@ when in mode 4 (link-aggregration-802.3ad)::
set bonding agg_mode
~~~~~~~~~~~~~~~~~~~~
-Enable one of the specific aggregators mode when in mode 4 (link-aggregration-802.3ad)::
+Enable one of the specific aggregators mode when in mode 4 (link-aggregation-802.3ad)::
testpmd> set bonding agg_mode (port_id) (bandwidth|count|stable)
@@ -2691,8 +2691,8 @@ where:
* ``shared_shaper_id``: Shared shaper ID to be deleted.
-Set port traffic management hiearchy node private shaper
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Set port traffic management hierarchy node private shaper
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
set the port traffic management hierarchy node private shaper::
@@ -2743,7 +2743,7 @@ Delete the WRED profile::
Add port traffic management hierarchy nonleaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add nonleaf node to port traffic management hiearchy::
+Add nonleaf node to port traffic management hierarchy::
testpmd> add port tm nonleaf node (port_id) (node_id) (parent_node_id) \
(priority) (weight) (level_id) (shaper_profile_id) \
@@ -2758,7 +2758,7 @@ where:
* ``weight``: Node weight (lowest weight is one). The node weight is relative
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
* ``n_sp_priorities``: Number of strict priorities.
@@ -2769,7 +2769,7 @@ where:
Add port traffic management hierarchy leaf node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Add leaf node to port traffic management hiearchy::
+Add leaf node to port traffic management hierarchy::
testpmd> add port tm leaf node (port_id) (node_id) (parent_node_id) \
(priority) (weight) (level_id) (shaper_profile_id) \
@@ -2784,7 +2784,7 @@ where:
* ``weight``: Node weight (lowest weight is one). The node weight is relative
to the weight sum of all siblings that have the same priority. It is used by
the WFQ algorithm running on the parent node for scheduling this node.
-* ``level_id``: Hiearchy level of the node.
+* ``level_id``: Hierarchy level of the node.
* ``shaper_profile_id``: Shaper profile ID of the private shaper to be used by
the node.
* ``cman_mode``: Congestion management mode to be enabled for this node.
@@ -2796,7 +2796,7 @@ where:
Delete port traffic management hierarchy node
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Delete node from port traffic management hiearchy::
+Delete node from port traffic management hierarchy::
testpmd> del port tm node (port_id) (node_id)
@@ -3989,7 +3989,7 @@ This section lists supported actions and their attributes, if any.
- ``dec_ttl``: Performs a decrease TTL value action
-- ``set_ttl``: Set TTL value with specificed value
+- ``set_ttl``: Set TTL value with specified value
- ``ttl_value {unsigned}``: The new TTL value to be set
- ``set_mac_src``: set source MAC address
@@ -4522,7 +4522,7 @@ The following sections show functions to load/unload eBPF based filters.
bpf-load
~~~~~~~~
-Load an eBPF program as a callback for partciular RX/TX queue::
+Load an eBPF program as a callback for particular RX/TX queue::
testpmd> bpf-load rx|tx (portid) (queueid) (load-flags) (bpf-prog-filename)
@@ -4560,7 +4560,7 @@ To load (not JITed) t1.o at TX queue 0, port 0::
bpf-unload
~~~~~~~~~~
-Unload previously loaded eBPF program for partciular RX/TX queue::
+Unload previously loaded eBPF program for particular RX/TX queue::
testpmd> bpf-unload rx|tx (portid) (queueid)
diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst
index c366af4..2fc6544 100644
--- a/doc/guides/tools/cryptoperf.rst
+++ b/doc/guides/tools/cryptoperf.rst
@@ -59,7 +59,7 @@ To set on the linearization options add below definition to the
**Step 3: Build the application**
Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the
-``dpdk-test-crypto-perf`` applcation.
+``dpdk-test-crypto-perf`` application.
Initially, the user must select a DPDK target to choose the correct target type
and compiler options to use when building the libraries.
@@ -80,7 +80,7 @@ EAL Options
~~~~~~~~~~~
The following are the EAL command-line options that can be used in conjunction
-with the ``dpdk-test-crypto-perf`` applcation.
+with the ``dpdk-test-crypto-perf`` application.
See the DPDK Getting Started Guides for more information on these options.
* ``-c <COREMASK>`` or ``-l <CORELIST>``
@@ -96,10 +96,10 @@ See the DPDK Getting Started Guides for more information on these options.
Add a virtual device.
-Appication Options
-~~~~~~~~~~~~~~~~~~
+Application Options
+~~~~~~~~~~~~~~~~~~~
-The following are the appication command-line options:
+The following are the application command-line options:
* ``--ptest type``
@@ -338,13 +338,13 @@ Test Vector File
The test vector file is a text file contain information about test vectors.
The file is made of the sections. The first section doesn't have header.
It contain global information used in each test variant vectors -
-typically information about plaintext, ciphertext, cipher key, aut key,
+typically information about plaintext, ciphertext, cipher key, auth key,
initial vector. All other sections begin header.
The sections contain particular information typically digest.
**Format of the file:**
-Each line beginig with sign '#' contain comment and it is ignored by parser::
+Each line beginning with sign '#' contain comment and it is ignored by parser::
# <comment>
@@ -352,16 +352,16 @@ Header line is just name in square bracket::
[<section name>]
-Data line contain information tocken then sign '=' and
+Data line contain information token then sign '=' and
a string of bytes in C byte array format::
- <tocken> = <C byte array>
+ <token> = <C byte array>
-**Tockens list:**
+**Tokens list:**
* ``plaintext``
- Original plaintext to be crypted.
+ Original plaintext to be encrypted.
* ``ciphertext``
diff --git a/doc/guides/tools/proc_info.rst b/doc/guides/tools/proc_info.rst
index 6bdf5a8..2ea1b59 100644
--- a/doc/guides/tools/proc_info.rst
+++ b/doc/guides/tools/proc_info.rst
@@ -44,7 +44,7 @@ If no port mask is specified xstats are reset for all DPDK ports.
**-m**: Print DPDK memory information.
**--show-port**
-The show-port parameter displays port level various configuration informationi
+The show-port parameter displays port level various configuration information
associated to RX port queue pair.
**--show-tm**
@@ -56,7 +56,7 @@ The show-crypto parameter displays available cryptodev configurations,
settings and stats per node.
**--show-ring[=name]**
-The show-ring pararmeter display current allocation of all ring with
+The show-ring parameter display current allocation of all ring with
debug information. Specifying the name allows to display details for specific
ring. For invalid or no ring name, whole list is dump.
@@ -76,7 +76,7 @@ Limitations
* When running ``dpdk-procinfo`` with shared library mode, it is required to
pass the same NIC PMD libraries as used for the primary application. Any
- mismatch in PMD library arguments can lead to undefined behaviour and results
+ mismatch in PMD library arguments can lead to undefined behavior and results
affecting primary application too.
* Stats retrieval using ``dpdk-procinfo`` is not supported for virtual devices like PCAP and TAP.
diff --git a/doc/guides/tools/testbbdev.rst b/doc/guides/tools/testbbdev.rst
index 07da35e..7e6a4db 100644
--- a/doc/guides/tools/testbbdev.rst
+++ b/doc/guides/tools/testbbdev.rst
@@ -139,7 +139,7 @@ There are 6 main test cases that can be executed using testbbdev tool:
* Latency measurement [-c latency]
- Measures the time consumed from the first enqueue until the first
appearance of a dequeued result
- - This measurment represents the full latency of a bbdev operation
+ - This measurement represents the full latency of a bbdev operation
(encode or decode) to execute
* Poll-mode Throughput measurement [-c throughput]
--
2.7.5
^ permalink raw reply [relevance 3%]
* [dpdk-dev] DPDK Release Status Meeting 23/5/2019
@ 2019-05-23 11:46 14% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2019-05-23 11:46 UTC (permalink / raw)
To: dpdk-dev
Cc: Stokes, Ian, Thomas Monjalon, Jerin Jacob, Akhil, Goyal,
Dumitrescu, Cristian, Xu, Qian Q, Yongseok Koh, Maxime Coquelin,
Zhang, Qi Z, Shahaf Shuler, De Lara Guarch, Pablo, Yigit, Ferruh
Minutes 23 May 2019
-------------------
Agenda:
* Release Dates
* Subtrees
* LTS
* OvS
* Opens
Participants:
* ARM
* Broadcom
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* RedHat
Release Dates
-------------
* v19.08 dates:
* Proposal/V1 Monday 03 June 2019
* Integration/Merge/RC1 Monday 01 July 2019
* Release Thurs 01 August 2019
* Schedule updated on roadmap page:
https://core.dpdk.org/roadmap/
* Reminder to send roadmaps for the release, it helps planning
* Intel is planning to send roadmap by the end of this week
* Marvell will have new PMDs and will provide a roadmap
* v19.11 proposed dates, *please comment*,
* Proposal/V1 Friday 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
* Constraints:
* PRC holidays on October 1-7 inclusive, rc1 shouldn't overlap with it
* US DPDK Summit on mid-November, better to have release before summit
Subtrees
--------
* Main
* No activity this week.
* Will target weekly merge starting next week.
* Next-Net
* RTE_prefix patch to be merged early.
* This will cause a lot of breakage in patches/backports.
* There is a script to convert the prefix automatically.
* Next-virtio
* Not many patches yet.
* Patch for SPDK.
* Under review. There is a new API(s).
* Requested some example code to demonstrate the APIs.
* Next-Crypto
* No patches yet.
* Next-Eventdev
* New timer patch for eventdev. Needs to be reviewed.
* Next-Ip-pipeline
* No update
* Stable trees
* 17.11.6
* 17.11.6 released 22 May 2019
* Testing with Red Hat lab (was down temporarily).
* 18.11.2
* 18.11.2-RC1 released 21 May 2019
* 11 June is the planned release date.
* Will be looking for testing from the community.
OvS
---
* 18.11.2 RC1 is out.
* Need to look at the impact of the rte_prefix.
* Will rebase end-of-month DPDKmaster to OvS
* 2.12 release dates
* 1 July for feature freeze
* No features beyond that date
* 20th July for code freeze
Conferences
-----------
* DPDK Userspace summit: DPDK Userspace · Sept. 19-20, 2019
https://www.dpdk.org/event/dpdk-userspace-bordeaux/
* CFP Opens: Monday, April 29
* CFP Closes: Friday, May 24
* Reminder of the short CFP duration and deadline is approaching
* US summit dates are not fixed yet
Opens
-----
* Akhil can able to spend more time on crypto sub-tree and there is a potential
co-maintainer from Arm, can close this open for now
* There still some Coverity defects open, some of them are from Marvell, NXP
drivers, it would be great to close them
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 14%]
* [dpdk-dev] DPDK Release Status Meeting 1/8/2019
@ 2019-08-02 11:35 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2019-08-02 11:35 UTC (permalink / raw)
To: dev; +Cc: Thomas Monjalon, Yigit, Ferruh
Minutes 1 August 2019
--------------------
Agenda:
* Release Dates
* RC3 Status
* Subtrees
* OvS
* Opens
Participants:
* Cavium/Marvell
* Debian/Microsoft
* Intel
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v19.08 dates:
* RC2 is released on Tuesday 23 July
* https://mails.dpdk.org/archives/announce/2019-July/000270.html
* RC3 is released on Wednesday 31 July
* https://mails.dpdk.org/archives/announce/2019-July/000272.html
* RC4 Tuesday 6 August
* Release Saturday 10 August
* v19.11 dates:
* Proposal/V1 Friday 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
RC3 Status
----------
* No test results available yet. Please submit test results to the list.
Subtrees
--------
* Next-Net
* No patches after RC3.
* Next-virtio
* Compilation issue for NXP.
* Next-Crypto
* No patches after RC3.
* Next-Eventdev
* No patches after RC3.
* Master
* Patches for network drivers.
* Power PC issues due to IOVA changes.
* Some patches for documentation, SPDX, etc.
* Stable trees
* 17.11 backported some patches for 17.11.7, no rc yet
* A request sent to authors to backport some patches
OvS
---
* Feature freeze done for 2.12, will take ~4 weeks, release ~22 August
* Some features vhost optimizations, af_xdp support, onv changes started
Opens
-----
* A new coverity scan done by John, there are new defects reported.
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 16%]
* [dpdk-dev] DPDK Release Status Meeting 28/11/2019
@ 2019-11-28 20:54 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2019-11-28 20:54 UTC (permalink / raw)
To: dev; +Cc: Thomas Monjalon
Minutes 21 November 2019
------------------------
Agenda:
* Release Dates
* RC4 Status
* Subtrees
* OvS
* Opens
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v19.11 dates:
* RC3 was released on Wednesday 20 November
https://mails.dpdk.org/archives/announce/2019-November/000302.html
* RC4 was released on Tuesday 26 November
https://mails.dpdk.org/archives/announce/2019-November/000303.html
* Release planned for Thursday/Friday 28/28 November
* Dates for 20.02 :
* Proposal/V1: Wednesday 11 December 2019
* Integration/Merge/RC1: Wednesday 15 January 2020
* Release: Friday 14 February 2020
RC4 Status
----------
* Intel testing complete for RC4. No major issues.
* OvS testing complete.
* Please report all test reports in reply to the RC4 announce message.
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>>" for the invite.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 26/03/2020
@ 2020-03-31 9:55 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2020-03-31 9:55 UTC (permalink / raw)
To: dev; +Cc: Yigit, Ferruh, thomas
Minutes 26 March 2020
---------------------
Agenda:
* Release Dates
* Subtrees
* OvS
Participants:
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
* ARM
Release Dates
-------------
* v20.05 dates:
* Proposal/V1: Wednesday 18 March 2020
* Integration/Merge/RC1: Friday 17 April 2020
* Release: Wednesday 20 May 2020
* Marvell, Arm, Mellanox & Broadcom already sent roadmap for 20.05, all
vendors please share the roadmap for the release.
Subtrees
--------
* main
* Some patches merged around EAL.
* Added Travis CI support for ARM.
* Still some random failures. Under investigation.
* There are several last series that need reviews in this release.
* This is challenging.
* We need the whole community involved with reviewing.
* Three big patch sets from Marvell
* IF proxy, Trace and Graph.
* Call for review of the testing guidelines:
* http://mails.dpdk.org/archives/web/2020-March/001346.html
Fixed issues with
* next-net
* Andrew Rybchenko took over maintenance this week from Ferruh.
* next-crypto
* Some patches merged
* Half of the backlog reviewed
* No major issues at the moment
* next-eventdev
* Some patches (10-15) to be merged.
* next-virtio
* Reviewing vHost IO IOAT Support Series
* Some progress in the discussion on the list.
* Agreed to do it in the vHost library.
* next-net-intel
* No update.
* next-net-mlx
* Working on a couple of patch series.
* LTS
* 18.11.7
* -rc1 is out.
* Release planned for 14 April
* 19.11.1 released
* https://mails.dpdk.org/archives/dev/2020-March/160132.html
OvS
---
* Second OVS-DPDK meeting done, thanks Kevin for notes and recording:
* https://bluejeans.com/s/6wR3z
* Intel is preparing something to present in next meeting
* Planning to do more test on 19.11.1
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 11/06/2020
@ 2020-06-17 15:34 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2020-06-17 15:34 UTC (permalink / raw)
To: dev; +Cc: Thomas Monjalon
Minutes 11 June 2020
--------------------
Agenda:
* Meeting
* Release Dates
* Subtrees
* OvS
Participants:
* Arm
* Debian/Microsoft
* Intel
* Mellanox
* Red Hat
Meeting
-------
* Call for maintainers to follow up on patches that have stalled.
* There are several patchset hanging around but not progressing.
* Maintainers should ask people for reviews or to respond to open comments.
* This would help overall progress with merging.
* From next week (18 June) we with use Jitsi instead of Skype for meetings:
* https://meet.jit.si/DPDK
Release Dates
-------------
* v20.08 dates:
* Proposal/V1: Friday, 12 June 2020
* -rc1: Wednesday, 8 July 2020
* -rc2: Monday, 20 July 2020
* Release: Tuesday, 4 August 2020
Subtrees
--------
* main
* Series from Stephen Hemminger on changing whitelist/blacklist:
* http://mails.dpdk.org/archives/dev/2020-June/170240.html
* There are a lot of patch series in this release including:
* RCU integration
* Bitops - ready for merge
* Lcore hotplug - for attaching external threads
* Vfio VF token interface
* IF Proxy
* Several Windows series
* next-net
* Merging on track ahead of V1 deadline.
* next-crypto
* No update this week.
* next-eventdev
* No update this week.
* next-virtio
* Not a lot of patches.
* Changes and improvements in virtio/vhost initialization.
* Significant rework of the vDPA API - goal is to remove the experimental tag.
* next-net-mlx
* Some big series ready to be merged or pending - patches to support Windows.
LTS
---
* v19.11.3-rc1 is out, please test
* https://mails.dpdk.org/archives/dev/2020-June/169263.html
* Test results from Intel and Mellanox.
* Waiting for results from Microsoft, OvS and Red Hat.
* v18.11.9 in progress
* Majority of patches backported.
* Issues with GCC10.
* RC1 towards the end of next week.
* Then moving to validation phase.
OvS
---
* Validating CVE fixes
* A performance drop observed previously couldn't be replicated.
* Release feature deadline is beginning of the July and code freeze mid July
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 13/08/2020
@ 2020-08-13 18:55 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2020-08-13 18:55 UTC (permalink / raw)
To: dev; +Cc: Yigit, Ferruh, Thomas Monjalon
Minutes 13 August 2020
----------------------
Agenda:
* Release Dates
* -rc3/-rc4 status
* Subtrees
* LTS
* OvS
Participants:
* Arm
* Broadcom
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* NXP
Release Dates
-------------
* v20.11 proposal dates, please comment:
* Proposal/V1: Friday, 11 September 2020
* -rc1: Friday, 9 October 2020
* -rc2: Friday, 23 October 2020
* Release: Friday, 13 November 2020
* The dates are still not finalized, we need to discuss this offline and
define dates as soon as possible, please comment.
* Please remember to send roadmap for 20.11, none received yet.
Subtrees
--------
DPDK 20.08 released.
There were a lot of maintainers on holiday this week and not much activity on the subtrees,
LTS
---
* 19.11.4 work is going on
* Some patches are backported, email sent, please review.
* RC planned for Monday 18th
* 18.11.10 work is going on
* Some patches are backported
OvS
---
* 2.14 release trending for 17 August
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 16%]
* [dpdk-dev] DPDK Release Status Meeting 18/03/2021
@ 2021-03-18 19:36 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-03-18 19:36 UTC (permalink / raw)
To: dev; +Cc: Yigit, Ferruh, thomas
Release status meeting minutes {Date}
=====================================
:Date: 18 March 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* LTS
* Conferences
* Opens
.Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.05` dates
- Proposal/V1: Thursday, 18 March
- -rc1: Thursday, 15 April
- Release: Friday, 14 May
* Please send roadmaps, preferably before beginning of the release
- Thanks to `Marvell`, `Huawei hns3`, `Nvidia`, `Wangxun` and `Intel` for
sending roadmap
Subtrees
--------
* main
- Thomas focused on Windows related patches
- Patches for ARM compilation
- Pulled MMIO for virtio legacy devices patches from Alibaba
- Tests broken due to version macro (fix pending)
- Should merge musl support in this release
** Needs support in CI Community lab
** Maybe run in container
- Migrating the Git repositories, documentation, and the DPDK
core website on Sunday 28th March
* next-net
- Progressing, nothing critical
* next-crypto
- Not much update
- Will review/merge some apps and drivers this week
* next-eventdev
- Several ongoing patches: periodic timer, vector event,
removal of DLB1 and updates to DLB2, CNXK evnetdev
* next-virtio
- Some series are ready but no PR yet
LTS
---
* `v19.11.7-rc2` is released, 2021-03-17
- http://inbox.dpdk.org/dev/20210317170343.3267049-1-christian.ehrhardt@canonical.com/T/#u
* `v20.11.1` is released, 2021-03-08
- http://inbox.dpdk.org/dev/20210308181351.409609-1-luca.boccassi@gmail.com/
Conferences
-----------
* DPDK APAC 2021 event is approaching, it is on 22-23 March
- https://www.dpdk.org/event/dpdk-summit-apac-2021/
- https://events.linuxfoundation.org/dpdk-summit-apac/
Opens
-----
* John is evaluating lgtm.com
- https://lgtm.com/projects/g/DPDK/dpdk/?mode=list
* Is there anyone did code review on github, please reach out for BKMs or for
experience sharing
.DPDK Release Status Meetings
*****
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
*****
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 11/06/2021
@ 2021-06-11 14:39 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-06-11 14:39 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes {Date}
=====================================
:Date: 10 June 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
.Participants:
* Arm
* Canonical
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.08` dates
- Proposal/V1: Wednesday, 2 June (completed)
- -rc1: Monday, 5 July
- Release: Tuesday, 3 August
* Note: We need to hold to the early August release date since
several of the maintainers will be on holidays after that.
Subtrees
--------
* main
- Started merging series from last release
** PCI bus update for resets with VF devices
- Thomas will start pulling branches today
- Marvell: Raw device driver for basebase/PHY
* next-net
- Andrew has started doing reviews
* next-crypto
- 4 new PMDs in this release
** CNXK
** MLX
** Intel QAT
** NXP baseband
- Reviews started
* next-eventdev
- CNXK eventdev driver update
* next-virtio
- 4 series from Intel around the async data - under review
- 1 series from Maxime - kernel vdpa support - get mac address
from hardware. Postponed from last series.
- Working on vhost user issue with numa reallocation
* next-net-brcm
- Should be a biggish release ~60 patches
* next-net-intel
- No update this week
* next-net-mlx
- Should be a small release for Mellanox
* next-net-mrvl
- CNXK ethernet driver (from last release).
- V3 should be merged last week.
LTS
---
* `v19.11` (next version is `v19.11.9`)
- 19.11.9 is in progress
- Needs an RC3 - triggered by kernel update in SuSE
- Tagged for release
- Waiting for tests
* `v20.11` (next version is `v20.11.2`)
- Tagged for release
* Distros
- v20.11 in Debian 11
- v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* None
.DPDK Release Status Meetings
*****
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
*****
^ permalink raw reply [relevance 16%]
* [dpdk-dev] DPDK Release Status Meeting 17/06/2021
@ 2021-06-18 16:03 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-06-18 16:03 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes {Date}
=====================================
:Date: 17 June 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
.Participants:
* Arm
* Broadcom
* Canonical
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.08` dates
- Proposal/V1: Wednesday, 2 June (completed)
- -rc1: Monday, 5 July
- Release: Tuesday, 3 August
* Note: We need to hold to the early August release date since
several of the maintainers will be on holidays after that.
* `v21.11` dates (proposed and subject to discussion)
- Proposal/V1: Friday, 10 September
- -rc1: Friday, 15 October
- Release: Friday, 19 November
Subtrees
--------
* main
- Merged series from last release on PCI bus update for resets with VF devices
- Working on unit test failures from UNH lab
- Working on Solarflare patches
- Discussion ongoing about DMA Engine RFC
- Thomas applying some patchsets
** Series from Marvell - Raw device driver for basebase/PHY
** Auxiliary bus
** Mediated device - concerns from kernel on on similar DSA Driver:
*** https://lore.kernel.org/kvm/162164243591.261970.3439987543338120797.stgit@djiang5-desk3.ch.intel.com/
*** https://patchwork.kernel.org/project/kvm/cover/0-v1-324b2038f212+1041f1-vfio3a_jgg@nvidia.com/
* next-net
- Andrew working on testpmd patches for Windows - needs ack
- Bonding patches also need reviews
* next-crypto
- 4 new PMDs in this release
** CNXK - reviewed
** MLX - no update
** Intel QAT - will be reviewed next week
** NXP baseband - requires new version
* next-eventdev
- CNXK eventdev driver - awaiting further revisions
* next-virtio
- 4 series from Intel around the async data - under review
- 1 series from Maxime - kernel vdpa support - get mac address
from hardware. Under review and will send update
- Working on fixing issue in vhost with numa reallocation
* next-net-brcm
- Big patchset with 58 patches merged into dpdk-next-net-brcm sub tree.
- 4 to 5 patches pending on patchwork.
- Partially merged in main. The rest under review Thomas.
* next-net-intel
- Proceeding okay. No issues
* next-net-mlx
- Should be a small release for Mellanox
- Mainly fixes and RFCs
* next-net-mrvl
- CNXK ethernet driver (from last release).
- V4 should be merged next week.
LTS
---
* `v19.11` (next version is `v19.11.9`)
- RC3 tagged
- Target release date July 2
* `v20.11` (next version is `v20.11.2`)
- Tagged for release: RC1
* Distros
- v20.11 in Debian 11
- v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* None
.DPDK Release Status Meetings
*****
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
*****
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 24/06/2021
@ 2021-06-28 15:42 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-06-28 15:42 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes {Date}
=====================================
:Date: 24 June 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
.Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.08` dates
- Proposal/V1: Wednesday, 2 June (completed)
- -rc1: Monday, 5 July
- Release: Tuesday, 3 August
* Note: We need to hold to the early August release date since
several of the maintainers will be on holidays after that.
* `v21.11` dates (proposed and subject to discussion)
- Proposal/V1: Friday, 10 September
- -rc1: Friday, 15 October
- Release: Friday, 19 November
Subtrees
--------
* main
- Unit test fixes for issues with Address Sanitizer.
- Build issues with Solarflare patches - under investigation.
- Some of the sub-trees already pulled as part of incremental merging prior to RC1.
- RC1 targeted for Monday 5th July. Subtree maintainers should submit PRs on
Wednesday 30th June to allow time for RC1 merge.
* next-net
- Andrew working on testpmd patches for Windows - needs ack
- Bonding patches also need reviews
* next-crypto
- 4 new PMDs in this release:
** CNXK - reviewed - awaiting final version for RC1.
** MLX - still in progress. New version with unit tests due in next few days.
** Intel QAT - under review.
** NXP baseband - requires new version.
* next-eventdev
- CNXK eventdev driver - should be available for RC1.
- Baseband patches reviewed.
* next-virtio
- 4 series from Intel around the async data - new series under review.
- Patchset on numa reallocation under review.
* next-net-brcm
- Big patchset with 58 patches merged into dpdk-next-net-brcm sub tree.
* next-net-intel
- Proceeding okay. No issues
* next-net-mlx
- Should be a small release for Mellanox
- Waiting for PR to be pulled.
* next-net-mrvl
- CNXK ethernet driver (from last release).
- V4 received and under review. Should be merged next week.
LTS
---
* `v19.11` (next version is `v19.11.9`)
- RC3 tagged
- Target release date July 2
* `v20.11` (next version is `v20.11.2`)
- RC2 tagged
* Distros
- v20.11 in Debian 11
- v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* None
.DPDK Release Status Meetings
*****
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
*****
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 01/07/2021
@ 2021-07-01 16:30 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-07-01 16:30 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes {Date}
=====================================
:Date: 1 July 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
.Participants:
* Broadcom
* Canonical
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.08` dates
- Proposal/V1: Wednesday, 2 June (completed)
- -rc1: Wednesday, 7 July
- Release: Tuesday, 3 August
* Note: We need to hold to the early August release date since
several of the maintainers will be on holidays after that.
* `v21.11` dates (proposed and subject to discussion)
- Proposal/V1: Friday, 10 September
- -rc1: Friday, 15 October
- Release: Friday, 19 November
Subtrees
--------
* main
- Backlog is a little big at the moment. RC1 will probably slip to Wednesday 7th July.
- Most subtrees PRs are ready or close to ready.
- Still waiting update on Solarflare patches.
- New auxiliary bus patch series should go into this release.
* next-net
- Testpmd patchset for Windows.
- Looking at net/sfc patches.
* next-crypto
- 4 new PMDs in this release:
** CNXK - reviewed - awaiting final version for RC1.
** MLX - still in progress. New version will be sent today.
** Intel QAT - under review.
** NXP baseband - requires new version.
* next-eventdev
- PR for RC1 will be completed today.
* next-virtio
- PR posted yesterday.
* next-net-brcm
- All patches in sub-tree waiting to be pulled.
* next-net-intel
- Proceeding okay. No issues
* next-net-mlx
- PR not pulled due to comments that need to be addressed.
- New version sent today.
* next-net-mrvl
- Pull request for RC1 sent.
LTS
---
* `v19.11` (next version is `v19.11.9`)
- RC3 tagged.
- Target release date July 2, however there are some late reported
MLX regressions that are under investigation.
- There are 2 other known issues:
** Plenty of GCC11 and Clang build issues were fixed, but 19.11.9
is not yet compatible with clang 12.0.0. Fixes are discussed
and a potential 3 backports identified for 19.11.10:
https://bugs.dpdk.org/show_bug.cgi?id=733
** Due to a kernel patch backport in SUSE Linux Enterprise Server 15
SP3 6, compilation of kni fails there:
https://bugs.dpdk.org/show_bug.cgi?id=728
* `v20.11` (next version is `v20.11.2`)
- RC2 released
- Some test reports coming in (Intel, MLX)
- 6 July is proposed release date.
* Distros
- v20.11 in Debian 11
- v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* There in an ongoing initiative around ABI stability which was
discussed in the Tech Board call. A workgroup has come up
with a list of critical and major changes required to let us
extend the ABI without as much disruption. For example:
** export driver interfaces as internal
** hide more structs (may require uninlining)
** split big structs + new feature-specific functions Major
** remove enum maximums
** reserved space initialized to 0
** reserved flags cleared
* We need to fill details and volunteers in this table:
https://docs.google.com/spreadsheets/d/1betlC000ua5SsSiJIcC54mCCCJnW6voH5Dqv9UxeyfE/edit?usp=sharing
* The DPDK North America Summit will be on July 12-13. Registration is free.
https://events.linuxfoundation.org/dpdk-summit-north-america/
.DPDK Release Status Meetings
*****
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
*****
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 15/07/2021
@ 2021-07-15 22:28 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-07-15 22:28 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes {Date}
=====================================
:Date: 15 July 2021
:toc:
.Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
.Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* `v21.08` dates
- Proposal/V1: Wednesday, 2 June (completed)
- rc1: Saturday, 10 July (completed)
- rc2: Thursday, 22 July
- rc3: Thursday, 29 July
- Release: Tuesday, 3 August
* Note: We need to hold to the early August release date since
several of the maintainers will be on holidays after that.
* `v21.11` dates (proposed and subject to discussion)
- Proposal/V1: Friday, 10 September
- -rc1: Friday, 15 October
- Release: Friday, 19 November
Subtrees
--------
* main
- RC1 released.
- RC2 targeted for Thursday 22 July.
- Still waiting update on Solarflare patches.
* next-net
- No update.
* next-crypto
- 4 new PMDs in this release:
** CNXK - merged.
** MLX - on last review. Should be merged for RC2.
** Intel QAT - Should be merged for RC2.
** NXP baseband - will be deferred to next release.
* next-eventdev
- PR for RC2 today or tomorrow.
* next-virtio
- Some patches in PR today.
- New DMA Dev work complicates merging of some of the vhost patches.
An offline meeting will be held to view options and decide the
best technical approach. Maxime to set up.
* next-net-brcm
- No update.
* next-net-intel
- No update.
* next-net-mlx
- PR not pulled due to comments that need to be addressed.
- New version sent today.
* next-net-mrvl
- Almost ready for RC2.
- 1 or 2 small series and bug fixes.
LTS
---
* `v19.11` (next version is `v19.11.9`)
- RC4 tagged.
- Target release date July 19.
* `v20.11` (next version is `v20.11.3`)
- 20.11.2 released by Xueming Li on July 7.
- https://git.dpdk.org/dpdk-stable/commit/?h=20.11&id=a86024748385423306aac45524d6fc8d22ea6703
* Distros
- v20.11 in Debian 11
- v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* There in an ongoing inititive around ABI stability which was
discussed in the Tech Board call. A workgroup has come up
with a list of critical and major changes required to let us
extend the ABI without as much disruption. For example:
** export driver interfaces as internal
** hide more structs (may require uninlining)
** split big structs + new feature-specific functions Major
** remove enum maximums
** reserved space initialized to 0
** reserved flags cleared
* We need to fill details and volunteers in this table:
https://docs.google.com/spreadsheets/d/1betlC000ua5SsSiJIcC54mCCCJnW6voH5Dqv9UxeyfE/edit?usp=sharing
.DPDK Release Status Meetings
*****
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
*****
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 2021-09-02
@ 2021-09-03 16:31 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-09-03 16:31 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes 2021-09-02
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Broadcom
* Canonical
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates
* Proposal/V1: Friday, 10 September
* -rc1: Friday, 15 October
* Release: Friday, 19 November
Subtrees
--------
* main
* Reviews starting
* next-net
* Reviews ongoing
* Reviewing Ethdev patches
* Will pull from sub-tree today
* next-net-brcm
* Patchset of 14 patches pending on patchwork
* All other patches are merged into the Broadcom subtree
* next-net-intel
- Reviews and merging ongoing
* next-net-mlx
- PR not pulled due to comments that need to be addressed
- New version sent today.
* next-net-mrvl
- Some patches submitted and already pulled by Ferruh
* next-crypto
* Started merging
* PR ready early next week
* next-eventdev
* Arourn 15 patches
* Changes for API hiding (for ABI stability)
* next-virtio
* Reviewing patches
* Xilinx driver reviewed
* DMA Device RFC under review
* 30 patches on list
* New vdpa driver
LTS
---
* v19.11 (next version is v19.11.10)
* Awaiting test reports
* Proposed release: Sept 6
* v20.11 (next version is v20.11.3)
* Awaiting test reports
* Proposed release: Sept 6
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* Call for roadmaps
* Proposal to submit roadmaps during the release week
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 16%]
* [dpdk-dev] DPDK Release Status Meeting 2021-09-16
@ 2021-09-17 15:32 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-09-17 15:32 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes 2021-09-16
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Broadcom
* Canonical
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates
* Proposal/V1: Friday, 10 September (complete)
* -rc1: Friday, 15 October
* Release: Friday, 19 November
Subtrees
--------
* main
* Oops/core dump handling
* Windows: new API for thread management
* Will review new version of DMA dev
* New Slack channel: https://join.slack.com/t/dpdkproject/shared_invite/zt-v6c9ef5z-FqgOAS7BDAYqev_a~pbXdw
* next-net
* Reviews and merging ongoing
* Lot of Ethdev patches - concerning due to number and to conflicts
* Will merge from sub-trees today
* next-net-brcm
* Patches have been merged to subtree
* next-net-intel
- Reviews and merging ongoing
* next-net-mlx
- 24 patches on the list that need to reviewed merged
* next-net-mrvl
- Some patches merged.
- 50-60 other patches
- Ready to merge
* next-crypto
* Merged ~50 patches
* Has been pulled by Thomas
* next-eventdev
* Some patches from Intel under review with comments
* Driver patches for cxnk
* Changes on API hiding (for ABI stability)
* next-virtio
* Reviewing patches and submitted first PR
* Maxime submitting virtio RSS feature
* 30 Patches on list, many around Vhost async
* Xilinx driver reviewed
* Power management patches under review
* DMA Device RFC under review
* Comments from Ilya on the OVS list that functionality may below in DPDK rather than OVS: http://patchwork.ozlabs.org/comment/2751918/
LTS
---
* v19.11 (next version is v19.11.10)
* 20.11.3 released on Monday Sept 6
* 19.11.10 released on Monday Sept 6
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* Release of OpenSSL 3.0 will cause some compilation issues in cryptodev: https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 2021-09-23
@ 2021-09-30 19:38 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-09-30 19:38 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes 2021-09-23
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates
* Proposal/V1: Friday, 10 September (complete)
* -rc1: Friday, 15 October
* Release: Friday, 19 November
Subtrees
--------
* next-net
* Merged from subtrees 2021-09-22
* Issue with Broadcom tree and older compilers
* Reviewing Enetfec NXP driver
* Lot of Ethdev patches - concerning due to number or patches and to conflicts between them.
* next-net-intel
- Merged base codes updates
- More coming
- Waiting for fix on ICE driver. CI issue with RSS
* next-net-mlx
- Some patches merged and some merges ongoing
* next-net-brcm
* Issue with GCC7 - under investigation
* next-net-mrvl
- Some patches merged and some ongoing
* next-eventdev
* 2 series from Intel - In good shape for merge
* Changes on API hiding (for ABI stability)
* next-virtio
* More reviews ongoing. ~6 ready for merge
* Reviewing virtio RSS feature
* next-crypto
* Patches for test framework
* ABI changes reviewed
* Crypto and security session will be sent in the next few days
* main
* API updates for interrupts
* - Call to driver maintainers to look at it
- https://patchwork.dpdk.org/project/dpdk/list/?series=18664
* Pipelines patches to review
* Issue with KNI build on SuSE
* New Slack channel: https://join.slack.com/t/dpdkproject/shared_invite/zt-v6c9ef5z-FqgOAS7BDAYqev_a~pbXdw
LTS
---
* v19.11 (next version is v19.11.10)
* 20.11.3 released on Monday Sept 6
* 19.11.10 released on Monday Sept 6
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* Release of OpenSSL 3.0 will cause some compilation issues in cryptodev: https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 2021-09-30
@ 2021-09-30 19:59 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-09-30 19:59 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes 2021-09-30
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* Broadcom
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates
* Proposal/V1: Friday, 10 September (complete)
* -rc1: Friday, 15 October
* Release: Friday, 19 November
Subtrees
--------
* next-net
* Reviewing and merging ongoing
* Pulled sub-trees and rebased to main
* Will merge other subtrees today
* Patch from ARM to fix descriptor order. However, there is a 20% decrease in performance on ThunderX. Other ARM vendors should check.
* Release queue patch - awaiting response
* next-net-intel
- Waiting base code update
- Tests need to be enabled in the CI
* next-net-mlx
- 3 patches merged and some merges ongoing
- Big regex patchset will be merged directly to main
* next-net-brcm
* Issue with GCC7 resolved
* next-net-mrvl
- A lot of patches to merge
- 2 big patches for inline-ipsec and ingress meter
- https://patches.dpdk.org/project/dpdk/list/?series=18917&state=*
* next-eventdev
* Intel patches merged (except one)
* Changes on API hiding (for ABI stability) reviewed and looks good.
* next-virtio
* Still quite a few series under review
* Fix for regression that could be merged: net/virtio: revert forcing IOVA as VA mode for virtio-user
* next-crypto
* Progressing.
* A few patches that can be merged
* Issue with Windows CI failure
* main
* **NOTE**: there are several large patchset on main the review detailed
reviews from the community such as the series for Interrupts
and for Thread API.
* Merging experimental API updates ongoing
* API updates for interrupts
* Call to driver maintainers to look at it:
* https://patchwork.dpdk.org/project/dpdk/list/?series=18664
* Some ASAN patches under review but need rework
* Thread API series needs more reviews
* https://patchwork.dpdk.org/project/dpdk/list/?series=18338
* DMA device under review
* Need to fix issue with MBUF segments
* Should be merged this release and needs review
* https://patches.dpdk.org/project/dpdk/patch/20210929213707.17727-1-olivier.matz@6wind.com/
* Patches under test for automatic delegation patch delegation in the CI
* Issue with KNI build on SuSE
* New Slack channel: https://join.slack.com/t/dpdkproject/shared_invite/zt-v6c9ef5z-FqgOAS7BDAYqev_a~pbXdw
LTS
---
* v19.11 (next version is v19.11.10)
* 20.11.3 released on Monday Sept 6
* 19.11.10 released on Monday Sept 6
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* Release of OpenSSL 3.0 will cause some compilation issues in cryptodev: https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 2021-10-21
@ 2021-10-27 15:53 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-10-27 15:53 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes 2021-10-21
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Broadcom
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates
* Proposal/V1: Friday, 10 September (complete)
* -rc1: Friday, 15 October - Moved to Monday 25 October
* Release: Friday, 19 November
Subtrees
--------
* next-net
* Subtrees pulled
* Most patches are in
* Ethdev patchset from Intel still iterating
* 2 Series from Nvidia around eth_dev, can go in after RC1
* Other eth_dev patches reviewed
* Some testpmd patches still to be reviewed
* Series should be ready Friday 22
* next-net-intel
* Mainly merged up
* next-net-mlx
* Some patch pulled
* Need to push fix for eal interrupts
* next-net-brcm
* 1 patchset on patchwork
* Will need a v2. Probably after RC1
* next-net-mrvl
* Almost all patches merged and pulled
* A few minor ones to be checked
* next-eventdev
* PR submitted
* next-virtio
* Started to apply patches
* PR hopefully ready today
* Not all series will be in this series
* next-crypto
* Merged ipsec changes
* Maybe some compilation issues
* 2 library changes pending
* main
* Interrupt series
- Some issues/feedback on mailing list
- https://patchwork.dpdk.org/project/dpdk/list/?series=18664
* Series to rename mbuf flags - API cleanup
* PCI Series
- Still under discussion
* Series for ARM on redefining wait schemes
- https://patchwork.dpdk.org/project/dpdk/list/?series=19829
* Series for new pdump design
* DMA library merged. PMDs under review.
* New Slack channel: https://join.slack.com/t/dpdkproject/shared_invite/zt-v6c9ef5z-FqgOAS7BDAYqev_a~pbXdw
LTS
---
* v19.11 (next version is v19.11.10)
* 20.11.3 released on Monday Sept 6
* 19.11.10 released on Monday Sept 6
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
- https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 2021-10-28
@ 2021-10-28 13:35 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-10-28 13:35 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes 2021-10-28
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Broadcom
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates: http://core.dpdk.org/roadmap/#dates
* PMD features freeze (-rc2): 5 November 2021
* Builtin applications features freeze (-rc3): 12 November 2021
* Release: 24 November 2021
Subtrees
--------
* next-net
* RC1 merged and released
* Still some patches to merge
* One ethdev patch not merged
* New NXT PMD - will need more changes
* Should be ready for a new PR tomorrow Friday 29
* next-net-intel
* More patches to be merged post RC1
* next-net-mlx
* More patches to be merged post RC1
* next-net-brcm
* More patches to be merged post RC1
* Ready for a PR.
* next-net-mrvl
* ~15 patches to be merged
* next-eventdev
* Looking at series on telemetry support
* Also a series from Ericsson under review but will probably move to next release
* Doc update
* next-virtio
* ~40 patches in the queue
* Power monitor series from Intel - now ok
* RSS series
* 2 outstanding
* Async support - needs reviews
* Xilinx vdpa - at risk
* next-crypto
* Security session postponed
* IPsec under review
* Telemetry merged
* Windows cross compilation for MLX5 not working
* main
* RC1 release on 25/10/2021
* Second largest RC1 in DPDK history
* Issue with Meson 6.0.0
* See proposed fixes on patchwork
* Interrupt series
* Some issues/feedback on mailing list
* https://patchwork.dpdk.org/project/dpdk/list/?series=18664
* Merging VFIO changes
* PCI Series
* Still under discussion
* Probably won't make this release
* Series for ARM on redefining wait schemes
* https://patchwork.dpdk.org/project/dpdk/list/?series=19829
* Should be ready for RC2
* IWYU - Thomas will review
* Some series changing API
* Sched library
LTS
---
* v19.11 (next version is v19.11.10)
* 20.11.3 released on Monday Sept 6
* 19.11.10 released on Monday Sept 6
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 15%]
* [dpdk-dev] DPDK Release Status Meeting 2021-11-28
@ 2021-11-05 7:49 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-11-05 7:49 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
Release status meeting minutes 2021-11-28
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates: http://core.dpdk.org/roadmap/#dates
* PMD features freeze (-rc2): 5 November 2021
* Builtin applications features freeze (-rc3): 12 November 2021
* Release: 24 November 2021
Subtrees
--------
* next-net
* Subtrees mainly pulled and merged
* Awaiting some changes/updates
* NXP ENETFEC may go into RC2: https://patchwork.dpdk.org/project/dpdk/list/?series=20286
* next-net-intel
* Tree mostly closed.
* Some patches need updating.
* next-net-mlx
* Updates required for build issue
* next-net-brcm
* No update.
* next-net-mrvl
* No update.
* next-eventdev
* No update.
* next-virtio
* Xilinx vdpa driver - new version sent for review
* Some fix patches to be merged
* next-crypto
* Most patches merged
* 2 series from Intel
- Need rebase to merge
* Should before RC2 window
* main
* ASAN series merged
* ARM wait scheme merged
* Interrupt series - Waiting for some fixes
* Memory allocator patches
* DMA drivers to merge
* Toeplitz hash to be merged
* GPU library to be merged
* PIE patches - waiting better patch log
LTS
---
* There is a proposal to make 19.11 LTS into a 3 year release
* 20.11.3 released on Monday Sept 6
* 19.11.10 released on Monday Sept 6
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2021-11-11
@ 2021-11-12 16:19 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-11-12 16:19 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
[-- Attachment #1: Type: text/plain, Size: 2777 bytes --]
Release status meeting minutes 2021-11-11
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates: http://core.dpdk.org/roadmap/#dates
* Built-in applications features freeze (-rc3): 16 November 2021
* Release: 24 November 2021
* Proposed dates for 22.02
* Proposal deadline (RFC/v1 patches): 14 December 2021
* API freeze (-rc1): 14 January 2022
* PMD features freeze (-rc2): 28 January 2022
* Built-in applications features freeze (-rc3): 18 February 2022
* Release: 22 February 2022
* There is also a proposal to have only 3 releases in 2022:
* 22.03, 22.07, 22.11
Subtrees
--------
* next-net
* Pulled from subtrees
* Waiting for some updates
* I40e descriptor fix
* - 20% performance drop on ARM platforms
- Needs some discussion
* next-net-intel
* Tree mostly closed.
* next-net-mlx
* Some fixes coming for
* Updates required for build issues
* next-net-brcm
* No update.
* next-net-mrvl
* 2 patches for merging
* next-eventdev
* 3 patches merged
* Working on doc changes
* next-virtio
* Xilinx vdpa driver - new version sent for review
* Some fix patches to be merged
* next-crypto
* Fixes under review
* Xilinx vdpa driver - merged
* main
* Rc2 released on 2021-11-09
* New driver for DMA
* GPU/CUDA library to be merged
* Issues with Clang 13 on Fedora 35
* Need to enable ASAN in CIs
* L3FWD - series that changes the IP addresses
* Interrupt series merged
* DMA drivers to merge
* DMARC mitigation has happened for dpdk.org's mailing lists
https://mails.dpdk.org/archives/announce/2021-September/000385.html
LTS
---
* There is a proposal to make 19.11 LTS into a 3 year release
* 20.11.3 released on Monday Sept 6
* 19.11.10 released on Monday Sept 6
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 20196 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2021-11-18
@ 2021-11-19 16:41 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-11-19 16:41 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
[-- Attachment #1: Type: text/plain, Size: 2184 bytes --]
Release status meeting minutes 2021-11-18
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
* v21.11 dates: http://core.dpdk.org/roadmap/#dates
* Doc, tool, and minor fixes (-rc4): 24November 2021
* Release: 26 November 2021
* There is also a proposal to have only 3 releases in 2022:
* 22.03, 22.07, 22.11
* Dates will be finalized after 21.11 release
Subtrees
--------
* next-net
* Fixed merged in RC3
* Mainly doc patches in RC4
* next-net-intel
* Mainly doc patches in RC4
* next-net-mlx
* A few remaining fixes to be merged
* Majority merged in RC3
* next-net-brcm
* No update.
* next-net-mrvl
* No patches.
* next-eventdev
* Doc series only (v4)
* next-virtio
* 3 patches for vhost async (postponed to next release)
* next-crypto
* A few BXP patches/fixes to be merged
* main
* RC3 released
* Only doc, tools and fixes will be merged in RC4
* Wed 24 for RC4 and release on Friday 26
* Subtree maintainers should rebase to main to pick up Fedora 35 fixes
* Please submit 22.02/22.03 roadmaps next week.
LTS
---
* There is a proposal to make 19.11 LTS into a 3 year release
* 20.11.3 released on Monday Sept 6
* 19.11.10 released on Monday Sept 6
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 8:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 16571 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2021-12-02
@ 2021-12-07 8:42 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-12-07 8:42 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
Release status meeting minutes 2021-12-02
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The discussion this week was mainly around release dates in the 3 release cycle. The following are the proposed dates for 22.03:
* 22.03 V1 2021-12-31
* 22.03 Merge 2022-02-11
* 22.03 Release 2022-03-11
And some provisional dates for the subsequent releases:
* 22.07 V1 2022-05-06
* 22.07 Merge 2022-06-10
* 22.07 Release 2022-07-15
* 22.11 V1 2022-09-09
* 22.11 Merge 2022-10-18
* 22.11 Release 2022-11-18
Subtrees
--------
* 21.11 released.
LTS
---
* There is a proposal to make 19.11 LTS into a 3 year release. This depends on companies providing testing for the additional releases:
* 21.11.1 in progress
* 20.11.4 in progress
* 19.11.11 in progress
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 12439 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2021-12-09
@ 2021-12-10 16:35 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2021-12-10 16:35 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]
Release status meeting minutes 2021-12-09
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed dates for 22.03:
* 22.03 V1 2021-12-31
* 22.03 Merge 2022-02-11
* 22.03 Release 2022-03-11
See also http://core.dpdk.org/roadmap/#dates
And some provisional dates for the subsequent releases:
* 22.07 V1 2022-05-06
* 22.07 Merge 2022-06-10
* 22.07 Release 2022-07-15
* 22.11 V1 2022-09-09
* 22.11 Merge 2022-10-18
* 22.11 Release 2022-11-18
Subtrees
--------
* next-net
* Some patches merged from mlx tree
* next-net-intel
* Some patches merged to next-net
* next-net-mlx
* Some patches merged to next-net
* next-net-brcm
* No update
* next-net-mrvl
- No update
* next-eventdev
* No update
* next-virtio
* Not many new series yet
* next-crypto
* No update on tree
* Some patches from Marvell and Intel QAT
* main
* Low activity at the moment
* Regression on vmxnet3 - under investigation
* Will work on tooling prior to V1
* There is a crash when using latest libabigail (stick to version 1.8)
LTS
---
* There is a proposal to make 19.11 LTS into a 3 year release. This depends on companies providing testing for the additional releases:
* 21.11.1 in progress
* 20.11.4 in progress
* 19.11.11 in progress
* Distros
* v20.11 in Debian 11
* v20.11 in Ubuntu 21.04
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 16337 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2022-01-20
@ 2022-01-20 13:03 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-01-20 13:03 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
[-- Attachment #1: Type: text/plain, Size: 2935 bytes --]
Release status meeting minutes 2022-01-20
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed dates for 22.03:
* 22.03 V1 2021-12-31
* 22.03 Merge 2022-02-11
* 22.03 Release 2022-03-11
See also http://core.dpdk.org/roadmap/#dates
And some provisional dates for the subsequent releases:
* 22.07 V1 2022-05-06
* 22.07 Merge 2022-06-10
* 22.07 Release 2022-07-15
* 22.11 V1 2022-09-09
* 22.11 Merge 2022-10-18
* 22.11 Release 2022-11-18
Subtrees
--------
* next-net
* Reviewing and merging has started
* PR will be created EOD 2022-01-21
* Some Ethdev patches under review
- Patchset for rte_flow bulk insertion to review
- Currently no hardware backend
* New driver: Net/SPNIC from @ramaxel.com
* next-net-intel
* Some patches merged to next-net
* next-net-mlx
- Some patches merged and pulled
- Will submit some other patches that are awaiting changes
* next-net-brcm
* Some patchsets merged
* Some more fixes in the pipeline, but nothing major right now
* next-net-mrvl
- Some patches being pushed
- Expecting around 30 patches
* next-eventdev
* 5 patches from Intel
* 15 patches from Marvell
* All under review
* next-virtio
* Some reviewing ongoing
* Reviewing patch on vhost async
* Adding stats to vhost library (probably in 22.07)
* next-crypto
* Not many merges yet
* Starting to review and merge
* main
* Some series for Windows
- Unit tests - awaiting new version
- Threading API - needs reviews
* Patches for Mempool, Ring and EAL
* EAL series from Dmitri under review
* Automated delegation in patchwork
* There is a need for some new maintainers since some have stepped down
* TAP and Bonding in particular
LTS
---
* 21.11.1
* Target April (after 22.03)
* 20.11.4
* Released on 2022-01-17
* 19.11.11
* Released on 2022-01-07
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 21142 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-01-27
@ 2022-01-28 8:42 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-01-28 8:42 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
[-- Attachment #1: Type: text/plain, Size: 2723 bytes --]
Release status meeting minutes 2022-01-27
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed dates for 22.03:
* 22.03 V1 2021-12-31
* 22.03 Merge 2022-02-11
* 22.03 Release 2022-03-11
See also http://core.dpdk.org/roadmap/#dates
And some provisional dates for the subsequent releases:
* 22.07 V1 2022-05-06
* 22.07 Merge 2022-06-10
* 22.07 Release 2022-07-15
* 22.11 V1 2022-09-09
* 22.11 Merge 2022-10-18
* 22.11 Release 2022-11-18
Subtrees
--------
* next-net
* Reviewing and merging progressing
* ICC failing in CI
* next-net-intel
* Some patches merged to next-net
* next-net-mlx
- Some patches merged and pulled
- Will submit some other patches that are awaiting changes
* next-net-brcm
* Currently up to date for RC1
* next-net-mrvl
- Most critical patches are merged
* next-eventdev
* All patches merged for RC1
* next-virtio
* Initial PR sent
* Adding stats to vhost library (probably in 22.07)
* next-crypto
* Some series merged and PR sent
* Other reviews ongoing
* main
* Some series for Windows under review
* - Unit tests - awaiting new version
- Threading API - needs reviews
- https://patches.dpdk.org/project/dpdk/list/?series=20472
* Patches for Mempool, Ring and EAL
* EAL series from Dmitri: Fast restart with many hugepages - needs reviews
* https://patches.dpdk.org/project/dpdk/list/?series=21266
* Automated delegation in patchwork
* There is a need for some new maintainers since some have stepped down
* TAP and Bonding in particular
LTS
---
* 21.11.1
- Target April (after 22.03)
* 20.11.4
- Released on 2022-01-17
* 19.11.11
- Released on 2022-01-07
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 19425 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-02-10
@ 2022-02-10 17:56 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-02-10 17:56 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
[-- Attachment #1: Type: text/plain, Size: 2690 bytes --]
Release status meeting minutes 2022-02-10
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed dates for 22.03:
* 22.03 V1 2021-12-31
* 22.03 Merge 2022-02-11
* 22.03 Release 2022-03-11
See also http://core.dpdk.org/roadmap/#dates
And some provisional dates for the subsequent releases:
* 22.07 V1 2022-04-10
* 22.07 Merge 2022-05-30
* 22.07 Release 2022-07-13
* 22.11 V1 2022-09-14
* 22.11 Merge 2022-10-03
* 22.11 Release 2022-11-16
Subtrees
--------
* next-net
* Reviewing and merging progressing
* Reviewing ethdev patches
* Critical for RC1
* Some still need additional reviews/comments
* Some sub-trees merged and some will be merged ahead of RC1/Friday.
* next-net-intel
* Some patches merged to next-net
* next-net-mlx
* Some patches ready for merge
* next-net-brcm
* Some fixes in the Broadcom sub tree and some in the pipeline.
* next-net-mrvl
* Some patches merged and some will be moved RC2
* next-eventdev
* Some patches merged and some will be moved RC2
* next-virtio
* Prepared a PR
* Working on the vhost async - Maybe for RC1, probably for RC2
* Series about vdpa - deferred
* Series for collecting statistics for vhost - also deferred
* next-crypto
* Waiting on new versions of some cryptodev patches
* Also patches for async API
* Also several PMD changes
* main
* EAL series on fast restart with many hugepages merged
* Windows Threading API - needs reviews
* Doesn't look ready for merge
* Other subtree merging in progress readying for RC1
LTS
---
* 21.11.1
* Target April (after 22.03)
* 20.11.4
* Released on 2022-01-17
* 19.11.11
* Released on 2022-01-07
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 17274 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-03-03
@ 2022-03-06 13:44 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-03-06 13:44 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
[-- Attachment #1: Type: text/plain, Size: 2223 bytes --]
Release status meeting minutes 2022-03-03
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed dates for 22.03:
* 22.03 RC3 2022-03-07
* 22.03 Release 2022-03-11
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for the subsequent releases:
* 22.07 V1 2022-04-10
* 22.07 Merge 2022-05-30
* 22.07 Release 2022-07-13
* 22.11 V1 2022-09-14
* 22.11 Merge 2022-10-03
* 22.11 Release 2022-11-16
Subtrees
--------
* next-net
* Mainly complete. Not many patches left in the backlog
* Some GCC12 build issues
* next-net-intel
* Mostly complete
* next-net-mlx
* Some fixes to be submitted for RC3
* next-net-brcm
* No update
* next-net-mrvl
* Majority of patches merged
* next-eventdev
* Majority of patches merged
* 2-3 other patches for RC3
* next-virtio
* PR ready
* next-crypto
* ~15 patches remaining, mainly fixes
* Some work going on around FIPS
* main
* EAL series on fast restart with many hugepages merged
* Some work going on around sample apps
* RC3 likely on or before Monday 7 March
LTS
---
* 21.11.1
* Backporting progressing
* 20.11.5
* Backporting progressing
* 19.11.12
* Backporting progressing
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15623 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2022-03-10
@ 2022-03-10 20:38 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-03-10 20:38 UTC (permalink / raw)
To: dev; +Cc: thomas, Yigit, Ferruh
[-- Attachment #1: Type: text/plain, Size: 2469 bytes --]
Release status meeting minutes 2022-03-10
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed dates for 22.03 (note, the slight extension of the release date):
* 22.03 RC4 2022-03-14
* 22.03 Release 2022-03-16
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for the subsequent releases:
* 22.07 V1 2022-04-10
* 22.07 Merge 2022-05-30
* 22.07 Release 2022-07-13
* 22.11 V1 2022-09-14
* 22.11 Merge 2022-10-03
* 22.11 Release 2022-11-16
Subtrees
--------
* next-net
* Tree merged to RC3
* Some testpmd fixes outstanding - new reviews or change requests required
* I40e build error from ARM - fix available
* Fixes should now go to main repo directly
* next-net-intel
* Some fixes to be pulled
* next-net-mlx
* Around 8 new patches for fixes since RC3
* next-net-brcm
* No update
* next-net-mrvl
* Some patches/fixes merged to subtree
* next-eventdev
* No outstanding patches
* next-virtio
* PR ready
* next-crypto
* Regression in vhost crypto - Fix completed and merged
* main
* Release candidate 22.03-rc3 released on 2022-03-08
* Some CI build failures on Ubuntu 21.04 and 21.10
* Still quite a few fixes to be merged
* Will collect fixes into RC4 for release/testing on Monday 2022-03-14
* Will target full release for Wednesday 2022-03-16
LTS
---
* 21.11.1
* Backporting progressing
* 20.11.5
* Backporting progressing
* 19.11.12
* Backporting progressing
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15280 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2022-04-14
@ 2022-04-15 12:26 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-04-15 12:26 UTC (permalink / raw)
To: dev; +Cc: thomas
[-- Attachment #1: Type: text/plain, Size: 3024 bytes --]
Release status meeting minutes 2022-04-14
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.07:
* Proposal deadline (RFC/v1 patches): 10 April 2022
* API freeze (-rc1): 30 May 2022
* PMD features freeze (-rc2): 20 June 2022
* Built-in applications features freeze (-rc3): 27 June 2022
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* Proposal deadline (RFC/v1 patches): 14 August 2022
* API freeze (-rc1): 3 October 2022
* PMD features freeze (-rc2): 24 October 2022
* Built-in applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Processing patches
* Shared between Andrew/Ferruh/Thomas
* next-net-intel
* Some patches to pull
* next-net-mlx
* Some patches to pull
* next-net-brcm
* No update
* next-net-mrvl
* Around 15 patches in queue
* next-eventdev
* Around 15 patches in queue
* next-virtio
* Currently reviewing async vhost patches - discussion ongoing
* VirtIO block device Intel vdpa
* Waiting for new revisions
* next-crypto
* 60 patches in backlog
* Some patches from last release
* Series on ipsec-qw under review
* Patchset for new BBDEV Rejected
* Flexran SDK - needs to be removed from Meson and use ipconfig
* main
* EAL patches under review
* Thread series for Windows
* Making progress
* Enabling of ASAN in the CI
* Requires existing ASAN defects to be closed
* https://bugs.dpdk.org/buglist.cgi?quicksearch=%5Basan%5D
* Lock annotations series:
* https://patchwork.dpdk.org/project/dpdk/list/?series=22292
* FreeBSD support for vmbus
* Cleanup series for memory leaks and NULL pointers need reviews:
* https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Sample apps being updated
LTS
---
* 21.11.1
* RC1 for 21.11.1
* Looking for testing before April 13th
* Release targeted for April 26th
* 20.11.5
* Released April 4th
* 19.11.12
* Released April 7th
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 17026 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-04-20
@ 2022-04-21 16:02 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-04-21 16:02 UTC (permalink / raw)
To: dev; +Cc: thomas
[-- Attachment #1: Type: text/plain, Size: 3091 bytes --]
Release status meeting minutes 2022-04-20
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.07:
* Proposal deadline (RFC/v1 patches): 10 April 2022
* API freeze (-rc1): 30 May 2022
* PMD features freeze (-rc2): 20 June 2022
* Builtin applications features freeze (-rc3): 27 June 2022
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* Proposal deadline (RFC/v1 patches): 14 August 2022
* API freeze (-rc1): 3 October 2022
* PMD features freeze (-rc2): 24 October 2022
* Builtin applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Processing patches
* next-net-intel
* 15 patches ready for upstream - waiting for pull
* next-net-mlx
* Some patches ready to pull (by end of the week)
* next-net-brcm
* No update
* next-net-mrvl
* Around 15 patches in queue
* next-eventdev
* Around 15 patches in queue
* next-virtio
* Currently reviewing
* Async vhost patches - discussion ongoing
* Vitio block device Intel vdpa
* Waiting for new revisions
* next-crypto
* Starting merging some patches
* Will look at sync patches next week
* Test security app needs review
* main
* Merged some EAL patches
* Thread series for Windows
* Making progress
* Enabling of ASAN in the CI
* Making progress
* Found issue with CI
* https://bugs.dpdk.org/buglist.cgi?quicksearch=%5Basan%5D
* Lock annotations series:
* https://patchwork.dpdk.org/project/dpdk/list/?series=22292
* FreeBSD support for vmbus
* Cleanup series for memory leaks and NULL pointers need reviews:
* https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Sample apps being updated
* Header split patchset needs review
* http://patchwork.dpdk.org/project/dpdk/patch/20220402104109.472078-2-wenxuanx.wu@intel.com/
LTS
---
* 21.11.1
* RC1 for 21.11.1
* Looking for testing before April 13th
* Release targeted for April 26th
* 20.11.5
* Released April 4th
* 19.11.12
* Released April 7th
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 17369 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-05-05
@ 2022-05-09 19:39 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-05-09 19:39 UTC (permalink / raw)
To: dev
[-- Attachment #1: Type: text/plain, Size: 3263 bytes --]
Release status meeting minutes 2022-05-05
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Debian/Microsoft
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.07:
* Proposal deadline (RFC/v1 patches): 10 April 2022
* API freeze (-rc1): 30 May 2022
* PMD features freeze (-rc2): 20 June 2022
* Built-in applications features freeze (-rc3): 27 June 2022
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* Proposal deadline (RFC/v1 patches): 14 August 2022
* API freeze (-rc1): 3 October 2022
* PMD features freeze (-rc2): 24 October 2022
* Built-in applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Moving forward with merging patches
* next-net-intel
* 18 patches ready for merge
* next-net-mlx
* Some patches pushed to next-net
* next-net-brcm
* No update
* next-net-mrvl
* 20 patches merged
* 14 patches in queue
* next-eventdev
* 20+ patches merged under review or pending merge
* next-virtio
* Fixing checksum bugs in virtio
* New version of Async vhost patches - getting closer to merge
* next-crypto
* 30 patches merged and 20 ready to be merged
* New PMD from Atomic Rules
* main
* Looking at Thread patch series for Windows
* Progressing - needs reviews
* Enabling of ASAN in the CI
* Some blocking issues
* Fix sent by Anatoly
* Lock annotations series:
* https://patchwork.dpdk.org/project/dpdk/list/?series=22292
* Needs docs and remerge after Maxime's changes
* Cleanup series for memory leaks and NULL pointers need reviews:
* https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Sample apps being updated
* Header split patchset needs review
* http://patchwork.dpdk.org/project/dpdk/patch/20220402104109.472078-2-wenxuanx.wu@intel.com/
* Docs fix for ETH and VLAN flow items in Support Matrix from Ilya needs review/merge
* https://patchwork.dpdk.org/project/dpdk/patch/20220316120157.390311-1-i.maximets@ovn.org/
* Public meeting on: ethdev: datapath-focused meter actions
* http://mails.dpdk.org/archives/dev/2022-April/239961.html
LTS
---
* 21.11.1
* Released April 26th
* 20.11.5
* Released April 4th
* 19.11.12
* Released April 7th
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 17713 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-19-05
@ 2022-05-20 19:30 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-05-20 19:30 UTC (permalink / raw)
To: dev; +Cc: thomas
[-- Attachment #1: Type: text/plain, Size: 3543 bytes --]
Release status meeting minutes 2022-19-05
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Debian/Microsoft
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the current dates for 22.07:
* Proposal deadline (RFC/v1 patches): 10 April 2022
* API freeze (-rc1): 6 June May 2022 - **Note change from 30 May**
* PMD features freeze (-rc2): 20 June 2022
* Builtin applications features freeze (-rc3): 27 June 2022
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* Proposal deadline (RFC/v1 patches): 14 August 2022
* API freeze (-rc1): 3 October 2022
* PMD features freeze (-rc2): 24 October 2022
* Builtin applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Moving forward with merging patches
* next-net-intel
* Some patches waiting to be pulled
* next-net-mlx
* Some patches pushed to next-net
* More work ongoing
* next-net-brcm
* No update
* next-net-mrvl
* Almost all patches merged and pulled
* Some fixes required - could go in RC2
* next-eventdev
* 20+ patches merged - almost all merged
* 1 patchset for DLB has comments and will wait for RC2
* next-virtio
* Reviewing vdpa/ifc patchset to support for virtio block devices
* Working on patchset for vhost software checksum in the Rx path
* Reviewed vhost per queue statistics patchset
* Async vhost patches merged
* next-crypto
* Some patches reviewed and merged
* Asymmetric crypto under review
* main
* RC1 will move to June 6th 2022
* Thread patch series for Windows - ready for merge
* EAL patches ready to merge
* Enabled ASAN checking in the CI
* Patchset to support DPDK on 64bit RISC-V architecture
* This is a new architecture
* Lock annotations series:
* https://patchwork.dpdk.org/project/dpdk/list/?series=22292
* Needs docs
* Cleanup series for memory leaks and NULL pointers need reviews:
* https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Header split patchset needs review
* http://patchwork.dpdk.org/project/dpdk/patch/20220402104109.472078-2-wenxuanx.wu@intel.com/
* GCC 12 issues
* There is a patchset to disable the new warnings and allow compilation but some
should be fixed: https://patchwork.dpdk.org/project/dpdk/list/?series=22993
* RFC to split driver specific commands out of testpmd
* https://patchwork.dpdk.org/project/dpdk/list/?series=23000&state=*
LTS
---
* 21.11.1
* Released April 26th
* 20.11.5
* Released April 4th
* 19.11.12
* Released April 7th
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains DPDK 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 18388 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-06-09
@ 2022-06-09 19:39 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-06-09 19:39 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2962 bytes --]
Release status meeting minutes 2022-06-09
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Debian/Microsoft
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.07:
* Proposal deadline (RFC/v1 patches): 10 April 2022
* API freeze (-rc1): 6 June 2022 - Actual 8 June
* PMD features freeze (-rc2): 20 June 2022
* Builtin applications features freeze (-rc3): 27 June 2022
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* Proposal deadline (RFC/v1 patches): 14 August 2022
* API freeze (-rc1): 3 October 2022
* PMD features freeze (-rc2): 24 October 2022
* Builtin applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* RC1 complete
* Some more Testpmd and driver patches for after RC1
* next-net-intel
* No update
* next-net-mlx
* No update
* next-net-brcm
* No update
* next-net-mrvl
* Patches merged for RC1
* ~ 25 patches in queue for RC2
* next-eventdev
* ~ 15 patches queued for RC2
* next-virtio
* ~ 40 patches merged
* Vhost Aysnc
* Per queue statistics
* Virtio block support for vdpa
* ~ 40 patches in queue for RC2
* Big series from Nvidia posted on Monday.
Will probably be pushed to next release.
* next-crypto
* ~ 30 patches in queue for RC2
* Series on OpenSSL 3.0 ongoing
* main
* Windows thread patch series merged but needs some followup
* Risc V series merged
* Lock annotations series postponed to next release
* Cleanup series for memory leaks and NULL pointers need reviews:
* https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Header split patchset
* Non-RFC version merged but not yet enabled for all drivers
* GCC 12 fixes
* 2 proposals - WIP
LTS
---
Note, there is a proposal to merge security fixes to all 3 LTS branches
by August 28th.
* 21.11.1
* Released April 26th
* 20.11.5
* Released April 4th
* 19.11.12
* Released April 7th
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15602 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-06-16
@ 2022-06-16 10:31 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-06-16 10:31 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3610 bytes --]
Release status meeting minutes 2022-06-16
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.07:
* Proposal deadline (RFC/v1 patches): 10 April 2022
* API freeze (-rc1): 6 June 2022 - Actual 8 June
* PMD features freeze (-rc2): 23 June 2022 - Changed from 20 June
* Builtin applications features freeze (-rc3): 30 June 2022 - Changed from 27 June
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* Proposal deadline (RFC/v1 patches): 14 August 2022
* API freeze (-rc1): 3 October 2022
* PMD features freeze (-rc2): 24 October 2022
* Builtin applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* RC1 complete
* Some more Testpmd and driver patches for after RC1
* next-net-intel
* 3 patches waiting for upstream
* 1 patch waiting for ARM's feedback on performance numbers
* next-net-mlx
* Merged 7 patches
* 1 other patchset being prepared for RC2
* Also some fixes
* next-net-brcm
* No update
* next-net-mrvl
* ~ 15 patches in queue for RC2
* Will submit PR Friday 17 June
* next-eventdev
* 2 patches from Intel for RC2
* Will submit PR Friday 17 June
* next-virtio
* A lot of patches ready and preparing for RC2 PR
* Work continuing on:
* Patches for vHost Aync
* Checksum offload
* Large patchset for MLX5 is pending
* next-crypto
* Applied around 20 patches
* 20 more remaining for RC2
* Patches on ipsec gateway that need reviews
* Patch for adding CMAC to OpenSSL
* Patch for Windows enablement of test application
* main
* Working on fixes to vHost Crypto and IPsec unit tests
* Cleanup series for memory leaks and NULL pointers need reviews:
* https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Will be merged if there are no reviews
* Header split patchset
* Non-RFC version merged but not yet enabled for all drivers
* GCC 12 fixes
* Merged patches agreed by Stephen and some other maintainers
* Note there is an issue where compilation of the CNXK drivers
is consuming too much memory, and time in the link stage:
* https://mails.dpdk.org/archives/dev/2022-June/244227.html
* If anyone has any suggestions let us know
LTS
---
Note, there is a proposal to merge security fixes to all 3 LTS branches
by August 28th.
* 21.11.2
* Back porting ongoing
* 21.11.1 released April 26th
* 20.11.6
* Backporting waiting for Rc2
* 20.11.5 released April 4th
* 19.11.13
* Backporting waiting for Rc2
* 19.11.12 released April 7th
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the status of the master tree and sub-trees, and for project managers to track progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16917 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-06-23
@ 2022-06-23 9:26 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-06-23 9:26 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3057 bytes --]
Release status meeting minutes 2022-06-23
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.07:
* Proposal deadline (RFC/v1 patches): 10 April 2022
* API freeze (-rc1): 6 June 2022 - Actual 8 June
* PMD features freeze (-rc2): 23 June 2022
* Built-in applications features freeze (-rc3): 30 June 2022
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* Proposal deadline (RFC/v1 patches): 14 August 2022
* API freeze (-rc1): 3 October 2022
* PMD features freeze (-rc2): 24 October 2022
* Built-in applications features freeze (-rc3): 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Majority of patches pulled in prep for RC2
* Some patches still under review
* Awaiting patch update from NFP
* next-net-intel
* 4 patches waiting for upstream
* Looking at fix for GCC12 issue in ice driver
* next-net-mlx
* Awaiting pull for RC2
* next-net-brcm
* No update
* next-net-mrvl
* PR sent for RC2
* 3 more patches - maybe TC2
* Issue with GCC12 on qede driver
* next-eventdev
* Merged
* No more patches pending
* next-virtio
* PR prepared and merged
* Contains new MLX5 patchset
* Only fixes and docs in queue
* next-crypto
* Crypto is merged
* Some fixes and other patches for RC3
* main
* Prepping for RC2
* Merging EAL patches
* Still working through GCC12 issues
* IP fragmentation patch still under discussion
* Some followups on Thread API for Windows - from Microsoft
* Cleanup series for memory leaks and NULL pointers need reviews:
* https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Will be merged if there are no reviews
* RC2 should be out 2022-05-24
* Ping Thomas if there are important features that need to be in RC2
LTS
---
* 21.11.2
* Back porting in progress
* 21.11.1 released April 26th
* 20.11.6
* Backporting waiting for RC2
* 20.11.5 released April 4th
* 19.11.13
* Backporting waiting for RC2
* 19.11.12 released April 7th
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15688 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-06-30
@ 2022-06-30 10:47 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-06-30 10:47 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3219 bytes --]
Release status meeting minutes 2022-06-30
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.07:
* V1 deadline: 10 April 2022
* RC1: 8 June 2022
* RC2: 23 June 2022
* RC3: 4 July 2022 - was 30 June 2022
* RC4: 8 July 2022
* Release: 13 July 2022
Updated dates are posted shortly after they are changed at:
http://core.dpdk.org/roadmap/#dates
Here are some provisional dates for 22.11:
* V1 deadline: 14 August 2022
* RC1: 3 October 2022
* RC2: 23 June 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* RC2 released
* Prepping for RC3
* Patch for MTU in PCAP Driver - needs reviews
* next-net-intel
* Get update
4 patches waiting for upstream
* Looking at fix for GCC12 issue in ice driver
* next-net-mlx
* 2 small patches for private testpmd
* next-net-brcm
* No update
* next-net-mrvl
* Mainly complete after RC2
* next-eventdev
* Some fixes from Intel
* next-virtio
* Some reviews to do
* Prepping a PR for RC3 around docs and fixes
* next-crypto
* Most patches merged in RC2
* Looking at docs and fixes
* main
* Merged last fixes for GCC 12
* Still some issues with cross compilation
* Merged NULL pointer/checks patches
* Series for memory leaks needs some rework
* Sent first RFC on rte_bus
* Please send **and** review deprecation notices:
https://patchwork.dpdk.org/project/dpdk/list/?series=&q=deprecat
Other
-----
* DPDK Summit: https://events.linuxfoundation.org/dpdk-userspace-summit/
* Call for papers: https://linuxfoundation.smapply.io/prog/dpdk_userspace_summit_2022/
Dates to Remember:
CFP Opens: Monday, June 27 at 12:00 am PDT
CFP Closes: Friday, July 22 at 11:59 PM PDT
Speaker Notifications: August 1
Schedule Announcement: Week of August 1
Presentation Slide Due Date: Tuesday, August 30
Event Dates: Tuesday, September 6 - Thursday, September 8, 2022
LTS
---
* 21.11.2
* Back porting in progress
* 21.11.1 released April 26th
* 20.11.6
* Backporting waiting for RC2
* 20.11.5 released April 4th
* 19.11.13
* Backporting waiting for RC2
* 19.11.12 released April 7th
* Distros
* v20.11 in Debian 11
* 22.04 will contain 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 17126 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-08-05
@ 2022-08-05 14:26 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-08-05 14:26 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]
Release status meeting minutes 2022-08-05
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 14 August 2022
* RC1: 3 October 2022
* RC2: 23 June 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* New drivers in this release
* next-net-intel
* No update
* next-net-mlx
* No update
* next-net-brcm
* No update
* next-net-mrvl
* 30-40 patches in this release
* next-eventdev
* Some patches from Intel
* Probably 30-40 patches
* next-virtio
* Currently ~16 patches in the release
* Chenbo will cover this release
* next-crypto
* Patches for BBDev
* Adding crypto security and sessions rework
* Additional FIPs validation patches in this release
* main
* Need to start reviews early on the mailing list
* Machine learning inference library RFC:
* https://inbox.dpdk.org/dev/20220803132839.2747858-1-jerinj@marvell.com/
Other
-----
* DPDK Summit: https://events.linuxfoundation.org/dpdk-userspace-summit/
* Event Dates: Tuesday, September 6 - Thursday, September 8, 2022
LTS
---
Waiting for test results. Aiming for August 29th for all 3 LTSs.
* 21.11.2
* Back porting in progress
* 20.11.6
* Back porting in progress
* 19.11.13
* Back porting in progress
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13624 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2022-08-18
@ 2022-08-18 10:38 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-08-18 10:38 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2370 bytes --]
Release status meeting minutes 2022-08-18
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat [No]
* Xilinx/AMD [No]
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022 (previously 14 August)
* RC1: 3 October 2022
* RC2: 23 June 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* New drivers in this release
* next-net-intel
* No update
* next-net-mlx
* Bug fixes
* next-net-brcm
* No update
* next-net-mrvl
* 30-40 patches in this release
* next-eventdev
* Some patches from Intel
* Probably 30-40 patches
* next-virtio
* Around 20 patches in list
* Several vhost patches
* next-crypto
* 150+ patches
* Some applied
* Patches for BBDev
* Adding crypto security and sessions rework
* Additional FIPs validation patches in this release
* main
* Several maintainers still on holiday
* Decision to push v1 deadline to Wednesday August 24th
Other
-----
* DPDK Summit: https://events.linuxfoundation.org/dpdk-userspace-summit/
* Event Dates: Tuesday, September 6 - Thursday, September 8, 2022
* Schedule: https://events.linuxfoundation.org/dpdk-userspace-summit/program/schedule/
LTS
---
Waiting for test results. Aiming for August 29th for all 3 LTSs.
* 21.11.2
* Back porting in progress
* 20.11.6
* Back porting in progress
* 19.11.13
* Back porting in progress
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14045 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2022-08-25
@ 2022-08-25 13:43 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-08-25 13:43 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3154 bytes --]
Release status meeting minutes 2022-08-25
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022 (previously 14 August)
* RC1: 3 October 2022
* RC2: 23 October 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* New drivers in this release
* Microsoft Azure Network Adapter (MANA) PMD
* There are several RDMA implementation now.
* Should we have RDMA bus driver?
* Google Virtual Ethernet (GVE)
* idpf (Infrastructure Data Path Function) PMD
* net/qdma PMD
* Work on removing deprecated flow API/code - needs acks from Intel
* https://lore.kernel.org/all/20220812191827.3187441-1-ivan.malov@oktetlabs.ru/
* Flow director clean-up also needs a lot of code change from Intel
* https://patches.dpdk.org/project/dpdk/list/?series=24187
* next-net-intel
* Some patches merged and awaiting pull
* next-net-mlx
* No update
* next-net-brcm
* No update
* next-net-mrvl
* 30-40 patches in this release
* next-eventdev
* Probably 30-40 patches in this release
* next-virtio
* Around 30 patches in queue
* Several vhost patches
* next-crypto
* 150+ patches
* Some reviewed and will be applied
* Patches for BBDev - needs review
* Adding crypto security and sessions rework
* Additional FIPs validation patches in this release
* main
* V1 deadline was Wednesday August 24th
* New arch type: LoongArch
* Proposed RC1 date (3 October) clashes with a national holiday
in PRC (October 1st - ~October 7th). We may need to push RC1
to October 10th, but that is late, so this needs some
consideration/discussion.
Other
-----
* DPDK Summit: https://events.linuxfoundation.org/dpdk-userspace-summit/
* Event Dates: Tuesday, September 6 - Thursday, September 8, 2022
* Schedule: https://events.linuxfoundation.org/dpdk-userspace-summit/program/schedule/
LTS
---
Waiting for test results. Aiming for August 29th for all 3 LTSs.
* 21.11.2
* Back porting in progress
* 20.11.6
* Back porting in progress
* 19.11.13
* Back porting in progress
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16258 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-09-01
@ 2022-09-01 8:58 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-09-01 8:58 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3000 bytes --]
Release status meeting minutes 2022-09-01
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022 (previously 14 August)
* RC1: 3 October 2022 (subject to discussion)
* RC2: 23 October 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* New drivers in this release
* Microsoft Azure Network Adapter (MANA) PMD
* There are several RDMA implementation now.
* Should we have RDMA bus driver?
* Google Virtual Ethernet (GVE)
* idpf (Infrastructure Data Path Function) PMD
* net/qdma PMD
* Work on removing deprecated flow API/code - needs acks from Intel
* https://lore.kernel.org/all/20220812191827.3187441-1-ivan.malov@oktetlabs.ru/
* Flow director clean-up merged
* next-net-intel
* No update
* next-net-mlx
* No update
* next-net-brcm
* No update
* next-net-mrvl
* Started merging patches
* Reviews ongoing
* next-eventdev
* Started merging patches
* Reviews ongoing
* next-virtio
* Around 30 patches in queue
* Several vhost patches
* next-crypto
* 3-35 patches merged
* Patches for BBDev - needs review
* Adding crypto security and sessions rework
* Additional FIPs validation patches in this release
* main
* New arch type: LoongArch
* Proposed RC1 date (3 October) clashes with a national holiday
in PRC (October 1st - ~October 7th). We may need to push RC1
to October 10th, but that is late, so this needs some
consideration/discussion.
* DPDK EU summit next week.
Other
-----
* DPDK Summit: https://events.linuxfoundation.org/dpdk-userspace-summit/
* Event Dates: Tuesday, September 6 - Thursday, September 8, 2022
* Schedule: https://events.linuxfoundation.org/dpdk-userspace-summit/program/schedule/
LTS
---
Waiting for test results. Aiming for August 29th for all 3 LTSs.
* 21.11.2
* Back porting in progress
* 20.11.6
* Back porting in progress
* 19.11.13
* Back porting in progress
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15783 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-09-15
@ 2022-09-15 21:49 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-09-15 21:49 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]
Release status meeting minutes 2022-09-15
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD [No]
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 3 October 2022
* RC2: 23 October 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Ethdev reviews ongoing
* Some patches merged
* New drivers in this release
* Microsoft Azure Network Adatper (MANA) PMD
* There are several RDMA implementation now.
* Should we have RDMA bus driver?
* Google Virtual Ethernet (GVE)
* idpf (Infrastructure Data Path Function) PMD
* net/qdma PMD
* next-net-intel
* Patches waiting for pull
* next-net-mlx
* No update
* next-net-brcm
* No update
* next-net-mrvl
* Patches pushed and waiting for pull
* next-eventdev
* Patches pushed and waiting for pull
* next-virtio
* Issue in 22.11 branch causing deadlock in vHost
* next-crypto
* 30-35 patches merged and awaiting pull
* Review of crypto security and sessions rework patches
* Call for review comments from community because it
affects a lot of drivers
* Patches around BBDev
* ACC 100/200 patches
* FIPs validation patches need reviews acks
* Asym changes under review
* main
* Looking at EAL patches
* Windows Thread series has updates
* New arch type: LoongArch
* MLX5 new features coming around rte_flow
* CC Thomas for attention any patchsets that need early merge
LTS
---
Waiting for test results. LTS release on August 29th.
* 21.11.2
* 20.11.6
* 19.11.13
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialled for 19.11 to the 20.11 LTS cycle.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14288 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-09-22
@ 2022-09-22 18:24 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-09-22 18:24 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 4340 bytes --]
Release status meeting minutes 2022-09-22
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 3 October 2022
* RC2: 23 October 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Ethdev patches remaining
* Need reviews
* NPF driver needs review
* https://patches.dpdk.org/project/dpdk/list/?series=24678
* Sets up internal ethdev to communicate with firmware
* Uses OVS specific/duplicated structs
* New drivers in this release
* Microsoft Azure Network Adapter (MANA) PMD
* V9 is out and under review
* Google Virtual Ethernet (GVE)
* Some discussion on MIT licenced code
* idpf (Infrastructure Data Path Function) PMD
* net/qdma PMD
* Awaiting reply from submitter
* Memif driver needs reviews from maintainer
* next-net-intel
* No update this week
* next-net-mlx
* No update this week
* Some big changes to come
* next-net-mrvl
* Patches merged and waiting for pull
* next-eventdev
* Patches merged and waiting for pull
* Some driver dependencies with next-net-mrvl
* ~10 other patches
* next-virtio
* Issue in 22.11 branch causing deadlock in vHost
* Fix merged. Will need backport
* vhost call API safe call causes deadlock SPDK
* SPDK will use a workaround with new API
* next-crypto
* 30-35 patches merged and awaiting pull
* Review of crypto security and sessions rework patches
* Call for review comments from community because it
affects a lot of drivers
* This is a much needed clean-up
* Patches around BBDev
* ACC 100/200 patches
* FIPs validation patches need reviews acks
* Asym changes under review
* main
* Subtrees not pulled yet
* Large rte_device rework done by David
* Bus and device clean-up to hide rte_bus, rte_drive
and rte_device objects
* Changes code in buses in a lot of drivers
* Will need support from sub-tree maintainers
* Looking at EAL patches
* Windows Thread series has updates
* New arch type: LoongArch
* MLX5 new features coming around rte_flow
* CC Thomas for attention to any patchsets that need early merge
* We will have 3 release cycles next year. Initial proposed schedule
Below based on last year's dates.
Proposed Schedule for 2023
--------------------------
23.04
* Proposal deadline (RFC/v1 patches): 30 December 2022
* API freeze (-rc1): 10 February 2023
* PMD features freeze (-rc2): 24 February 2023
* Builtin applications features freeze (-rc3): 3 March 2023
* Release: 10 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 7 April 2023
* API freeze (-rc1): 26 May 2023
* PMD features freeze (-rc2): 16 June 2023
* Builtin applications features freeze (-rc3): 23 June 2023
* Release: 14 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 11 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 17 November 2023
Other
-----
* TBA
LTS
---
LTSes released on August 29th.
* 21.11.2
* 20.11.6
* 19.11.13
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialed for 19.11 to the 20.11 LTS cycle.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 20092 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-10-06
@ 2022-10-06 14:27 14% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-10-06 14:27 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 4584 bytes --]
Release status meeting minutes 2022-10-06
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM [No]
* Canonical [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 7 October 2022 - Was 3 October
* RC2: 23 October 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* 2 series critical for this release
* Protocol based buffer split
* Additional contention management - Need review/ack from Jerin
* Hairpin feature is pending
* Ethdev 2 series targeted for this release
* Dumping Rx/Tx descriptors - will go in next release
* Recovering events sent by driver - has comments that need to be addressed
* NPF driver merged
* New drivers in this release:
* Microsoft Azure Network Adapter (MANA) PMD
* New version sent today - looks good for merge
* Google Virtual Ethernet (GVE)
* Some discussion on MIT licenced code
* Needs tech board review + governing board review
* idpf (Infrastructure Data Path Function) PMD
* Reviewed but awaiting replies to comments
* Needs additional explanation of the intention/scope
* net/qdma PMD
* Awaiting reply from submitter
* Memif driver needs reviews from maintainer
* next-net-intel
* Being merged - too many things to fix
* next-net-mlx
* Waiting for RC1
* Some big changes to come on hardware steering for RC2
* next-net-mrvl
* Waiting for RC1
* next-eventdev
* Waiting for RC1
* next-virtio
* PR pulled for RC1
* Fix for gcc12 with LoongArch and with ARM64
* Issue in 22.11 branch causing deadlock in vHost
* Fix merged. Will need backport
* vhost call API safe call causes deadlock SPDK
* SPDK will use a workaround with new API
* next-crypto
* Most patches merged
* Review of crypto security and sessions rework patches
* Call for review comments from community because it
affects a lot of drivers
* This is a much needed clean-up
* Patches around BBDev
* ACC 100/200 patches
* FIPs validation patches need reviews acks
* Asym changes under review
* main
* 3 series for RC1 still in progress
* Windows
* LoongArch
* Telemetry series
* Memarea needs reviews in order to get it into this release
* Member library - adding NitroSketch
* Power library targeting RC1
* Needs other reviews
* Will also be targeted by AMD
* Bus and device clean up to hide rte_bus, rte_drive
and rte_device objects
* Changes needed in other bus drivers
* New arch type LoongArch is in queue
* RC1 targeted for Friday 8
Proposed Schedule for 2023
23.03
* Proposal deadline (RFC/v1 patches): 30 December 2022
* API freeze (-rc1): 10 February 2023
* PMD features freeze (-rc2): 24 February 2023
* Builtin applications features freeze (-rc3): 3 March 2023
* Release: 10 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 7 April 2023
* API freeze (-rc1): 26 May 2023
* PMD features freeze (-rc2): 16 June 2023
* Builtin applications features freeze (-rc3): 23 June 2023
* Release: 14 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 11 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 17 November 2023
Other
-----
* TBA
LTS
---
LTSes released on August 29th.
* 21.11.2
* 20.11.6
* 19.11.13
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialed for 19.11 to the 20.11 LTS cycle.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 21169 bytes --]
^ permalink raw reply [relevance 14%]
* DPDK Deprecation Notice Review Meeting 2022-09-30
@ 2022-10-06 15:14 6% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-10-06 15:14 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand, orika
[-- Attachment #1: Type: text/plain, Size: 12272 bytes --]
DPDK Deprecation Notice Review Meeting 2022-09-30
=================================================
DPDK Community member met and reviewed the status of the DPDK
deprecation notices prior to the RC1 deadline. The source document
is https://git.dpdk.org/dpdk/tree/doc/guides/rel_notes/deprecation.rst
copied below.
Key messages:
* We should do periodic community reviews of the deprecation notices
and in particular at the start of the yy.11 cycle.
* We could group long standing deprecations notices at the start of
the doc in a section that is separate from the notices that are
specific to the current yy.11.
* Notes to the notices are inline below and prefixed with ">".
Deprecation Notices
-------------------
* kvargs: The function ``rte_kvargs_process`` will get a new parameter
for returning key match count. It will ease handling of no-match case.
> Won't make it into this release.
* eal: RTE_FUNC_PTR_OR_* macros have been marked deprecated and will be removed
in the future. Applications can use ``devtools/cocci/func_or_ret.cocci``
to update their code.
> This is still relevant to current and future releases.
* eal: The function ``rte_eal_remote_launch`` will return new error codes
after read or write error on the pipe, instead of calling ``rte_panic``.
> partially done may need other rte_panic removed
* rte_atomicNN_xxx: These APIs do not take memory order parameter. This does
not allow for writing optimized code for all the CPU architectures supported
in DPDK. DPDK has adopted the atomic operations from
https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html. These
operations must be used for patches that need to be merged in 20.08 onwards.
This change will not introduce any performance degradation.
> This is still relevant to current and future releases.
* rte_smp_*mb: These APIs provide full barrier functionality. However, many
use cases do not require full barriers. To support such use cases, DPDK has
adopted atomic operations from
https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html. These
operations and a new wrapper ``rte_atomic_thread_fence`` instead of
``__atomic_thread_fence`` must be used for patches that need to be merged in
20.08 onwards. This change will not introduce any performance degradation.
> This is still relevant to current and future releases.
* bus: The ``dev->device.numa_node`` field is set by each bus driver for
every device it manages to indicate on which NUMA node this device lies.
When this information is unknown, the assigned value is not consistent
across the bus drivers.
In DPDK 22.11, the default value will be set to -1 by all bus drivers
when the NUMA information is unavailable.
> This is in progress.
* kni: The KNI kernel module and library are not recommended for use by new
applications - other technologies such as virtio-user are recommended instead.
Following the DPDK technical board
`decision <https://mails.dpdk.org/archives/dev/2021-January/197077.html>`_
and `refinement <http://mails.dpdk.org/archives/dev/2022-June/243596.html>`_:
* Some deprecation warnings will be added in DPDK 22.11.
* The KNI example application will be removed from DPDK 22.11.
* The KNI kernel module, library and PMD will be removed from the DPDK 23.11.
> We should add a compilation and/or dmesg deprecation warning @ferruh
* lib: will fix extending some enum/define breaking the ABI. There are multiple
samples in DPDK that enum/define terminated with a ``.*MAX.*`` value which is
used by iterators, and arrays holding these values are sized with this
``.*MAX.*`` value. So extending this enum/define increases the ``.*MAX.*``
value which increases the size of the array and depending on how/where the
array is used this may break the ABI.
``RTE_ETH_FLOW_MAX`` is one sample of the mentioned case, adding a new flow
type will break the ABI because of ``flex_mask[RTE_ETH_FLOW_MAX]`` array
usage in following public struct hierarchy:
``rte_eth_fdir_flex_conf -> rte_eth_fdir_conf -> rte_eth_conf (in the middle)``.
Need to identify this kind of usages and fix in 20.11, otherwise this blocks
us extending existing enum/define.
One solution can be using a fixed size array instead of ``.*MAX.*`` value.
> We need some documentation, in the contributors guide or the programmers guide
on how to deal with this. There is general agreement that having a MAX value
in an enum is a bad idea for ABI but developers like using this as a sentinal
or array size value so some people have been using "reserved" padding values
in enums to workaround this restrictions. The community should agree, and
document, what is acceptable.
* ethdev: The function ``rte_eth_set_queue_rate_limit`` takes ``rate`` in Mbps.
The queue rate is limited to 64 Gbps because declared as ``uint16_t``.
The ``rate`` parameter will be modified to ``uint32_t`` in DPDK 22.11
so that it can work for more than 64 Gbps.
> Patch submitted need ack from Intel and NXT.
> https://patches.dpdk.org/project/dpdk/patch/1664344318-3594-1-git-send-email-skoteshwar@marvell.com/
* ethdev: Since no single PMD supports ``RTE_ETH_RX_OFFLOAD_HEADER_SPLIT``
offload and the ``split_hdr_size`` field in structure ``rte_eth_rxmode``
to enable per-port header split, they will be removed in DPDK 22.11.
The per-queue Rx packet split offload ``RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT``
can still be used, and it is configured by ``rte_eth_rxseg_split``.
> Acked and will be merge
> https://patches.dpdk.org/project/dpdk/patch/20220812031313.87385-1-xuan.ding@intel.com/
* ethdev: Announce moving from dedicated modify function for each field,
to using the general ``rte_flow_modify_field`` action.
> This is still relevant to current and future releases.
* ethdev: The flow API matching pattern structures, ``struct rte_flow_item_*``,
should start with relevant protocol header.
Some matching pattern structures implements this by duplicating protocol header
fields in the struct. To clarify the intention and to be sure protocol header
is intact, will replace those fields with relevant protocol header struct.
In v21.02 both individual protocol header fields and the protocol header struct
will be added as union, target is switch usage to the protocol header by time.
In v21.11 LTS, protocol header fields will be cleaned and only protocol header
struct will remain.
> Some work still ongoing, may need to go into RC2 but should be in RC1
> Best effort for RC1, and then list any missing structs in the docs.
* ethdev: Queue specific stats fields will be removed from ``struct rte_eth_stats``.
Mentioned fields are: ``q_ipackets``, ``q_opackets``, ``q_ibytes``, ``q_obytes``,
``q_errors``.
Instead queue stats will be received via xstats API. Current method support
will be limited to maximum 256 queues.
Also compile time flag ``RTE_ETHDEV_QUEUE_STAT_CNTRS`` will be removed.
> This deprecation notice will stay.
* ethdev: Items and actions ``PF``, ``VF``, ``PHY_PORT``, ``PORT_ID`` are
deprecated as hard-to-use / ambiguous and will be removed in DPDK 22.11.
> Some have been removed as part of a patch series. The deprecation notice will
need to change to reflect.
* ethdev: The use of attributes ``ingress`` / ``egress`` in "transfer" flows
is deprecated as ambiguous with respect to the embedded switch. The use of
these attributes will become invalid starting from DPDK 22.11.
> There is a patch in progress for this.
* ethdev: Actions ``OF_SET_MPLS_TTL``, ``OF_DEC_MPLS_TTL``, ``OF_SET_NW_TTL``,
``OF_COPY_TTL_OUT``, ``OF_COPY_TTL_IN`` are deprecated as not supported by
any PMD, so they will be removed in DPDK 22.11.
> Patch has been submitted
* ethdev: Actions ``OF_DEC_NW_TTL``, ``SET_IPV4_SRC``, ``SET_IPV4_DST``,
``SET_IPV6_SRC``, ``SET_IPV6_DST``, ``SET_TP_SRC``, ``SET_TP_DST``,
``DEC_TTL``, ``SET_TTL``, ``SET_MAC_SRC``, ``SET_MAC_DST``, ``INC_TCP_SEQ``,
``DEC_TCP_SEQ``, ``INC_TCP_ACK``, ``DEC_TCP_ACK``, ``SET_IPV4_DSCP``,
``SET_IPV6_DSCP``, ``SET_TAG``, ``SET_META`` are marked as legacy and
superseded by the generic MODIFY_FIELD action.
The legacy actions should be deprecated in 22.07, once MODIFY_FIELD
alternative is implemented.
The legacy actions should be removed in DPDK 22.11.
> Should be grouped with ??? notice above, and the specific drivers named.
> There was a proposal to have an earlier removal date, at the very start
> of the xx.11 period so that code is changed/tested in time for RC1.
* ethdev: The enum ``rte_eth_event_ipsec_subtype`` will be extended to add
new subtype values ``RTE_ETH_EVENT_IPSEC_SA_PKT_EXPIRY``,
``RTE_ETH_EVENT_IPSEC_SA_BYTE_HARD_EXPIRY`` and
``RTE_ETH_EVENT_IPSEC_SA_PKT_HARD_EXPIRY`` in DPDK 22.11.
> Merged
* bbdev: ``RTE_BBDEV_OP_TYPE_COUNT`` terminating the ``rte_bbdev_op_type``
enum will be deprecated and instead use fixed array size when required
to allow for future enum extension.
Will extend API to support new operation type ``RTE_BBDEV_OP_FFT`` as per
this `RFC <https://patches.dpdk.org/project/dpdk/list/?series=22111>`__.
New members will be added in ``rte_bbdev_driver_info`` to expose
PMD queue topology inspired by
this `RFC <https://patches.dpdk.org/project/dpdk/list/?series=22076>`__.
New member will be added in ``rte_bbdev_driver_info`` to expose
the device status as per
this `RFC <https://patches.dpdk.org/project/dpdk/list/?series=23367>`__.
This should be updated in DPDK 22.11.
> This involves several patches, some will be merged
* cryptodev: Hide structures ``rte_cryptodev_sym_session`` and
``rte_cryptodev_asym_session`` to remove unnecessary indirection between
session and the private data of session. An opaque pointer can be exposed
directly to application which can be attached to the ``rte_crypto_op``.
> Patches submitted. One issue with security below.
* cryptodev: The function ``rte_cryptodev_cb_fn`` will be updated
to have another parameter ``qp_id`` to return the queue pair ID
which got error interrupt to the application,
so that application can reset that particular queue pair.
> Will be removed without any objections(? note unclear)
* security: Hide structure ``rte_security_session`` and expose an opaque
pointer for the private data to the application which can be attached
to the packet while enqueuing.
> Kontantin has a comment (should be merged in RC2)
* eventdev: The function ``rte_event_crypto_adapter_queue_pair_add`` will
accept configuration of type ``rte_event_crypto_adapter_queue_conf`` instead
of ``rte_event``, similar to ``rte_event_eth_rx_adapter_queue_add`` signature.
Event will be one of the configuration fields,
together with additional vector parameters.
> Patches ready. Comment required from Abhinandan
* eventdev: The function pointer declaration ``eventdev_stop_flush_t``
will be renamed to ``rte_eventdev_stop_flush_t`` in DPDK 22.11.
> Patch available and will be merged today
* eventdev: The element ``*u64s`` in the structure ``rte_event_vector``
is deprecated and will be replaced with ``u64s`` in DPDK 22.11.
> Patch available and will be merged today
* eventdev: The structure ``rte_event_vector`` will be modified to include
``elem_offset:12`` bits taken from ``rsvd:15``. The ``elem_offset`` defines
the offset into the vector array from which valid elements are present.
The difference between ``rte_event_vector::nb_elem`` and
``rte_event_vector::elem_offset`` gives the number of valid elements left
to process from the ``rte_event_vector::elem_offset``.
> Patch is merged. Should remove deprecation docs.
* metrics: The function ``rte_metrics_init`` will have a non-void return
in order to notify errors instead of calling ``rte_exit``.
> Patch submitted by Bruce
* raw/dpaa2_cmdif: The ``dpaa2_cmdif`` rawdev driver will be deprecated
in DPDK 22.11, as it is no longer in use, no active user known.
> Drop from deprecations.
[-- Attachment #2: Type: text/html, Size: 35323 bytes --]
^ permalink raw reply [relevance 6%]
* DPDK Release Status Meeting 2022-10-13
@ 2022-10-13 15:48 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-10-13 15:48 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 4199 bytes --]
Release status meeting minutes 2022-10-13
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 7 October 2022 - Was 3 October
* RC2: 23 October 2022
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* RC1 out
* Hairpin feature is merged
* Ethdev - Dumping Rx/Tx descriptors - merged
* Ethdev - Recovering events sent by driver - has comments that need to be addressed
* New drivers in this release:
* Microsoft Azure Network Adapter (MANA) PMD
* Merged in RC1
* However, there is an issue due to dependencies not being available
* Compilation will be disabled until dependencies become available
* Google Virtual Ethernet (GVE)
* Some discussion on MIT licenced code
* Went to governing board review
* idpf (Infrastructure Data Path Function) PMD
* Under review
* net/qdma PMD
* Awaiting reply from submitter
* Memif driver needs reviews from maintainer
* next-net-intel
* Some fixes merged
* next-net-mlx
* Some big changes to come on hardware steering for RC2
* next-net-mrvl
* 13 patches to merge. 2 merged.
* next-eventdev
* 4 patches from Intel merged
* 4 patches from E/// under review
* next-virtio
* Actively reviewing patches, ~24 in queue
* next-crypto
* QAT crypto driver patches need ack
* Patches around BBDev
* 1 patchset merged and 1 pending
* New Huawei UADK driver
* main
* RC1 out. Features merged:
* LoongArch merged
* Windows Thread API merged
* Buffer split merge
* Member library with NitroSketch
* Power library
* See announce for full list: http://mails.dpdk.org/archives/announce/2022-October/000428.html
* Telemetry series under discussion
* Memarea postponed
* Needs other reviews
* Mempool changes need tests and reviews prior to merge in RC2
* Regression on unit tests due to mempool changes
* Meson version upgraded to 0.53.2.
* KNI deprecation warnings added for compile and runtime
* We should also upgrade the minimum required kernel version for 22.11
* Suggestions welcome
Proposed Schedule for 2023
23.03
* Proposal deadline (RFC/v1 patches): 30 December 2022
* API freeze (-rc1): 10 February 2023
* PMD features freeze (-rc2): 24 February 2023
* Built-in applications features freeze (-rc3): 3 March 2023
* Release: 10 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 7 April 2023
* API freeze (-rc1): 26 May 2023
* PMD features freeze (-rc2): 16 June 2023
* Built-in applications features freeze (-rc3): 23 June 2023
* Release: 14 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 11 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Built-in applications features freeze (-rc3): 27 October 2023
* Release: 17 November 2023
Other
-----
* TBA
LTS
---
LTSes released on August 29th.
* 21.11.2
* 20.11.6
* 19.11.13
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialed for 19.11 to the 20.11 LTS cycle.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC. on https://meet.jit.si/DPDK
If you wish to attend just send an email to "John McNamara john.mcnamara@intel.com" for the invite.
Drafts/Notes
-----
[-- Attachment #2: Type: text/html, Size: 20218 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-10-20
@ 2022-10-21 9:31 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-10-21 9:31 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 4266 bytes --]
Release status meeting minutes 2022-10-20
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM [No]
* Canonical [No]
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 7 October 2022
* RC2: 28 October 2022 - moved from 24 October
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* NFP several patches in backlog
* Indirect Aging patches under review
* Ethdev - Recovering events sent by driver - merged
* New drivers in this release:
* Microsoft Azure Network Adapter (MANA) PMD
* Merged in RC1
* However, there is an issue due to dependencies not being available
* Compilation will be disabled until dependencies become available
* Patch sent
* Google Virtual Ethernet (GVE)
* Some discussion on MIT licenced code
* Went to governing board review
* idpf (Infrastructure Data Path Function) PMD
* Under review
* New version to be sent today to address review comments
* net/qdma PMD
* Awaiting reply from submitter
* Most likely next release
* Memif driver needs reviews from maintainer
* next-net-intel
* 15-20 patches waiting for merge
* Mostly bug fixes
* next-net-mlx
* Big patchset for hardware steering targeting RC2
* next-net-mrvl
* PR sent for RC2
* next-eventdev
* Awaiting 1 patch from Intel
* After that PR sent for RC2
* next-virtio
* Most patches review
* Awaiting new version of async vhost
* next-crypto
* Big series on BBDev
* QAT crypto driver patches need ack
* New Huawei UADK driver
* New version under test
* main
* RC2 moved to Friday 28 October
* Looking at fixes
* ASAN fixes
* Trace framework
* Memarea postponed
* Needs other reviews
* Mempool changes need tests and reviews prior to merge in RC2
* Should go into RC2
* DTS first series to be merged
* Meson version upgraded to 0.53.2.
* KNI deprecation warnings added for compile and runtime
* We should also upgrade the minimum required kernel version for 22.11
* Suggestions welcome
* Probably the earliest LTS kernel: 4.14
* Looking for RC1 test reports from different vendors
Proposed Schedule for 2023
23.03
* Proposal deadline (RFC/v1 patches): 30 December 2022
* API freeze (-rc1): 10 February 2023
* PMD features freeze (-rc2): 24 February 2023
* Builtin applications features freeze (-rc3): 3 March 2023
* Release: 10 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 7 April 2023
* API freeze (-rc1): 26 May 2023
* PMD features freeze (-rc2): 16 June 2023
* Builtin applications features freeze (-rc3): 23 June 2023
* Release: 14 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 11 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 17 November 2023
Other
-----
* TBA
LTS
---
LTSes released on August 29th.
Next releases will be:
* 21.11.3
* 20.11.7
* 19.11.14
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialled for 19.11 to the 20.11 LTS cycle.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 20448 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-10-27
@ 2022-10-27 18:55 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-10-27 18:55 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3633 bytes --]
Release status meeting minutes 2022-10-27
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 7 October 2022
* RC2: 28 October 2022 - moved from 24 October
* RC3: 31 October 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* NFP several patches merged
* Indirect Aging patches under review
* New version sent
* New drivers in this release:
* Microsoft Azure Network Adapter (MANA) PMD
* Compilation will be disabled until dependencies become available
* Google Virtual Ethernet (GVE)
* Merged
* idpf (Infrastructure Data Path Function) PMD
* Under review
* New updates sent
* net/qdma PMD
* Awaiting reply from submitter
* Most likely next release
* Memif driver needs reviews from maintainer
* next-net-intel
* ~20 patches, mainly bug fixes, waiting for merge
* next-net-mlx
* PR sent for RC2
* next-eventdev
* PR merged for RC2
* next-virtio
* PR ready for RC2
* next-crypto
* 60-70 patches merged and ready for pull
* New Huawei UADK driver ready for merge
* Will be ready for pull on Friday 28 October
* main
* RC2 on Friday 28 October
* Mempool changes merged
* Meson version upgraded to 0.53.2.
* KNI deprecation warnings added for compile and runtime
* We should also upgrade the minimum required kernel version for 22.11
* Suggestions welcome
* Probably the earliest LTS kernel: 4.14
* Looking for RC1 test reports from different vendors
Proposed Schedule for 2023
23.03
* Proposal deadline (RFC/v1 patches): 30 December 2022
* API freeze (-rc1): 10 February 2023
* PMD features freeze (-rc2): 24 February 2023
* Built-in applications features freeze (-rc3): 3 March 2023
* Release: 10 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 7 April 2023
* API freeze (-rc1): 26 May 2023
* PMD features freeze (-rc2): 16 June 2023
* Built-in applications features freeze (-rc3): 23 June 2023
* Release: 14 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 11 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Built-in applications features freeze (-rc3): 27 October 2023
* Release: 17 November 2023
Other
-----
* TBA
LTS
---
LTSes released on August 29th.
Next releases will be:
* 21.11.3
* 20.11.7
* 19.11.14
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialled for 19.11 to the 20.11 LTS cycle.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 18273 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-11-03
@ 2022-11-03 20:25 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-11-03 20:25 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3527 bytes --]
Release status meeting minutes 2022-11-03
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM [No]
* Canonical [No]
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 7 October 2022
* RC2: 28 October 2022
* RC3: 10 November 2022
* Release: XX November 2022 - To be determined.
Subtrees
--------
* next-net
* Mainly fixes from now on.
* Rte_flow clean-up moved to next release
* New drivers in this release:
* Microsoft Azure Network Adapter (MANA) PMD
* Compilation is disabled until dependencies become available
* Google Virtual Ethernet (GVE)
* Merged
* idpf (Infrastructure Data Path Function) PMD
* Merged
* net/qdma PMD
* Most likely next release
* next-net-intel
* Merged in RC2. Bug fixes only for RC3.
* next-net-mlx
* Merged in RC2. Bug fixes only for RC3.
* next-net-mrvl
* Merged in RC2. Bug fixes only for RC3.
* next-eventdev
* Merged in RC2. Bug fixes only for RC3.
* next-virtio
* Merged in RC2. Bug fixes only for RC3.
* next-crypto
* Some fixes applied and some more to apply.
* main
* RC2 released on November 1.
* RC3 will be on November 10.
* There seems to have been a Coverity server update leading to
more new issues than usual. Could maintainers please apply any
Coverity fixes for RC3, subject to the usual quality checks.
Proposed Schedule for 2023
23.03
* Proposal deadline (RFC/v1 patches): 30 December 2022
* API freeze (-rc1): 10 February 2023
* PMD features freeze (-rc2): 24 February 2023
* Builtin applications features freeze (-rc3): 3 March 2023
* Release: 10 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 7 April 2023
* API freeze (-rc1): 26 May 2023
* PMD features freeze (-rc2): 16 June 2023
* Builtin applications features freeze (-rc3): 23 June 2023
* Release: 14 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 11 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 17 November 2023
Other
-----
* TBA
LTS
---
Next releases will be:
* 21.11.3
* Backport patches have been sent
* Some in progress
* 20.11.7
* Backport patches have been sent
* Some in progress
* 19.11.14
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialled for 19.11 to the 20.11 LTS cycle.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
Drafts/Notes
-----
[-- Attachment #2: Type: text/html, Size: 18020 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-11-010
@ 2022-11-11 11:21 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-11-11 11:21 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2663 bytes --]
Release status meeting minutes 2022-11-10
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM [No]
* Canonical [No]
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 7 October 2022
* RC2: 28 October 2022
* RC3: 14 November 2022
* RC4: 18 November 2022
* Release: 23 November 2022
Subtrees
--------
* next-net
* Mainly fixes from now on.
* Still a lot of patches and waiting on reviews
* Some outstanding for testpmd, memif and request from Intel to help review.
* next-net-intel
* Needs additional time for RC3 as there are still have P2 bug fixes to be reviewed.
* There are alos bug fixes on dpdk-next-net-intel tree waiting for merge.
* next-net-mlx
* Closing on patches. Bug fixes only for RC3.
* next-net-mrvl
* No new patches.
* next-eventdev
* Pull request sent to Thomas.
* next-virtio
* Pull request sent to Thomas.
* next-crypto
* 20 fixes applied with some more to apply.
* Will be ready later today/tomorrow for Pull Request
* main
* RC2 released on November 1.
* Mempool stats - no response from Mailing List as to whether it needs to be in RC3 or not.
* Ok to merge in this release.
* Will need additional testing.
* Request to Intel team to test.
* DMA perf app - still has RFC tags.
* need confirmation in Intel [RFC v5] app/dma-perf: introduce dma-perf application
* OK for 22.03.
* RC3/RC4 and Release dates have changed. See above.
LTS
---
Next releases will be:
* 21.11.3
* Backport patches have been sent
* Some in progress
* 20.11.7
* Backport patches have been sent
* Some in progress
* 19.11.14
* Backport patches have been sent
* Some in progress
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14046 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-11-17
@ 2022-11-18 19:42 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-11-18 19:42 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]
Release status meeting minutes 2022-11-17
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 7 October 2022
* RC2: 28 October 2022
* RC3: 14 November 2022
* RC4: 21 November 2022
* Release: 23 November 2022
Subtrees
--------
* next-net
* RC3 is out.
* Only fixes from now on.
* next-net-intel
* Some iavf fixes required in RC4.
* next-net-mlx
* Majority of code in RC3.
* Looking at fixes and docs.
* next-net-mrvl
* No update. Most code merged.
* next-eventdev
* No update. Most code merged.
* next-virtio
* Majority of code in RC3.
* Looking at fixes and docs.
* next-crypto
* Doc patches.
* From next release next-crypto will be split with next-bbdev
* main
* RC3 released.
* RC4 on Monday 21 November.
LTS
---
Next releases will be:
* 21.11.3
* In progress.
* Backport patches have been sent
* Loooking at RC3 fixes
* 20.11.7
* Backport patches have been sent
* Some in progress
* 19.11.14
* Backport patches have been sent
* Some in progress
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 12913 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2022-11-24
@ 2022-11-24 15:42 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-11-24 15:42 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3027 bytes --]
Release status meeting minutes 2022-11-24
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Canonical [No]
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 22.11:
* V1 deadline: 24 August 2022
* RC1: 7 October 2022
* RC2: 28 October 2022
* RC3: 10 November 2022
* Release: 16 November 2022
Subtrees
--------
* next-net
* Only doc fixes after RC4.
* next-net-intel
* Only doc fixes after RC4.
* next-net-mlx
* Only doc fixes after RC4.
* next-net-mvl
* Only doc fixes after RC4.
* next-eventdev
* Only doc fixes after RC4.
* next-virtio
* Only doc fixes after RC4.
* next-crypto
* Only doc fixes after RC4.
* main
* RC4 released.
* New next-bbdev tree created.
* Please note the proposed schedule for 2023 below
and respond if you have any concerns with the
dates.
Proposed Schedule for 2023
23.03
* Proposal deadline (RFC/v1 patches): 30 December 2022
* API freeze (-rc1): 10 February 2023
* PMD features freeze (-rc2): 24 February 2023
* Builtin applications features freeze (-rc3): 3 March 2023
* Release: 10 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 7 April 2023
* API freeze (-rc1): 26 May 2023
* PMD features freeze (-rc2): 16 June 2023
* Builtin applications features freeze (-rc3): 23 June 2023
* Release: 14 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 11 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 17 November 2023
LTS
---
Next releases will be:
* 21.11.3
* Backport patches have been sent.
* Merging of 22.11 patches in progress.
* 20.11.7
* Backport patches have been sent.
* Merging of 22.11 patches in progress.
* 19.11.14
* Backport patches have been sent.
* Merging of 22.11 patches in progress.
Discussion needed on whether we will continue the 3 year LTS cycle that
was trialled for 19.11 to the 20.11 LTS cycle.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16095 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-12-01
@ 2022-12-01 19:01 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-12-01 19:01 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2871 bytes --]
Release status meeting minutes 2022-12-01
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM [No]
* Canonical [No]
* Debian/Microsoft
* Intel
* Marvell [No]
* Nvidia
* Red Hat
* Xilinx/AMD
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 8 February 2023
* RC2: 1 March 2023
* RC3: 8 March 2023
* Release: 20 March 2023
Subtrees
--------
* next-net
* No update.
* next-net-intel
* No update.
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-virtio
* No update.
* next-crypto
* No update.
* main
* 22.11 released.
* We are looking for a new shared maintainer for next-net
* There is an ABI breakage issue
* Will be fixed in release 22.11.1 on stable.
* Call for roadmaps for 23.03
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.03
* Proposal deadline (RFC/v1 patches): 25 December 2022
* API freeze (-rc1): 8 February 2023
* PMD features freeze (-rc2): 1 March 2023
* Builtin applications features freeze (-rc3): 8 March 2023
* Release: 20 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Next releases will be:
* 21.11.3
* Backport patches have been sent.
* Merging of 22.11 patches in progress.
* 20.11.7
* Backport patches have been sent.
* Merging of 22.11 patches in progress.
* 19.11.14
* Backport patches have been sent.
* Merging of 22.11 patches in progress.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15674 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2022-12-08
@ 2022-12-08 13:51 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2022-12-08 13:51 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3095 bytes --]
Release status meeting minutes 2022-12-08
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* AMD
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 8 February 2023
* RC2: 1 March 2023
* RC3: 8 March 2023
* Release: 20 March 2023
Subtrees
--------
* next-net
* No update.
* next-net-intel
*
* Issue with net/iavf: fix slow memory allocation
* Needs to be fixed for LTS releases
* https://patchwork.dpdk.org/project/dpdk/patch/20221117065726.277672-1-kaisenx.you@intel.com/
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* MLDev targeted for this release.
* next-eventdev
* Nothing major yet.
* next-baseband
* New subtree starting from this release.
* next-virtio
* Virtio-user multi-queue patch.
* next-crypto
* No update.
* main
* 22.11.1 released with fix for symbols.
* Work on thread API ongoing in this release
* Call for roadmaps for 23.03
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.03
* Proposal deadline (RFC/v1 patches): 25 December 2022
* API freeze (-rc1): 8 February 2023
* PMD features freeze (-rc2): 1 March 2023
* Builtin applications features freeze (-rc3): 8 March 2023
* Release: 20 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
Other
-----
* TBA
LTS
---
Next releases will be:
* 21.11.3
* RC sent and under test
* In progress
* 20.11.7
* Awaiting test results
* On track
* 19.11.14
* Awaiting test results
* On track
LTSes will need the fix for 2net/iavf: fix slow memory allocation" mentioned above.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 17218 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-01-19
@ 2023-01-24 10:33 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-01-24 10:33 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3381 bytes --]
Release status meeting minutes 2023-01-19
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 8 February 2023
* RC2: 1 March 2023
* RC3: 8 March 2023
* Release: 20 March 2023
Subtrees
--------
* next-net
* Patches being merged but slowly
* rte_flow has a lot of changes in this release and needs support
* Some reviews ongoing but we are missing reviewer support on this tree.
* next-net-intel
* No update.
* next-net-mlx
* No update.
* next-net-mvl
* Nearly all patches merged. Ready for pull.
* next-eventdev
* Nearly all patches merged. Waiting for some review comments
3 sets of patches from Intel.
* Some CNXK updates
* next-baseband
* New tree from this release.
* Some series merged and some under review.
* next-virtio
* Not many series under review.
* Vhost async and VDPA patches need review.
* next-crypto
* Some patches merged this week.
* Build patches for QAT
* PDCP (Packet Data Convergence Protocol) new library targeted for this release
* Patch for CCP driver from last release
* main
* Thread API from Tyler under review
* ABI check merged
* ML Dev patches need review
* CNI (Container Network Interface) for the AF_XDP driver.
* Will update patch to include explanation/docs.
* Request for Roadmaps
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.03
* Proposal deadline (RFC/v1 patches): 25 December 2022
* API freeze (-rc1): 8 February 2023
* PMD features freeze (-rc2): 1 March 2023
* Builtin applications features freeze (-rc3): 8 March 2023
* Release: 20 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
Other
-----
* TBA
LTS
---
Next releases will be:
* 22.11.1
* 21.11.4
* 20.11.8
* 19.11.15?
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 18068 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-01-26
@ 2023-01-26 19:02 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-01-26 19:02 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3007 bytes --]
Release status meeting minutes 2023-01-26
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 8 February 2023
* RC2: 1 March 2023
* RC3: 8 March 2023
* Release: 20 March 2023
Subtrees
--------
* next-net
* Needs more reviews/support.
* Focus is on ethdev reviews.
* rte_flow has a lot of cleanup changes in this release and needs reviews
* Some reviews ongoing but we are missing reviewer support on this tree.
* next-net-intel
* No update.
* next-net-mlx
* Some patches integrated and waiting to be pulled.
* More in the backlog.
* next-net-mvl
* No update
* next-eventdev
* No update
* next-baseband
* No update
* next-virtio
* No update
* next-crypto
* No update
* main
* Thread API from Tyler under review
* Waiting for ack on deprecation
* Telemetry patches from Robin under review.
* Two series on annotations.
* Spurious failures in service-cores tests
* testpmd fixes/additions need closer reviews
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.03
* Proposal deadline (RFC/v1 patches): 25 December 2022
* API freeze (-rc1): 8 February 2023
* PMD features freeze (-rc2): 1 March 2023
* Builtin applications features freeze (-rc3): 8 March 2023
* Release: 20 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
Other
-----
* TBA
LTS
---
Next releases will be:
* 22.11.1
* 21.11.4
* 20.11.8
* 19.11.15?
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16884 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-02-02
@ 2023-02-03 12:35 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-02-03 12:35 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3564 bytes --]
Release status meeting minutes 2023-02-02
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 8 February 2023
* RC2: 1 March 2023
* RC3: 8 March 2023
* Release: 20 March 2023
Subtrees
--------
* next-net
* The next-net tree needs more reviews/support.
* 30+ patches on rte_flow
* 25+ ethdev patches
* Both sets need reviews and fixes
* CPFL has dependencies - needs to be clarified
* Ethdev patch for live migration
- Currently the design may only work with MLX
so it may get moved to a private API
* Patch series for trace points in ethdev
* next-net-intel
* 20+ patches ready for merge.
* next-net-mlx
* Some patches integrated and waiting to be pulled.
* More in the backlog.
* next-net-mvl
* Patches merge and awaiting pull
* next-eventdev
* Patches merge and awaiting pull
* next-baseband
* Two series
- One reviewed and one needs revision
* next-virtio
* Review on big Control Queue support series
* Async vhost packed ring optimization
* next-crypto
* Some pat
* 2 major series
- Compressdev - need review
- PDCP (Packet Data Convergence Protocol)
* main
* Thread API from Tyler under review
* First one merged
* Telemetry patches from Robin under review.
* Two series on annotations.
- Preferred syntax under discussion
* Spurious failures in service-cores tests
* testpmd fixes/additions need closer reviews
* igbuio build issue - There are multiple reports and fix patches. One should be merged.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.03
* Proposal deadline (RFC/v1 patches): 25 December 2022
* API freeze (-rc1): 8 February 2023
* PMD features freeze (-rc2): 1 March 2023
* Builtin applications features freeze (-rc3): 8 March 2023
* Release: 20 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
Other
-----
* TBA
LTS
---
Next releases will be:
* 22.11.1
* 21.11.4
* 20.11.8
* 19.11.15?
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 18578 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-02-09
@ 2023-02-10 16:42 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-02-10 16:42 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3772 bytes --]
Release status meeting minutes 2023-02-09
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 8 February 2023 - Moving to 16-17 February
* RC2: 1 March 2023
* RC3: 8 March 2023
* Release: 20 March 2023
Subtrees
--------
* next-net
* Merged some patches to next-net and rebased on latest main.
* From the remaining patches (~100 patches remaining if you drop very old ones):
- 8 flow API patchset, 5 of them fully acked by Ori
- 4 ethdev set
- One of them sent today
- 2 of them direct-rearm and MAC occupy two entries, they are from previous versions. Some concerns on these.
- Multiple testpmd and driver patches, will look at them after library ones
- Have asked for changes for af_xdp CNI one, it is missing some documentation and needs some minor code changes
- It will be great if we can have more testpmd reviews
- New PMD probably won't go into -rc1
- Needs update from next-intel maintainer
* next-net-intel
* No update.
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* Patches merged and awaiting pull
* next-baseband
* Two series: One reviewed and one needs revision
* next-virtio
* Pull request sent and merged.
* Quite a few patches ready for virtio.
* next-crypto
* No update.
* main
* 3 patches to merge
* Windows Thread API
* Robin Telemetry patches
- EAL parts are ready
- Some more need on testpmd
* Not enough consensus/discussion on lock annotations
* The following needs review:
* enhance NUMA affinity heuristic
* https://patchwork.dpdk.org/project/dpdk/patch/20230201122048.1283392-1-kaisenx.you@intel.com/
* Proposal to move RC1 to February 16-17
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.03
* Proposal deadline (RFC/v1 patches): 25 December 2022
* API freeze (-rc1): 8 February 2023
* PMD features freeze (-rc2): 1 March 2023
* Builtin applications features freeze (-rc3): 8 March 2023
* Release: 20 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
Other
-----
* TBA
LTS
---
Next releases will be:
* 22.11.1
* 21.11.4
* 20.11.8
* 19.11.15?
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 18874 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-02-23
@ 2023-02-27 8:41 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-02-27 8:41 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3430 bytes --]
Release status meeting minutes 2023-02-23
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 20 February 2023
* RC2: 8 March 2023
* RC3: 15 March 2023
* Release: 24 March 2023
Subtrees
--------
* next-net
* Majority of rte_flow and ethdev patches merged.
* Some additional PMD and driver patches for RC2.
* next-net-intel
* About 60 patches has been merged.
* A few fixes still under review and targeted for RC2
* next-net-mlx
* Patches merged to RC1
* ~30 patches for RC2.
* next-net-mvl
* Mainly merged. Just a few patches remaining.
* next-eventdev
* Merged.
* next-baseband
* PR prepared.
* 1 new series that needs revision from Intel.
* next-virtio
* No patches currently ready for RC2.
* next-crypto
* Patchset on FIPs validation needs review.
* Some old QAT patches from Arek that need ack.
* Compressdev patch requires reviews
* PDCP library may still be in RC2 but may move to next release.
* main
* Patches for MLdev to be merged.
* Telemetry patches - not all merged (some need discussion)
* Patch for "vfio: do not coalesce DMA mapping" needs review/discussion:
* https://patches.dpdk.org/project/dpdk/patch/20230104051936.2456411-1-nipun.gupta@amd.com/
* Proposed RC2 date: 8 March
* Proposed RC3 date: 15 March
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.03
* Proposal deadline (RFC/v1 patches): 25 December 2022
* API freeze (-rc1): 20 February 2023
* PMD features freeze (-rc2): 81 March 2023
* Builtin applications features freeze (-rc3): 15 March 2023
* Release: 24 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
Other
-----
* TBA
LTS
---
Next releases will be:
Backports in progress and pull requests have been sent.
* 22.11.1
* 21.11.4
* 20.11.8
* 19.11.15?
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 17777 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-03-02
@ 2023-03-03 16:08 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-03-03 16:08 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3241 bytes --]
Release status meeting minutes 2023-03-02
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 20 February 2023
* RC2: 8 March 2023
* RC3: 15 March 2023
* Release: 24 March 2023
Subtrees
--------
* next-net
* New versions of some patchsets under review.
* Fix for crash from trace in ethdev
* https://bugs.dpdk.org/show_bug.cgi?id=1162
* https://patches.dpdk.org/project/dpdk/patch/20230223123029.2117781-2-adwivedi@marvell.com/
* Some ASAN warnings under review
* New version of CPFL - looks okay - minor issues
* Documentation for dynamic parameters required
* Abstraction of AXV-512 needed
* next-net-intel
* 5 patches waiting for merge
* next-net-mlx
* Some patches merged and some more in the backlog for RC2
* Will make a PR Friday
* next-net-mvl
* 2-3 patches ongoing
* next-eventdev
* Merged.
* next-baseband
* 1 new series that needs revision from Intel.
* next-virtio
* Some patches to review.
* next-crypto
* FIPS patches merged
* PMD patches merged
* Tree is ready for RC2
* Compressdev merged
* main
* Merging some fixes
* Proposed RC2 date: 8 March
* Proposed RC3 date: 15 March
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.03
* Proposal deadline (RFC/v1 patches): 25 December 2022
* API freeze (-rc1): 20 February 2023
* PMD features freeze (-rc2): 81 March 2023
* Builtin applications features freeze (-rc3): 15 March 2023
* Release: 24 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Next releases will be:
Backports in progress and pull requests have been sent.
* 22.11.1
* 21.11.4
* 20.11.8
* 19.11.15
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16728 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-03-09
@ 2023-03-09 17:32 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-03-09 17:32 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2882 bytes --]
Release status meeting minutes 2023-03-09
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 20 February 2023
* RC2: 9-10 March 2023
* RC3: 15 March 2023
* Release: 24 March 2023
Subtrees
--------
* next-net
* Merged for RC2
* next-net-intel
* 9 fix patches waiting for merge
* next-net-mlx
* No update
* Patch to compile MLX5 on Windows
* next-net-mvl
* All merged for RC2.
* next-eventdev
* All merged for RC2.
* next-baseband
* All merged for RC2.
* next-virtio
* All merged for RC2.
* next-crypto
* All merged for RC2.
* main
* Mainly ready for RC2.
* Merging some fixes
* ASAN reports under review.
* See: https://bugs.dpdk.org/show_bug.cgi?id=823
* MLdev to be merged
* RC2 date: 9-10 March
* Proposed RC3 date: 15 March
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.03
* Proposal deadline (RFC/v1 patches): 25 December 2022
* API freeze (-rc1): 20 February 2023
* PMD features freeze (-rc2): 9-10 March 2023
* Builtin applications features freeze (-rc3): 15 March 2023
* Release: 24 March 2023
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
Other
-----
* TBA
LTS
---
Next releases will be:
Backports in progress and pull requests have been sent.
* 22.11.1
* 21.11.4
* 20.11.8
* 19.11.15
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16381 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-03-23
@ 2023-03-23 11:28 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-03-23 11:28 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2913 bytes --]
Release status meeting minutes 2023-03-23
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.03:
* V1: 25 December 2022
* RC1: 20 February 2023
* RC2: 12 March 2023
* RC3: 19 March 2023
* RC4: 27 March 2023
* Release: 29 March 2023
Subtrees
--------
* next-net
* Mainly closed after RC3
* Driver documentation to be updated
* next-net-intel
* No update
* next-net-mlx
* Some patches pending:
* GCC12 fix
* next-net-mvl
* No more patches after RC3.
* next-eventdev
* No more patches after RC3.
* next-baseband
* No more patches after RC3.
* next-virtio
* Some fix patches. Can mainly wait to the next release.
https://bugs.dpdk.org/show_bug.cgi?id=1196
* next-crypto
* No update
* main
* Looking at deprecation notices
* Please update Release Notes.
* In particular please update the "Tested Platforms" section of the Release Notes:
https://doc.dpdk.org/guides/rel_notes/release_23_03.html#tested-platforms
* RC4 planned for Monday 27 March
* Release planned for Wednesday 29 March
* 22.07 V1 deadline moved out 1 week to 15 April
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 15 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Next LTS releases will be:
* 22.11.1
* 21.11.4
* Backports up to date with RC3
* 20.11.8
* Backports up to date with RC3
* 19.11.15
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15584 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-04-06
@ 2023-04-07 10:43 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-04-07 10:43 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2872 bytes --]
Release status meeting minutes 2023-04-06
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 31 May 2023
* RC2: 21 June 2023
* RC3: 28 June 2023
* Release: 12 July 2023
Subtrees
--------
* next-net
* Deferred patches moved to new.
* next-net-intel
* No update
* next-net-mlx
* No update
* next-net-mvl
* Some work ongoing for this release.
* next-eventdev
* A few minor feature
* next-baseband
* No major features so far.
* next-virtio
* New series on guest notifications in slow path
* VDU - Vhost VDPA in userspace. https://lwn.net/Articles/841054/
* next-crypto
* Updates to PDCP
* Patches for asymmetric crypto
* Rte_security patch for out of place inline IPsec
* main
* A lot of patches to improve the Windows port
* New version of lock annotation support
* Patches from ARM for PMU
* Memarea feature
* CDX bus patches from AMD
* Call for updates to the external Roadmap:
https://core.dpdk.org/roadmap/
* Retrospective:
* Bonding PMD: there is a gap in maintenance.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Next LTS releases will be:
* 22.11.1
* 21.11.4
* On track for RC1
* 20.11.8
* RC1 sent and first test report received
* 19.11.15
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15551 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-04-06
@ 2023-04-24 19:23 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-04-24 19:23 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3038 bytes --]
Release status meeting minutes 2023-04-06
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell NO
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 31 May 2023
* RC2: 21 June 2023
* RC3: 28 June 2023
* Release: 12 July 2023
Subtrees
--------
* next-net
* No new PMDs in this release (so far).
* next-net-intel
* No update
* next-net-mlx
* No update
* next-net-mvl
* No update
* next-eventdev
* No update
* next-baseband
* No major features so far.
* next-virtio
* New series on guest notifications in slow path
* VDUSE - Vhost VDPA in userspace. https://lwn.net/Articles/841054/
* next-crypto
* Patches to add new algorithms
* Updates to PDCP
* Patches for asymmetric crypto
* rte_security patch for out of place inline IPsec
* main
* A lot of patches to improve the Windows port
* New version of lock annotation support
* Patches from ARM for PMU
* Postponed from last release
* For tracing
* Power Management feature from AMD
* Memarea feature
* CDX bus patches from AMD
* Virtual PCI like bus
* Call for updates to the external Roadmap:
https://core.dpdk.org/roadmap/
* Retrospective:
* Bonding PMD: there is a gap in maintenance.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Next LTS releases will be:
* 22.11.1
* 21.11.4
* RC1 testing underway
* 20.11.8
* RC1 sent and first test report received
* 19.11.15
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04 contains 21.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16785 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-04-27
@ 2023-05-02 13:26 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-05-02 13:26 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3341 bytes --]
Release status meeting minutes 2023-04-27
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 31 May 2023
* RC2: 21 June 2023
* RC3: 28 June 2023
* Release: 12 July 2023
Subtrees
--------
* next-net
* Under review.
* next-net-intel
* Starting to apply patches, about 20 patches are waiting for merge
* next-net-mlx
* No update
* next-net-mvl
* No update
* next-eventdev
* No update
* next-baseband
* No major features so far.
* next-virtio
* New series on guest notifications in slow path
* VDUSE - Vhost VDPA in userspace. https://lwn.net/Articles/841054/
* next-crypto
* 60-70 patches in backlog
* Some patches to be merged this week.
* Patches to add new algorithms
* Updates to PDCP
* Patches for asymmetric crypto
* Rte_security patch for out of place inline IPsec
* main
* Starting to merge patches to improve the Windows port
* New version of lock annotation support - merged
* Patches from ARM for PMU
* Postponed from last release
* For tracing
* Awaiting feedback on comments
* Power Management feature from AMD
* Memarea feature
* CDX bus patches from AMD
* Virtual PCI like bus
* New checkpatch checks for atomic functions
* Call for updates to the external Roadmap:
https://core.dpdk.org/roadmap/
* Retrospective:
* Bonding PMD: there is a gap in maintenance.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Next LTS releases will be:
* 22.11.1
* RC1 sent - Scheduled for May 5
* 21.11.4
* Got test feedback from Nvidia, Red Hat and Intel
* 20.11.8
* RC1 sent and first test report received
* 19.11.15
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 17459 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-05-04
@ 2023-05-04 10:24 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-05-04 10:24 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3522 bytes --]
Release status meeting minutes 2023-05-04
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 31 May 2023
* RC2: 21 June 2023
* RC3: 28 June 2023
* Release: 12 July 2023
Subtrees
--------
* next-net
* Under review.
* ~120 patches in backlog.
* GVE license update
* next-net-intel
* Starting to apply patches, about 20 patches are waiting for merge.
* next-net-mlx
* No update
* next-net-mvl
* Some patches merged.
* ~30 patches remaining.
* next-eventdev
* Some patches merged.
* AMD patches under review
* next-baseband
* No major features so far.
* next-virtio
* Intel series for port mirroring
* Some concerns on code duplication and API complexity
* Report of performance degradation in vhost driver
* New series on guest notifications in slow path
* VDUSE - Vhost VDPA in userspace. https://lwn.net/Articles/841054/
* Under review
* next-crypto
* 60-70 patches in backlog
* Patches to add new algorithms
* Reviewing PDCP patches
* Reviews and merges ongoing
* main
* Starting to merge patches to improve the Windows port
* Reviewing ethdev patches
* Patches from ARM for PMU
* Postponed from last release
* For tracing
* Awaiting feedback on comments
* Power Management feature from AMD
* Memarea feature
* CDX bus patches from AMD
* Virtual PCI like bus
* New checkpatch checks for atomic functions
* Issues with Fedora 38 and GCC 13
* Issue with Coverity automated analysis
* Call for updates to the external Roadmap:
https://core.dpdk.org/roadmap/
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Next LTS releases will be:
* 22.11.1
* RC1 sent - Scheduled for May 5
* 21.11.4
* Got test feedback from Nvidia, Red Hat and Intel
* 20.11.8
* RC1 sent and first test report received
* 19.11.15
* CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 17833 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-05-11
@ 2023-05-11 13:57 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-05-11 13:57 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3671 bytes --]
Release status meeting minutes 2023-05-11
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 31 May 2023
* RC2: 21 June 2023
* RC3: 28 June 2023
* Release: 12 July 2023
Subtrees
--------
* next-net
* Under review.
* ~120 patches in backlog.
* GVE license updated from MIT to FreeBSD
* next-net-intel
* Some patches are waiting for merge and some under review.
* Seeking community input on adapting DPDK to P4 Runtime backend:
http://mails.dpdk.org/archives/dev/2023-May/267719.html
* next-net-mlx
* No update
* next-net-mvl
* Some patches merged.
* ~30 patches remaining.
* next-eventdev
* Some patches merged.
* AMD patches under review
* next-baseband
* No major patches in this release.
* next-virtio
* Reviews ongoing
* Intel series for port mirroring
* Some concerns on code duplication and API complexity
* Report of performance degradation in vhost driver
* New series on guest notifications in slow path
* VDUSE - Vhost VDPA in userspace. https://lwn.net/Articles/841054/
* Under review
* next-crypto
* 60-70 patches in backlog
* Patches to add new algorithms
* Reviewing PDCP patches
* Reviews and merges ongoing
* main
* Starting to merge patches to improve the Windows port
* Reviewing ethdev patches
* Patches from ARM for PMU
* Postponed from last release
* For tracing
* Awaiting feedback on comments
* Power Management feature from AMD
* Memarea feature
* CDX bus patches from AMD
* Virtual PCI like bus
* New checkpatch checks for atomic functions
* Issues with Fedora 38 and GCC 13
* Fixes merged
* Call for updates to the external Roadmap:
https://core.dpdk.org/roadmap/
* Static code analysis
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 31 May 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Next LTS releases will be:
* 22.11.1
* Released on May 7
* 21.11.4
* Some issues found in Intel testing - under investigation.
* 20.11.8
* Released on April 27
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 18228 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-06-01
@ 2023-06-01 15:42 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-06-01 15:42 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3909 bytes --]
Release status meeting minutes 2023-06-01
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 7 June 2023
* RC2: 21 June 2023
* RC3: 28 June 2023
* Release: 12 July 2023
Subtrees
--------
* next-net
* Focused on rte_dev. Reviews ongoing from Ori.
* Should be okay for RC1.
* Offload flag renaming.
* next-net-intel
* ~ 50 patches waiting for merge
* Seeking community input on adapting DPDK to P4 Runtime backend:
* http://mails.dpdk.org/archives/dev/2023-May/267719.html
* Will set up a community meeting to discuss the P4 table driven approach.
* The meeting is provisionally scheduled for June 7 at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
* Email me for an invite
* next-net-mlx
* Merging patches.
* Should be mainly ready for RC1.
* next-net-mvl
* PR ready to merged.
* next-eventdev
* PR ready to merged.
* next-baseband
* New series sent this week from Heman.
* Too large for this release, will target 23.11
http://patches.dpdk.org/project/dpdk/list/?series=28139
* next-virtio
* Patch from Eelco on offload ready to apply
* Sys call out of the data path
* Spin locks
* Intel series for port mirroring
* Some concerns on code duplication and API complexity
* New series on guest notifications in slow path
* VDUSE - Vhost VDPA in userspace. https://lwn.net/Articles/841054/
* New version sent. Needs to be rebased on top of Eelco's series.
* next-crypto
* Libpdcp merged.
* Asym crypto needs to be reviewed.
* Almost ready for PR merge.
* GCC 13 issues in drivers
* main
* Starting to merge patches to improve the Windows port
* Reviewing ethdev patches
* Patches from ARM for PMU
* Postponed from last release for tracing
* Awaiting feedback on comments - will be deferred if no replies.
* Power Management feature from AMD
* CDX bus patches from AMD
* Virtual PCI like bus
* Issues with Fedora 38 and GCC 13
* Fixes merged
* Issues with Intel lab CI reporting false positives
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 7 June 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
* 22.11.1
* Released on May 7
* 21.11.4
* Released May 17
* 20.11.8
* Released on April 27
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 18632 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-06-08
@ 2023-06-08 18:40 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-06-08 18:40 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3169 bytes --]
Release status meeting minutes 2023-06-08
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 7 June 2023 - Trending to 9 June.
* RC2: 21 June 2023
* RC3: 28 June 2023
* Release: 12 July 2023
Subtrees
--------
* next-net
* Focused on rte_flow and eth_dev.
* Mainly ready for RC1.
* PTP Time-sync looking for comments.
* We still have a lack of a bonding maintainer for reviews.
* next-net-intel
* Mainly ready for merge
* Some bug fixes under review.
* next-net-mlx
* Merging patches.
* Should be mainly ready for RC1.
* next-net-mvl
* PR merged.
* Some more patches in prep for RC2.
* next-eventdev
* PR merged.
* next-baseband
* Some discussion on API changes in BBDev.
* Tree clean otherwise. Ready for merge.
* next-virtio
* Eelco's series merged.
* VDUSE - Vhost VDPA in userspace. https://lwn.net/Articles/841054/
* Rebased on top of Eelco's series.
* next-crypto
* Mainly ready.
* Compilation issue with IPsecMB
* Should be ready for merge in next 1-2 days.
* main
* Working to merge patches to improve the Windows port
* Merged telemetry updates for memory allocator.
* Big features mainly merged.
* New version of graph bind/unbind required.
* Issues with Intel lab CI reporting false positives should be fixed.
* RC1 targeted for June 9
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 7 June 2023
* PMD features freeze (-rc2): 21 June 2023
* Builtin applications features freeze (-rc3): 28 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
* 22.11.1
* Released on May 7
* 21.11.4
* Released May 17
* 20.11.8
* Released on April 27
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v20.11 in Debian 11
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16021 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-06-15
@ 2023-06-15 17:59 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-06-15 17:59 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3005 bytes --]
Release status meeting minutes 2023-06-15
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 13 June 2023
* RC2: 23 June 2023 - Moved from 21
* RC3: 30 June 2023 - Moved from 28
* Release: 12 July 2023
Subtrees
--------
* next-net
* Looking at larger patches from SFC and Netronome.
* next-net-intel
* Mostly merged for RC1.
* next-net-mlx
* No update.
* next-net-mvl
* 20 patches merged and ready for RC2.
* next-eventdev
* 3 patches merged and ready for RC2.
* next-baseband
* Some discussion on API/ABI changes in BBDev.
* next-virtio
* Some patches, mostly fixes, under review.
* Majority of the larger features merged in RC1.
* next-crypto
* Comments on some of the patches for RC2: needs review
* MLX5 crypto driver.
* OpenSSL and QAT: from Kai
* Some compilations issue on IPsecMB blocking merge.
* main
* RC1 is out.
* Graph series has a new revision.
* Meson build script updates.
* Patch from Bruce on tracing/logging
* PCIe maintainership
* Overall we need more maintainers and/or more trees
* Trees for graph and pipeline
* Tree for core and other
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 7 June 2023
* PMD features freeze (-rc2): 23 June 2023
* Builtin applications features freeze (-rc3): 30 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backporting in progress.
Next LTS releases:
* 22.11.2
* 21.11.5
* 20.11.9
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16270 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-06-22
@ 2023-06-23 13:18 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-06-23 13:18 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2825 bytes --]
Release status meeting minutes 2023-06-22
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM [no]
* Debian/Microsoft [no]
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 13 June 2023
* RC2: 23 June 2023
* RC3: 30 June 2023
* Release: 12 July 2023
Subtrees
--------
* next-net
* Most patches ready for RC2
* next-net-intel
* No update.
* next-net-mlx
* Most patches ready for RC2.
* Some will go in RC3.
* next-net-mvl
* Ready for RC2. PR sent.
* next-eventdev
* Ready for RC2. PR sent.
* next-baseband
* No update.
* next-virtio
* No update.
* next-crypto
* Mainly ready for RC2.
* main
* Prepping for RC2
* Maintainers list needs to be refreshed. Can everyone please check
the current MAINTAINERS and make any changes.
* All maintainers should be registered in Bugzilla. This will
become mandatory via checkpatch.
* DPDK EU Summit, call for papers:
https://events.linuxfoundation.org/dpdk-summit/
https://events.linuxfoundation.org/dpdk-summit/program/cfp/
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.07
* Proposal deadline (RFC/v1 patches): 22 April 2023
* API freeze (-rc1): 7 June 2023
* PMD features freeze (-rc2): 23 June 2023
* Builtin applications features freeze (-rc3): 30 June 2023
* Release: 12 July 2023
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backporting in progress.
Next LTS releases:
* 22.11.2
* 21.11.5
* 20.11.9
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15725 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-06-29
@ 2023-06-29 11:01 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-06-29 11:01 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2965 bytes --]
Release status meeting minutes 2023-06-29
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed current dates for 23.07:
* V1: 22 April 2023
* RC1: 13 June 2023
* RC2: 27 June 2023 - Moved from 23 June
* RC3: 5 July 2023 - Moved from 30 June
* Release: 17 July 2023 - Moved from 12 July
Subtrees
--------
* next-net
* RC2 released. Waiting for test results and fixes.
* Issue with testpmd and port forwarding:
https://bugs.dpdk.org/show_bug.cgi?id=1259
* next-net-intel
* No update.
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-baseband
* No update.
* next-virtio
* No update.
* next-crypto
* No update.
* main
* RC2 released 2023-06-27
* Need to remove some code from the Marvell regex driver since it
is based on private APIs and can't be compiled.
* Maintainers list needs to be refreshed. Can everyone please check
the current MAINTAINERS and make any changes.
* All maintainers should be registered in Bugzilla. This will
become mandatory via checkpatch.
* DPDK EU Summit, call for papers closes this week:
https://events.linuxfoundation.org/dpdk-summit/
https://events.linuxfoundation.org/dpdk-summit/program/cfp/
* NOTE: deprecation notices should be sent soon so we can get sufficient Acks.
* Updated RC/Release dates:
RC3 July 5
RC4 July 12
Release July 17
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backporting in progress.
Next LTS releases:
* 22.11.2
* 21.11.5
* 20.11.9
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 16279 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-07-13
@ 2023-07-16 18:11 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-07-16 18:11 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2526 bytes --]
Release status meeting minutes 2023-07-13
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current target or completed dates for 23.07:
* V1: 22 April 2023
* RC1: 13 June 2023
* RC2: 27 June 2023
* RC3: 12 July 2023
* RC4: 18 July 2023
* Release: 21 July 2023
Subtrees
--------
* next-net
* Fixes only.
* next-net-intel
* Some fixes pending.
* next-net-mlx
* All RC3 patches merged.
* Some small changes remaining.
* next-net-mvl
* No more patches.
* next-eventdev
* No more patches.
* next-baseband
* No more patches.
* next-virtio
* Some minor patches.
* next-crypto
* Some patches/fixes for RC4.
* main
* RC3 is out.
* Only fixes and docs for RC4.
* DTS need more reviews.
* NOTE: deprecation notices should be sent soon so we can get sufficient Acks.
https://patchwork.dpdk.org/bundle/dmarchand/deprecation_notices/?state=*
* Updated RC/Release dates:
RC3 July 12
RC4 July 18
Release July 21
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backporting in progress.
Next LTS releases:
* 22.11.2
* 21.11.5
* 20.11.9
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15181 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2023-07-20
@ 2023-07-21 14:24 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-07-21 14:24 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2566 bytes --]
Release status meeting minutes 2023-07-20
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
* Canonical
Release Dates
-------------
The following are the proposed working dates for 23.07:
* V1: 22 April 2023
* RC1: 13 June 2023
* RC2: 27 June 2023
* RC3: 12 July 2023
* RC4: 18 July 2023
* Release: 21 July 2023
Subtrees
--------
* next-net
* Fix patches merged for RC4.
* next-net-intel
* Fixes merged.
* next-net-mlx
* Merged to RC4.
* next-net-mvl
* Merged to RC4.
* next-eventdev
* Merged to RC4.
* next-baseband
* Merged to RC4.
* next-virtio
* Merged to RC4.
* next-crypto
* Merged to RC4.
* main
* RC4 is out.
* Deprecation notices to be closed.
* NOTE: deprecation notices should be sent soon so we can get sufficient Acks.
https://patchwork.dpdk.org/bundle/dmarchand/deprecation_notices/?state=*
* Updated RC/Release dates:
Final release July 21
* NOTE: no community call until August 10.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backporting in progress.
Next LTS releases:
* 22.11.2
* 21.11.5
- Backports done to RC3
* 20.11.9
- Backports done to RC3
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
* NOTE: no community call until August 10.
[-- Attachment #2: Type: text/html, Size: 17536 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2023-08-10
@ 2023-08-10 19:02 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-08-10 19:02 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2367 bytes --]
Release status meeting minutes 2023-08-10
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD [No]
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 23.11:
* V1: 12 August 2023
* RC1: 29 September 2023
* RC2: 20 October 2023
* RC3: 27 October 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* New driver from Napatech
* New driver RNP: https://patchwork.dpdk.org/project/dpdk/list/?series=29118
* 1 other new driver
* next-net-intel
* No update.
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-baseband
* No update.
* next-virtio
* No update.
* next-crypto
* Some patches in progress.
* Patch to remove some of the experimental API tags.
* main
* Preparing for LTS release.
* Removing deprecated libraries.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backports ongoing. Awaiting test results.
Next LTS releases:
* 22.11.2
* 21.11.5
* 20.11.9
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14209 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2023-08-17
@ 2023-08-17 8:48 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-08-17 8:48 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2482 bytes --]
Release status meeting minutes 2023-08-17
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Debian/Microsoft
* Intel
* Marvell
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 23.11:
* V1: 12 August 2023
* RC1: 29 September 2023
* RC2: 20 October 2023
* RC3: 27 October 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* New driver from Napatech
* New driver RNP: https://patchwork.dpdk.org/project/dpdk/list/?series=29118
* 1 other new driver
* next-net-intel
* No update.
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-baseband
* No update.
* next-virtio
* No update.
* next-crypto
* No update.
* main
* Busy with Windows.
* Splitting EAL into two.
* Cleanups for C11
* New series for determining dependencies for unit tests.
* Working on build fixes.
* Preparing for LTS release.
* Removing deprecated libraries.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backports ongoing. Awaiting test results.
Next LTS releases:
* 22.11.2 - RC sent
* 21.11.5 - awaiting test reports
* 20.11.9 - released
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14366 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2023-08-17
@ 2023-08-24 10:54 15% Mcnamara, John
2023-08-31 8:28 15% ` Mcnamara, John
0 siblings, 1 reply; 140+ results
From: Mcnamara, John @ 2023-08-24 10:54 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2846 bytes --]
Release status meeting minutes 2023-08-17
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Marvell
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 23.11:
* V1: 12 August 2023
* RC1: 29 September 2023
* RC2: 20 October 2023
* RC3: 27 October 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* New driver from Napatech
* New driver RNP: https://patchwork.dpdk.org/project/dpdk/list/?series=29118
* 1 other new driver
* next-net-intel
* Some fixes merged.
* Some patch sets for IDPF and CPF under rework.
* next-net-mlx
* No update.
* next-net-mvl
* 30-40 patches merged.
* Almost everything reviewed.
* next-eventdev
* 10 patched pending.
* next-baseband
* Under review.
* next-virtio
* Working on improvements for VDUSE.
* Other patches under review.
* next-crypto
* 50-55 patches.
* 2-3 new features from Marvell
* RX inject patchset for review.
* SSL/TLS patches for review.
* SM2 patches.
* Merging not started yet.
* main
* Busy with Windows.
* Splitting EAL into two.
* Cleanups for C11
* New series for determining dependencies for unit tests. - Merged.
* Working on build fixes.
* Preparing for LTS release.
* Removing deprecated libraries.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backports ongoing. Awaiting test results.
Next LTS releases:
* 22.11.2 - Aug 31 set as release date.
* 21.11.5 - Testing reports received. Release in progress.
* 20.11.9 - Released
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15407 bytes --]
^ permalink raw reply [relevance 15%]
* RE: DPDK Release Status Meeting 2023-08-17
2023-08-24 10:54 15% Mcnamara, John
@ 2023-08-31 8:28 15% ` Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-08-31 8:28 UTC (permalink / raw)
To: Mcnamara, John, dev
[-- Attachment #1: Type: text/plain, Size: 3133 bytes --]
Note, these minutes were for 2023-08-24.
From: Mcnamara, John <john.mcnamara@intel.com>
Sent: Thursday, August 24, 2023 11:55 AM
To: dev@dpdk.org
Cc: thomas@monjalon.net; david.marchand@redhat.com
Subject: DPDK Release Status Meeting 2023-08-17
Release status meeting minutes 2023-08-17
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Marvell
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 23.11:
* V1: 12 August 2023
* RC1: 29 September 2023
* RC2: 20 October 2023
* RC3: 27 October 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* New driver from Napatech
* New driver RNP: https://patchwork.dpdk.org/project/dpdk/list/?series=29118
* 1 other new driver
* next-net-intel
* Some fixes merged.
* Some patch sets for IDPF and CPF under rework.
* next-net-mlx
* No update.
* next-net-mvl
* 30-40 patches merged.
* Almost everything reviewed.
* next-eventdev
* 10 patched pending.
* next-baseband
* Under review.
* next-virtio
* Working on improvements for VDUSE.
* Other patches under review.
* next-crypto
* 50-55 patches.
* 2-3 new features from Marvell
* RX inject patchset for review.
* SSL/TLS patches for review.
* SM2 patches.
* Merging not started yet.
* main
* Busy with Windows.
* Splitting EAL into two.
* Cleanups for C11
* New series for determining dependencies for unit tests. - Merged.
* Working on build fixes.
* Preparing for LTS release.
* Removing deprecated libraries.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backports ongoing. Awaiting test results.
Next LTS releases:
* 22.11.2 - Aug 31 set as release date.
* 21.11.5 - Testing reports received. Release in progress.
* 20.11.9 - Released
* 19.11.15
* Will be updated with CVE and critical fixes only.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
Opens
-----
* None
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>" for the invite.
[-- Attachment #2: Type: text/html, Size: 16601 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-09-07
@ 2023-09-07 10:43 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-09-07 10:43 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3094 bytes --]
Release status meeting minutes 2023-09-07
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 23.11:
* V1: 12 August 2023
* RC1: 29 September 2023
* RC2: 20 October 2023
* RC3: 27 October 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* New driver from Napatech
* New driver RNP: https://patchwork.dpdk.org/project/dpdk/list/?series=29118
* 1 other new driver
* More reviews are required.
* next-net-intel
* 12 patches awaiting merge.
* next-net-mlx
* Some patches coming next week.
* next-net-mvl
* All patches merged.
* next-eventdev
* Intel patches merged
* 12 patches pending.
* next-baseband
* 2 series under review.
* next-virtio
* Working on improvements for VDUSE.
* Other patches under review.
* No big features for now.
* next-crypto
* Started merged patches and giving comments.
* ~55 patches.
* 2-3 new features from Marvell
* RX inject patchset for review.
* SSL/TLS patches for review.
* SM2 patches.
* main
* Updates to the MAINTAINERs file to help with automated delegation.
* Some updates to bit count helpers for Windows but affects other
trees as well.
* Patch for Atomics
* This needs review since it is an important API that will touch a lot of components later.
* https://patchwork.dpdk.org/project/dpdk/list/?series=29318
* Preparing for LTS release.
* Removing deprecated libraries.
* Meeting cancelled next week due to DPDK Summit.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backports ongoing. Awaiting test results.
Next LTS releases:
* 22.11.2 - Aug 31 set as release date. In validation.
* 21.11.5 - Released
* 20.11.9 - Released
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15561 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-09-21
@ 2023-09-21 12:16 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-09-21 12:16 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2888 bytes --]
Release status meeting minutes 2023-09-21
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 23.11:
* V1: 12 August 2023
* RC1: 29 September 2023
* RC2: 20 October 2023
* RC3: 27 October 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* Mbuf recycle merged.
* New driver from Napatech
* Discussions/reviews ongoing
* New driver from RNP
* Approx 200 patches
* next-net-intel
* No update
* next-net-mlx
* Some patches integrated and some in progress
* next-net-mvl
* All patches merged.
* next-eventdev
* Intel patches merged
* 3 new features under review
* next-baseband
* 2 series under review.
* 1 accepted and moving to PR
* next-virtio
* Working on improvements for VDUSE.
* Other patches under review.
* next-crypto
* Started merging patches. About 50% merged.
* 2-3 new features from Marvell
* RX inject patchset for review.
* SSL/TLS patches for review.
* SM2 patches.
* main
* PCI API cleanup merged. Subtrees take note.
* Patch for Atomics
* This needs review since it is an important API that will touch a lot of components later.
* https://patchwork.dpdk.org/project/dpdk/list/?series=29318
* Preparing for LTS release.
* Removing deprecated libraries.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 29 September 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backports ongoing. Awaiting test results.
Next LTS releases:
* 22.11.2 - Released
* 21.11.5 - Released
* 20.11.9 - Released
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15363 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-09-28
@ 2023-09-29 15:26 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-09-29 15:26 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 3111 bytes --]
Release status meeting minutes 2023-09-28
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia [No]
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023 - was 29 September 2023
* RC2: 20 October 2023
* RC3: 27 October 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* Some patches merged
* Focusing on eth_dev patches for RC1
* Around 50% of remaining patches are rte_flow
* needs some reviews
* next-net-intel
* Some patches waiting for merge
* Tree will be ready for RC1 be EOD 2023-09-28
* next-net-mlx
* No update
* next-net-mvl
* All patches merged.
* Will send PR 2023-09-29
* next-eventdev
* Waiting for some fixes for cnxk
* Will send PR 2023-09-29
* next-baseband
* Reviewing patches for VRB2 series.
* next-virtio
* Working on improvements for VDUSE.
* Other patches under review.
* next-crypto
* 3 series to complete before PR
* 2-3 new features from Marvell
* RX inject patchset for review.
* SSL/TLS patches for review.
* SM2 patches need ack
* main
* Working on Control Threads
* PCI API cleanup merged. Subtrees take note.
* Patch for Atomics
* This needs review since it is an important API that will touch a lot of components later.
* https://patchwork.dpdk.org/project/dpdk/list/?series=29318
* Preparing for LTS release.
* Removing deprecated libraries.
* DPDK Summit videos are out:
https://www.youtube.com/playlist?list=PLo97Rhbj4ceJf9p-crjGvGvn8pMWrJ_cV
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 11 October 2023
* PMD features freeze (-rc2): 20 October 2023
* Builtin applications features freeze (-rc3): 27 October 2023
* Release: 15 November 2023
LTS
---
Backports ongoing. Awaiting test results.
Next LTS releases:
* 22.11.2 - Released
* 21.11.5 - Released
* 20.11.9 - Released
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15918 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-10-05
@ 2023-10-05 9:04 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-10-05 9:04 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2726 bytes --]
Release status meeting minutes 2023-10-05
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023
* RC2: 27 October 2023
* RC3: 3 November 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* Initial pull done.
* Working on the rest of the tree.
* There are still a number of rte_flow patches pending merge but not having
reviews
* next-net-intel
* No update
* next-net-mlx
* No update
* next-net-mvl
* Will send PR today
* next-eventdev
* Sent PR
* next-baseband
* Reviewing patches for VRB2 series.
* next-virtio
* Other patches under review.
* next-crypto
* 3 series pending PR - will be complete by the end of the week
* 2-3 new features from Marvell
* RX inject patchset for review.
* SSL/TLS patches for review.
* SM2 patches need ack
* main
* Patch for Atomics merged.
* Some additions/changes needed in RC2.
* Reviewing dispatcher library - new library approved by tech board.
* Working on Control Threads
* PCI API cleanup merged. Subtrees take note.
* Preparing for LTS release.
* Removing deprecated libraries.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 11 October 2023
* PMD features freeze (-rc2): 27 October 2023
* Builtin applications features freeze (-rc3): 3 November 2023
* Release: 15 November 2023
LTS
---
LTS in the current cycle have been released.
* 22.11.2 - Released
* 21.11.5 - Released
* 20.11.9 - Released
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14702 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-10-12
@ 2023-10-12 18:56 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-10-12 18:56 UTC (permalink / raw)
To: dev; +Cc: thomas, david.marchand
[-- Attachment #1: Type: text/plain, Size: 2562 bytes --]
Release status meeting minutes 2023-10-12
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023 - Trending 16 October
* RC2: 27 October 2023
* RC3: 3 November 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* Mainly in sync with main for RC1
* However some eth_dev patches remaining
* Question around PTP patches
* next-net-intel
* All the main feature for CPF and IPF merged and awaiting pull.
* next-net-mlx
* Waiting for pull.
* next-net-mvl
* PR sent.
* Some patches for RC2.
* next-eventdev
* PR sent.
* next-baseband
* Preparing PR.
* next-virtio
* No big fixes.
* Some fixes.
* next-crypto
* RC1 patches merged to main.
* main
* Merged AMD power series.
* Working on dispatcher library, should be ready for RC1.
https://patchwork.dpdk.org/project/dpdk/list/?series=29250
* Looking at patches for DMA dev and Graph nodes.
* RC1 targeted for Monday 16th October
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 11 October 2023
* PMD features freeze (-rc2): 27 October 2023
* Builtin applications features freeze (-rc3): 3 November 2023
* Release: 15 November 2023
LTS
---
LTS in the current cycle have been released.
* 22.11.2 - Released
* 21.11.5 - Released
* 20.11.9 - Released
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14029 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2023-10-19
@ 2023-10-19 19:41 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-10-19 19:41 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2808 bytes --]
Release status meeting minutes 2023-10-19
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023
* RC2: 27 October 2023 - Trending to 1 November
* RC3: 3 November 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* RC1 released
* next-net-intel
* Will submit patch for missing actions in P4/rte_flow
* next-net-mlx
* ~50 patches for RC2
* next-net-mvl
* Some patches for RC2.
* Will send PR today
* next-eventdev
* vdev fixes merged.
* Will send PR today
* next-baseband
* Reviews almost complete
* Waiting for revisions
* next-virtio
* Some reviews to do.
* No big features, mainly fixes.
* next-crypto
* ~20 patches in RC2 backlog
* main
* RC1 released: October 18th
* Series that need acks/reviews:
https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Series to mark experimental APIs as stable. Request for maintainers to
review an APIs that will move to stable.
* Regression in bitops API in RC1 - fix under discussion
Breaks OVS builds
* Reviews in progress for some of applications like DMA perf and ML dev test, and Pipeline.
* RC2 trending to November 1st.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 11 October 2023
* PMD features freeze (-rc2): 27 October 2023 - Trending to 1 November
* Builtin applications features freeze (-rc3): 3 November 2023
* Release: 15 November 2023
LTS
---
LTS in the current cycle have been released.
* 22.11.2 - Released
* 21.11.5 - Released
* 20.11.9 - Released
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14705 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-10-26
@ 2023-10-26 22:27 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-10-26 22:27 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2856 bytes --]
Release status meeting minutes 2023-10-26
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023
* RC2: 27 October 2023 - Trending to 1 November
* RC3: 3 November 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* Eth_dev patches need to be finalized for RC2.
* 3 new drivers - not merged yet.
* Napatech driver will probably be in the next release
* next-net-intel
* Some fixes merged.
* next-net-mlx
* Some patches merged.
* ~45 patches for RC2
* next-net-mvl
* Prepping for RC2.
* next-eventdev
* Prepping for RC2.
* next-baseband
* Some patches ready
* Patches for new FPGA variant
* next-virtio
* Some fixes added and ready for pull.
* next-crypto
* ~10 patches in RC2 backlog.
* Merging in progress.
* main
* Looking at Windows patches.
* Series that need acks/reviews:
https://patchwork.dpdk.org/bundle/dmarchand/need_reviews/
* Series to mark experimental APIs as stable. Request for maintainers to
review an APIs that will move to stable.
* Regression in bitops API in RC1 - Fix merged.
* Reviews in progress for some of applications like DMA perf and ML dev test, and Pipeline.
* RC2 trending to November 1st.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 11 October 2023
* PMD features freeze (-rc2): 27 October 2023 - Trending to 1 November
* Builtin applications features freeze (-rc3): 3 November 2023
* Release: 15 November 2023
LTS
---
LTS in the current cycle have been released.
* 22.11.2 - Released
* 21.11.5 - Released
* 20.11.9 - Released
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* v22.11 in Debian 12
* Ubuntu 22.04-LTS contains 21.11
* Ubuntu 23.04 contains 22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14760 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-11-02
@ 2023-11-02 10:58 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-11-02 10:58 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
Release status meeting minutes 2023-11-02
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023
* RC2: 27 October 2023 - Trending to 3 November
* RC3: 3 November 2023
* Release: 15 November 2023
Subtrees
--------
* next-net
* Tree not closed yet for RC2.
* Reviews and updates ongoing.
* next-net-intel
* Some fixes merged.
* Patch for prog action
* next-net-mlx
* Almost ready for merge.
* next-net-mvl
* PR sent.
* next-eventdev
* PR sent.
* next-baseband
* PR sent.
* One series still under review.
* next-virtio
* PR sent.
* One series still under review.
* Some fixes pending.
* next-crypto
* 3-4 patches in RC2 backlog.
* IPsecMB patch needs ack.
* main
* Starting to pull for RC2.
* RC2 trending to Friday November 3rd.
Proposed Schedule for 2023
--------------------------
See also http://core.dpdk.org/roadmap/#dates
23.11
* Proposal deadline (RFC/v1 patches): 12 August 2023
* API freeze (-rc1): 11 October 2023
* PMD features freeze (-rc2): 27 October 2023 - Trending to 3 November
* Builtin applications features freeze (-rc3): 3 November 2023
* Release: 15 November 2023
LTS
---
LTS in the current cycle have been released.
* 22.11.3 - In progress
* 21.11.6 - In progress
* 20.11.10 - In progress
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14013 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2023-11-09
@ 2023-11-09 10:07 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-11-09 10:07 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]
Release status meeting minutes 2023-11-09
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023
* RC2: 6 November 2023
* RC3: 13 November 2023
* RC4: 20 November 2023
* Release: 22 November 2023
Subtrees
--------
* next-net
* RC2 released
* Working on bugs/fixes.
* next-net-intel
* QA testing ongoing.
* Some small fixes for post RC2.
* next-net-mlx
* No update.
* next-net-mvl
* QA testing ongoing.
* Some small fixes to apply.
* next-eventdev
* QA testing ongoing.
* Some small fixes to apply.
* next-baseband
* PR being prepared.
* next-virtio
* No update.
* next-crypto
* 8-9 patches for RC3
* Coccinelle script for Null checks.
* Preparing PR.
* main
* RC2 released November 6th.
* Provisional dates for the next phases of the release:
* RC3: 13 November 2023
* RC4: 20 November 2023
* Release: 22 November 2023
Proposed Schedule for 2023
--------------------------
See notes above and http://core.dpdk.org/roadmap/#dates
LTS
---
LTS in the current cycle are in progress.
* 22.11.3 - In progress
* 21.11.6 - In progress
* 20.11.10 - In progress
* 19.11.15
* Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13550 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2023-11-16
@ 2023-11-16 21:13 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-11-16 21:13 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2686 bytes --]
Release status meeting minutes 2023-11-16
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023
* RC2: 6 November 2023
* RC3: 13 November 2023
* RC4: 21 November 2023
* Release: 23 November 2023
The following are the current working dates for 24.03:
- Proposal deadline (RFC/v1 patches): 22 December 2023
- API freeze (-rc1): 5 February 2024
- PMD features freeze (-rc2): 23 February 2024
- Builtin applications features freeze (-rc3): 4 March 2024
- Release: 14 March 2024
Subtrees
--------
* next-net
* RC3 released
* Working on fixes.
https://bugs.dpdk.org/show_bug.cgi?id=1326
* next-net-intel
* Most fixes merged in RC3.
* Some small fixes and docs pending for RC4.
* next-net-mlx
* Some small fixes and docs pending for RC4.
* next-net-mvl
* Merged in RC3.
* next-eventdev
* Merged in RC3.
* next-baseband
* PR sent.
* next-virtio
* PR sent and merged in RC3.
* next-crypto
* 3-4 fixes for RC4
* main
* Move Experimental features older than 2 years to stable.
* Waiting for latest version of DTS features.
* Provisional dates for the next phases of the release:
* RC4: 21 November 2023
* Release: 23 November 2023
Proposed Schedule for 2023
--------------------------
See http://core.dpdk.org/roadmap/#dates
LTS
---
* 22.11.3 - In progress
* 21.11.6 - In progress
* 20.11.10 - In progress
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
Drafts/Notes
-----
* 22.11.1 - Xueming
* 21.11.4 - Kevin
* 20.11.8 - Luca
* 19.11.15 - Christian
[-- Attachment #2: Type: text/html, Size: 15117 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-11-23
@ 2023-11-24 8:53 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-11-24 8:53 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2722 bytes --]
Release status meeting minutes 2023-11-23
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023
* RC2: 6 November 2023
* RC3: 13 November 2023
* RC4: 23 November 2023
* Release: 24 November 2023
The following are the current working dates for 24.03:
- Proposal deadline (RFC/v1 patches): 22 December 2023
- API freeze (-rc1): 5 February 2024
- PMD features freeze (-rc2): 23 February 2024
- Builtin applications features freeze (-rc3): 4 March 2024
- Release: 14 March 2024
Subtrees
--------
* next-net
* No direct changes past RC4
* next-net-intel
* No direct changes past RC4
* next-net-mlx
* No direct changes past RC4
* next-net-mvl
* No direct changes past RC4
* next-eventdev
* No direct changes past RC4
* next-baseband
* No direct changes past RC4
* next-virtio
* No direct changes past RC4
* next-crypto
* No direct changes past RC4
* main
* RC4 released
* Release targeted for 24 November 2023, depending on some build/CI issues:
* Build/link issue on Debian
https://salsa.debian.org/debian/dpdk/-/jobs/4949787
* cpfl compilation issue
https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_Next/i586
* LCOREs autotest timing out on ARM:
https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_12/aarch64
Proposed Schedule for 2023
--------------------------
See http://core.dpdk.org/roadmap/#dates
LTS
---
* 22.11.3 - In progress
* 21.11.6 - In progress
* 20.11.10 - In progress
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14353 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-12-07
@ 2023-12-12 14:23 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-12-12 14:23 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2607 bytes --]
Release status meeting minutes 2023-12-07
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023
* RC2: 6 November 2023
* RC3: 13 November 2023
* RC4: 23 November 2023
* Release: 24 November 2023
The following are the current working dates for 24.03:
- Proposal deadline (RFC/v1 patches): 22 December 2023/Proposal 29 December
- API freeze (-rc1): 5 February 2024
- PMD features freeze (-rc2): 23 February 2024
- Builtin applications features freeze (-rc3): 4 March 2024
- Release: 14 March 2024
Subtrees
--------
* next-net on
* No direct changes past RC4
* next-net-intel
* No updates this week.
* next-net-mlx
* No updates this week.
* Roadmap sent.
* next-net-mvl
* Starting to merge patches.
* Roadmap sent.
* next-eventdev
* Starting to merge patches.
* next-baseband
* No updates this week.
* next-virtio
* No updates this week.
* next-crypto
* No updates this week.
* main
* New branch mirroring to GitHub to reduce load on git.dpdk.org.
* Request for Roadmaps: https://core.dpdk.org/roadmap/
* Merging logging and other cleanups.
* Improved Windows support.
* Proposal to move v1 date from December 22 to 29
Proposed Schedule for 2023
--------------------------
See http://core.dpdk.org/roadmap/#dates
LTS
---
* 22.11.4 - In progress
* 21.11.6 - In progress - backports mainly done
* 20.11.10 - In progress - RC1 sent - testing ongoing
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14155 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2023-12-14
@ 2023-12-14 13:39 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2023-12-14 13:39 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2484 bytes --]
Release status meeting minutes 2023-12-14
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 23.11:
* V1: 12 August 2023
* RC1: 11 October 2023
* RC2: 6 November 2023
* RC3: 13 November 2023
* RC4: 23 November 2023
* Release: 24 November 2023
The following are the current working dates for 24.03:
- Proposal deadline (RFC/v1 patches): 29 December 2023 (moved from 22 December)
- API freeze (-rc1): 5 February 2024
- PMD features freeze (-rc2): 23 February 2024
- Builtin applications features freeze (-rc3): 4 March 2024
- Release: 14 March 2024
Subtrees
--------
* next-net on
* Patches starting to arrive.
* next-net-intel
* No updates this week.
* next-net-mlx
* Roadmap sent.
* next-net-mvl
* Starting to merge patches.
* Roadmap sent.
* next-eventdev
* Starting to merge patches.
* next-baseband
* No updates this week.
* next-virtio
* No updates this week.
* next-crypto
* ~37 patches in backlog.
* main
* V1 date moved to December 29th
* New branch mirroring to GitHub to reduce load on git.dpdk.org.
* Request for Roadmaps: https://core.dpdk.org/roadmap/
* Looking for a new maintainer for the DMA device performance tool.
Proposed Schedule for 2023
--------------------------
See http://core.dpdk.org/roadmap/#dates
LTS
---
* 22.11.4 - In progress
* 21.11.6 - RC in progress
* 20.11.10 - Released.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13458 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-01-18
@ 2024-01-18 19:59 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-01-18 19:59 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]
Release status meeting minutes 2024-01-18
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 24.03:
* V1: 29 December 2023
* RC1: 5 February 2024
* RC2: 23 February 2024
* RC3: 4 March 2024
* Release: 14 March 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Starting to review patches.
* next-net-intel
* Will merge initial patches this week
* next-net-mlx
* Some patches merged.
* next-net-mvl
* Port representor for cnxk work in progress.
* next-eventdev
* New feature EMLdev Event Adaptor library.
* next-baseband
* Reviews started and changes requested.
* next-virtio
* Patch from Marvell under review.
* next-crypto
* Started merging.
* ~80 patches in backlog.
* TLS support in cnxk driver.
* New Nitrox PMD for compressdev.
* main
* Cleanups in progress.
* New bus driver from Huawei.
* Working on iavf fix for OVS.
Proposed Schedule for 2023
--------------------------
See http://core.dpdk.org/roadmap/#dates
LTS
---
* 22.11.4 - In progress
* 21.11.6 - Released.
* 20.11.10 - Released.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 12693 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-01-25
@ 2024-01-25 16:26 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-01-25 16:26 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
Release status meeting minutes 2024-01-25
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* Intel
* Marvell
* Nvidia [No]
* Red Hat
Release Dates
-------------
The following are the current working dates for 24.03:
* V1: 29 December 2023
* RC1: 5 February 2024
* RC2: 23 February 2024
* RC3: 4 March 2024
* Release: 14 March 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* No update.
* next-net-intel
* Merged to main.
* next-net-mlx
* No update.
* next-net-mvl
* Port representor for cnxk work in progress.
* next-eventdev
* New feature MLdev Event Adaptor library.
* next-baseband
* Reviews started and changes requested.
* New version of BBdev patches.
* next-virtio
* Patch from Marvell under review.
* next-crypto
* Started merging.
* ~40 merged. ~40 patches in backlog.
* TLS support in cnxk driver.
* New Nitrox PMD for compressdev.
* main
* Cleanups in progress.
* Windows patches in progress.
* New bus driver from Huawei.
* Looking at argument parsing.
LTS
---
* 22.11.4 - Released.
* 21.11.6 - Released.
* 20.11.10 - Released.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 12391 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-02-01
@ 2024-02-05 14:35 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-02-05 14:35 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2348 bytes --]
Release status meeting minutes 2024-02-01
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 24.03:
* V1: 29 December 2023
* RC1: 12 February 2024
* RC2: 27 February 2024
* RC3: 6 March 2024
* Release: 14 March 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Ethdev patches reviewed and some merged.
* next-net-intel
* Merged to main.
* next-net-mlx
* No update.
* next-net-mvl
* Port representor for cnxk work in progress.
* next-eventdev
* New feature MLdev Event Adaptor library.
- Needs unit test
* next-baseband
* Preparing pull request for end of week.
* next-virtio
* Preparing pull request for end of week.
* next-crypto
* Ready for pull.
* TLS support in cnxk driver.
* New Nitrox PMD for compressdev.
* QAT patches require acks.
* main
* Cleanups in progress.
- Log cleanup.
* Windows patches in progress.
* New bus driver from Huawei.
* Looking at argument parsing.
* Proposed 24.03 dates:
* RC1: 12 February 2024
* RC2: 27 February 2024
* RC3: 6 March 2024
* Release: 14 March 2024
LTS
---
* 22.11.4 - Released.
* 21.11.6 - Released.
* 20.11.10 - Released.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13163 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-02-15
@ 2024-02-15 17:27 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-02-15 17:27 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2402 bytes --]
Release status meeting minutes 2024-02-15
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM [No]
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current working dates for 24.03:
* V1: 29 December 2023
* RC1: 12 February 2024
* RC2: 27 February 2024
* RC3: 6 March 2024
* Release: 14 March 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Ethdev patches reviewed and some merged.
* Merging ongoing for RC1.
* next-net-intel
* Merged to main.
* next-net-mlx
* PR sent for RC1.
* next-net-mvl
* PR sent for RC1.
* next-eventdev
* New feature MLdev Event Adaptor library.
- Needs unit test
* PR sent for RC1.
* next-baseband
* PR sent for RC1.
* next-virtio
* PR sent for RC1.
* Looking at some fixes.
* next-crypto
* PR sent for RC1.
* TLS support in cnxk driver.
* New Nitrox PMD for compressdev reworking for RC2.
* Looking at patches for RC2.
* main
* Cleanups in progress.
- Log cleanup.
* Windows patches in progress.
* New bus driver from Huawei.
* Looking at argument parsing.
* Proposed 24.03 dates:
* RC1: 12 February 2024 - Trending to 19th.
* RC2: 27 February 2024
* RC3: 6 March 2024
* Release: 14 March 2024
LTS
---
* 22.11.4 - Released.
* 21.11.6 - Released.
* 20.11.10 - Released.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13519 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-02-22
@ 2024-02-22 10:19 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-02-22 10:19 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]
Release status meeting minutes 2024-02-22
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.03:
* V1: 29 December 2023
* RC1: 21 February 2024
* RC2: 4 March 2024
* RC3: 11 March 2024
* Release: 20 March 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Some patch sets didn't make it into RC1.
* Will review of RC2.
* next-net-intel
* Merged to main.
* next-net-mlx
* RC1 merged.
* ~50 patches for RC2.
* next-net-mvl
* Merged for RC1.
* next-eventdev
* Merged for RC1.
* next-baseband
* PR for RC1 to be reworked for RC2.
* next-virtio
* Merged for RC1.
* Some additional rework on patches for RC2.
* next-crypto
* Merged for RC1.
* ~ 40 patches for RC2.
* QAT patches need acks.
* TLS support in cnxk driver.
* New Nitrox PMD for compressdev reworking for RC2.
* main
* RC1 released 21 February.
* Proposed 24.03 dates:
* RC2: 4 March 2024
* RC3: 11 March 2024
* Release: 20 March 2024
LTS
---
* 22.11.4 - Released.
* 21.11.6 - Released.
* 20.11.10 - Released.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 12796 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-02-29
@ 2024-03-05 13:15 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-03-05 13:15 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]
Release status meeting minutes 2024-02-29
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.03:
* V1: 29 December 2023
* RC1: 21 February 2024
* RC2: 4 March 2024
* RC3: 11 March 2024
* Release: 20 March 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Testpmd patch from Napatech.
* AF_XDP update and docs.
* next-net-intel
* Some additions/fixes for RC2.
* next-net-mlx
* Mainly merged for RC2.
* next-net-mvl
* 40 patches to merge for RC2.
* next-eventdev
* Bruce patches reviewed. Good to merge.
* Prepping for RC2.
* next-baseband
* PR for RC1 was reworked for RC2.
* next-virtio
* Prepping for RC2.
* next-crypto
* Merged for RC1.
* ~ 35 patches for RC2.
* There is a new Ionic driver. Probably will be postponed to next release.
* main
* Windows series being reviewed.
* Proposed 24.03 dates:
* RC2: 4 March 2024
* RC3: 11 March 2024
* Release: 20 March 2024
LTS
---
* 22.11.4 - Released.
* 21.11.6 - Released.
* 20.11.10 - Released.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 12656 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-03-07
@ 2024-03-07 10:05 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-03-07 10:05 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]
Release status meeting minutes 2024-03-07
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.03:
* V1: 29 December 2023
* RC1: 21 February 2024
* RC2: 7 March 2024
* RC3: 11 March 2024
* Release: 20 March 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Patches merged for RC2.
* Only docs and fixes in RC3.
* next-net-intel
* Pushed ~10 patches for RC2.
* Issue: https://bugs.dpdk.org/show_bug.cgi?id=1386
* next-net-mlx
* Merged for RC2.
* next-net-mvl
* Patches merged for RC2.
* next-eventdev
* Patches merged for RC2.
* next-baseband
* 2 fixes merged.
* Ready for RC2.
* next-virtio
* Ready for RC2.
* next-crypto
* Merged for RC2.
* Series for IPsecMB causing issue in CI.
- Postponed for RC3 until CI fixed.
* main
* Windows series merged.
* Working on hot fix for Hash library.
- This is currently blocking RC2.
* RC2 should be out 7 March 2024
* Proposed 24.03 dates:
* RC2: 7 March 2024
* RC3: 11 March 2024
* Release: 20 March 2024
LTS
---
* 22.11.4 - Released.
* 21.11.6 - Released.
* 20.11.10 - Released.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 22.04-LTS contains DPDK v21.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13144 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-03-14
@ 2024-03-14 10:16 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-03-14 10:16 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2388 bytes --]
Release status meeting minutes 2024-03-14
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.03:
* V1: 29 December 2023
* RC1: 21 February 2024
* RC2: 8 March 2024
* RC3: 15 March 2024
* Release: 27 March 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Almost complete for RC3.
* Trying to include test_pmd cleanup
* Outstanding TAP patchset
* next-net-intel
* TODO
* next-net-mlx
* PR sent for RC3.
* next-net-mvl
* PR sent for RC3.
* next-eventdev
* Patches merged for RC2.
* next-baseband
* No new features/fixes for RC3.
* next-virtio
* Some last minutes issue being fixed.
* next-crypto
* Mostly merged for RC3.
* Some APP patches remaining.
* main
* Bug in Ubuntu ASAN library that make tests crash.
- David has a fix available for testing.
- https://github.com/actions/runner-images/issues/9491
- https://git.dpdk.org/dpdk/commit/?id=d0d7032a3f6e66c1a09b13ad42e9d7975db8c627
* Merged workaround for Lcore autotest.
* Working on build fixes.
* Adding new DTS test
* Proposed 24.03 dates:
* RC3: 15 March 2024
* Release: 27 March 2024
LTS
---
* 22.11.4 - Released.
* 21.11.6 - Released.
* 20.11.10 - Released.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04-LTS will contain DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13302 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-03-21
@ 2024-03-21 14:49 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-03-21 14:49 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]
Release status meeting minutes 2024-03-21
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.03:
* V1: 29 December 2023
* RC1: 21 February 2024
* RC2: 8 March 2024
* RC3: 18 March 2024
* RC4: 22 March 2024
* Release: 27 March 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Some fixes merged.
* Ready for Pull
* next-net-intel
* 2 fix/doc patches.
* next-net-mlx
* Series merged after RC3.
* next-net-mvl
* No new changes post RC3.
* next-eventdev
* No new changes post RC3.
* next-baseband
* No new changes post RC3.
* next-virtio
* No new changes post RC3.
* next-crypto
* Some doc patches.
* Patch for ipsecgw sample app to be postponed to
next release due to risk of breakage in other PMDs.
* main
* RH testing for RC3 - no major issues.
* Looking at Windows patches for next release to
make sure there aren't any API/ABI breaking changes.
* Doc fixes and release notes.
* Proposed 24.03 dates:
* RC4: 22 March 2024
* Release: 27 March 2024
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - In progress.
* 22.11.5 - In progress.
* 21.11.7 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04-LTS will contain DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13374 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-03-28
@ 2024-03-28 11:30 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-03-28 11:30 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2733 bytes --]
Release status meeting minutes 2024-03-28
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.03:
* V1: 29 December 2023
* RC1: 21 February 2024
* RC2: 8 March 2024
* RC3: 15 March 2024
* Release: 27 March 2024
* 24.07 Proposed dates:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Complete for RC4/Release.
* next-net-intel
* Complete for RC4/Release.
* next-net-mlx
* Complete for RC4/Release.
* next-net-mvl
* Complete for RC4/Release.
* next-eventdev
* Complete for RC4/Release.
* next-baseband
* Complete for RC4/Release.
* next-virtio
* Complete for RC4/Release.
* next-crypto
* Complete for RC4/Release.
* main
* Working on release notes and final documentation fixes.
* Target release March 28th.
* 24.07 Proposed dates:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - In progress.
* 22.11.5 - In progress.
* 21.11.7 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04-LTS will contain DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14476 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-04-11
@ 2024-04-11 9:50 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-04-11 9:50 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2935 bytes --]
Release status meeting minutes 2024-04-11
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia [No]
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.03:
* V1: 29 December 2023
* RC1: 21 February 2024
* RC2: 8 March 2024
* RC3: 15 March 2024
* Release: 27 March 2024
* 24.07 Proposed dates:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* New Napatech PMD.
* next-net-intel
* Some patches applied from last release.
* There will be a number of base code updates
in this release.
* Test failure:
https://mails.dpdk.org/archives/test-report/2024-April/634973.html
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-baseband
* Merging 1 patchset from previous release.
* next-virtio
* 2 series posted.
* next-crypto
* Some patches from previous release.
* Patches from Pensando.
* main
* Some issues with latest OVS and DPDK 23.11.
* Looking at changes for Graph library.
* Ongoing changes for Windows.
* 24.07 Proposed dates:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - In progress.
* 22.11.5 - In progress.
* 21.11.7 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04-LTS will contain DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15014 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-04-18
@ 2024-04-18 14:51 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-04-18 14:51 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2996 bytes --]
Release status meeting minutes 2024-04-18
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.03:
* V1: 29 December 2023
* RC1: 21 February 2024
* RC2: 8 March 2024
* RC3: 15 March 2024
* Release: 27 March 2024
* 24.07 Proposed dates:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* New Napatech PMD.
* next-net-intel
* Some patches applied from last release.
* There will be a number of base code updates
in this release.
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-baseband
* Merging 1 patchset from previous release.
* next-virtio
* 2 series posted.
* next-crypto
* Some patches from previous release.
* Patches from Pensando.
* main
* Some issues with latest OVS and DPDK 23.11.
- Fixes in progress
* Looking at changes for Graph library.
* Ongoing changes for Windows.
- Several series.
* High level of patches in this release (more than 1000).
* 24.07 Proposed dates:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - In progress. Test reports incoming.
* 22.11.5 - In progress. Test reports incoming.
* 21.11.7 - In progress. Test reports incoming.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04-LTS will contain DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15012 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-04-25
@ 2024-04-25 9:04 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-04-25 9:04 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2852 bytes --]
Release status meeting minutes 2024-04-25
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* New Napatech PMD.
* next-net-intel
* Some patches applied from last release.
* There will be a number of base code updates
in this release.
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-baseband
* Merging 1 patchset from previous release.
* next-virtio
* 2 series posted.
* next-crypto
* Some patches from previous release.
* Patches from Pensando.
* New driver from Linaro
* main
* Looking at changes for Graph library.
* Ongoing changes for Windows.
- Several series.
* New DMA driver from Marvell
* High level of patches in this release (more than 1000).
* Note, we are looking for new maintainers for Bonding and Failsafe.
* 24.07 Proposed dates:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - In progress. Test reports incoming.
* 22.11.5 - Released.
* 21.11.7 - RC out. Testing ongoing.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04-LTS will contain DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14243 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-05-09
@ 2024-05-09 8:46 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-05-09 8:46 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2629 bytes --]
Release status meeting minutes 2024-05-09
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* New Napatech PMD.
* next-net-intel
* Some patches applied from last release.
* There will be a number of base code updates
in this release.
* next-net-mlx
* Starting to merge some patches.
* next-net-mvl
* Starting to review patches. No merges yet.
* next-eventdev
* Starting to review patches. No merges yet.
* next-baseband
* No update.
* next-virtio
* No update.
* next-crypto
* No update on tree.
* ~40 patches in backlog.
* main
* Looking at changes for Graph library.
* Ongoing changes for Windows.
- Several series.
* New DMA driver from Marvell
* Note, we are looking for new maintainers for Bonding and Failsafe.
* 24.07 Proposed dates:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
LTS
---
* 23.11.1 - In progress. Test reports incoming.
* 22.11.5 - Released.
* 21.11.7 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04-LTS will contain DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13782 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-05-16
@ 2024-05-16 8:56 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-05-16 8:56 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2800 bytes --]
Release status meeting minutes 2024-05-16
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 7 June 2024
- PMD features freeze (-rc2): 21 June 2024
- Builtin applications features freeze (-rc3): 28 June 2024
- Release: 10 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* New Napatech PMD. Discussion ongoing.
* next-net-intel
* Some patches applied from last release.
* There will be a number of base code updates
in this release.
* next-net-mlx
* Starting to merge some patches.
* next-net-mvl
* Starting to review patches. No merges yet.
* next-eventdev
* Starting to review patches. No merges yet.
* next-baseband
* Reviewing updated versions.
* next-virtio
* Reviews starting.
* next-crypto
* ~40 patches in backlog.
* main
* ~700-800 patches in this release.
* Merging DTS changes.
* Looking at changes for Graph library.
* Ongoing changes for Windows.
- Several series.
- The stdatomic patchset is ready. It will be merged this week.
* New DMA driver from Marvell
* Patch submitted for reading ZSTD compressed firmware in Ubuntu 24.04.
It is reviewed, tested and will be merged soon.
* Alpine compilation should be fixed now. Will work with UNH to restore this test
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - In progress. Test reports incoming.
* 22.11.5 - Released.
* 21.11.7 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04-LTS will contain DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13774 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-06-06
@ 2024-06-06 13:15 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-06-06 13:15 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2590 bytes --]
Release status meeting minutes 2024-06-06
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Canonical
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 14 June 2024
- PMD features freeze (-rc2): 5 July 2024
- Builtin applications features freeze (-rc3): Mid July 2024 (TBC)
- Release: End July 2023 (TBC)
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Starting to merge patches.
* Tap PMD with RSS and eBPF was broken. Fixed now but should
be part of the DTS. Looking for a volunteer.
* Realtec drivers submitted
* Napatech update submitted
* next-net-intel
* Some patches applied from last release.
* There will be a number of base code updates
in this release.
* next-net-mlx
* ~34 being prepared for merge
* next-net-mvl
* PR sent.
* next-eventdev
* PR sent but there are some more patches that arrived
after the PR so this may be reworked.
* next-baseband
* Starting reviews.
* next-virtio
* Starting reviews.
* next-crypto
* Some patches merged.
* Reviews ongoing.
* main
* RC1 and RC2 dates will move out:
- RC1: Friday June 14th
- RC2: Friday July 5th
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - Released.
* 22.11.5 - Released.
* 21.11.7 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04-LTS will contain DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13616 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-06-13
@ 2024-06-18 10:42 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-06-18 10:42 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2766 bytes --]
Release status meeting minutes 2024-06-13
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD [No]
* ARM
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 14 June 2024
- PMD features freeze (-rc2): 5 July 2024
- Builtin applications features freeze (-rc3): Mid July 2024 (TBC)
- Release: End July 2023 (TBC)
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Merged most of the ethdev patches.
* GENEVE one is remaining, I guess that is for next release.
* Napatech PMD reviewed, will wait for new version.
* Overall next-net is OK for -rc1.d
* next-net-intel
* Large ICE driver base code update submitted and waiting
review.
* next-net-mlx
* Almost completed for merge.
* Still working on one patchset.
* next-net-mvl
* PR ready.
* next-eventdev
* PR ready.
* next-baseband
* Prepared a pull request, there is one series which needs
a respin from Hernan.
* next-virtio
* Prepared a pull request (around 16 patches merged),
more patches need reviews and will go to rc2.
* next-crypto
* 2 PMDs to merge but should be ready for the PR.
* Awaiting some updates as requested from submitters.
* main
* Some series for Windows merged.
* Working on some respin patches.
* RC1 should be out Monday 17th June
* RC2 targeted for 5 July 2024
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - Released.
* 22.11.5 - Released.
* 21.11.7 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13944 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-06-20
@ 2024-06-20 10:59 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-06-20 10:59 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2787 bytes --]
Release status meeting minutes 2024-06-20
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 14 June 2024
- PMD features freeze (-rc2): 5 July 2024
- Builtin applications features freeze (-rc3): Mid July 2024 (TBC)
- Release: End July 2023 (TBC)
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Merged most of the ethdev patches.
* GENEVE one is remaining, I guess that is for next release.
* Napatech PMD reviewed, will wait for new version.
* No other updates this week.
* next-net-intel
* Large ICE driver base code update under review.
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-baseband
* Some of the main series merged for RC1.
Working on remaining series.
* next-virtio
* Some series merged for RC1.
More patches need reviews and will go to rc2.
* next-crypto
* 54 patches (mainly to to test apps).
* Reviews needed on OpenSSL driver.
* Awaiting some updates as requested from submitters.
* main
* RC1 is out. Awaiting test.
* Highlights of 24.07-rc1:
- pointer compression library
- AMD Pensando ionic crypto driver
- UADK compress driver
- Marvell Odyssey ODM DMA driver
- more cleanups to prepare MSVC build
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.1 - Released.
* 22.11.5 - Released.
* 21.11.7 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13976 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-06-27
@ 2024-06-27 16:04 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-06-27 16:04 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2500 bytes --]
Release status meeting minutes 2024-06-27
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 14 June 2024
- PMD features freeze (-rc2): 5 July 2024
- Builtin applications features freeze (-rc3): 12 July 2024
- Release: 23 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* No other updates this week.
* next-net-intel
* Large ICE driver base code update under review.
* Some under patches under review.
* next-net-mlx
* No update.
* next-net-mvl
* PR sent and merged.
* next-eventdev
* PR sent and merged.
* next-baseband
* Some of the main series merged for RC1.
* Working on remaining series.
* next-virtio
* Some series merged for RC1.
* More patches need reviews and will go to rc2.
* next-crypto
* Majority of patches merged.
* OpenSSL patches reviewed and acked.
* main
* RC1 is out.
* Some test reports coming in.
* Discussion ongoing about replacing rte_memcpy with
standard memcpy.
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.2 - Released.
* 22.11.6 - Released.
* 21.11.8 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13410 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-07-04
@ 2024-07-09 13:40 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-07-09 13:40 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2358 bytes --]
Release status meeting minutes 2024-07-04
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 14 June 2024
- PMD features freeze (-rc2): 5 July 2024
- Builtin applications features freeze (-rc3): 12 July 2024
- Release: 23 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Still some work to do before RC2.
* next-net-intel
* Large ICE driver base code applied.
* 2 outstanding patches.
* next-net-mlx
* Mainly ready.
* next-net-mvl
* PR sent.
* next-eventdev
* PR sent.
* next-baseband
* PR sent.
* 1 more fix pending.
* next-virtio
* Some series merged.
* Preparing for RC2.
* next-crypto
* Majority of patches merged.
* Some reviews/acks required.
* main
* Merged build changes.
* Added some logging fixes and updates.
* RC2 in progress
LTS
---
Please add acks to confirm validation support for a 3 year LTS window:
http://inbox.dpdk.org/dev/20240117161804.223582-1-ktraynor@redhat.com/
* 23.11.2 - In progress.
* 22.11.6 - In progress.
* 21.11.8 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13169 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-07-18
@ 2024-07-18 9:18 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-07-18 9:18 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2705 bytes --]
Release status meeting minutes 2024-07-18
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 14 June 2024
- PMD features freeze (-rc2): 12 July 2024
- Builtin applications features freeze (-rc3): 22 July 2024
- Release: 30/31 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Looking at Napatech driver updates post-RC2.
* Adding some fixes.
* In this release there is a new driver from ZTE and two from Realtek.
* next-net-intel
* Main base code changes merged.
* Some other fix patches under review.
* next-net-mlx
* Merging some fixes and minor changes.
* next-net-mvl
* No update this week.
* next-eventdev
* No update this week.
* next-baseband
* No update this week.
* next-virtio
* No update this week.
* next-crypto
* Around 9 fix patches in Patchwork.
* main
* RC2 released 12 July.
* Looking at merging DTS patches and fixes.
* RC3 should close Monday 22 July
* RC4 should be Friday 26 July
* Release on 30/31 July
The following are the proposed dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 7 October 2024
- PMD features freeze (-rc2): 28 October 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023
LTS
---
Status of the current LTSes
* 23.11.2 - In progress.
* 22.11.6 - In progress.
* 21.11.8 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13995 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-07-25
@ 2024-07-25 9:00 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-07-25 9:00 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 3048 bytes --]
Release status meeting minutes 2024-07-25
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 14 June 2024
- PMD features freeze (-rc2): 12 July 2024
- Builtin applications features freeze (-rc3): 22 July 2024
- Release: 31 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* RC3 released.
* next-net-intel
* No post RC3 changes.
* next-net-mlx
* Crash in virtio with VDBA, under investigation.
* next-net-mvl
* No post RC3 changes.
* next-eventdev
* No post RC3 changes. 1 fix will go to next release.
* next-baseband
* No post RC3 changes.
* next-virtio
* 1 fix patch under investigation.
* next-crypto
* Issue reported in ipsec-gw. May need to be reverted.
https://inbox.dpdk.org/dev/7c690dcb-8824-452e-85d5-7f665ff56246@intel.com/
* main
* RC3 released 23 July.
* RC4 should be Monday 29 July
* Release on 30/31 July
* Please ack these and other deprecation notices:
https://patches.dpdk.org/project/dpdk/patch/20240221161319.7054-1-pbhagavatula@marvell.com/
https://patches.dpdk.org/project/dpdk/patch/20240722145324.1091-1-gmuthukrishn@marvell.com/
https://patches.dpdk.org/project/dpdk/patch/20240722145551.1159-1-gmuthukrishn@marvell.com/
https://patches.dpdk.org/project/dpdk/patch/20240723133706.2150828-1-asasidharan@marvell.com/
The following are the proposed dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 7 October 2024
- PMD features freeze (-rc2): 28 October 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023
LTS
---
Status of the current LTSes
* 23.11.2 - In progress.
* 22.11.6 - In progress.
* 21.11.8 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14801 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-08-22
@ 2024-08-22 9:54 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-08-22 9:54 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2664 bytes --]
Release status meeting minutes 2024-08-22
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.07:
- Proposal deadline (RFC/v1 patches): 26 April 2024
- API freeze (-rc1): 14 June 2024
- PMD features freeze (-rc2): 12 July 2024
- Builtin applications features freeze (-rc3): 22 July 2024
- Release: 31 July 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Not many patches yet.
* Ethdev patches from previous release.
* next-net-intel
* Nothing merged yet.
* next-net-mlx
* Not update.
* next-net-mvl
* Around 10 patches under review.
* next-eventdev
* Around 10 patches under review.
* next-baseband
* Some patches merged and some under review.
* next-virtio
* 2 series to post and some fixes.
* next-crypto
* 35+ patches in queue.
* Some new APIs and changes to APIs.
* main
* Closing out some patches from previous release.
* Looking at iavf driver.
* Patches starting to arrive.
* DPDK Summit Montreal 24-25, 2024
* https://events.linuxfoundation.org/dpdk-summit/
The following are the proposed dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 7 October 2024
- PMD features freeze (-rc2): 28 October 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023
LTS
---
Status of the current LTSes
* 23.11.2 - In progress.
* 22.11.6 - Released.
* 21.11.8 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13965 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-09-05
@ 2024-09-05 8:58 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-09-05 8:58 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]
Release status meeting minutes 2024-09-05
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 7 October 2024
- PMD features freeze (-rc2): 28 October 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Ethdev patches from previous release.
* next-net-intel
* Base code updates applied.
* ~30 patches so far.
* next-net-mlx
* In progress. ~10 patches in flight.
* next-net-mvl
* Around 20 patches under review.
* Will start merging after v1 deadline.
* next-eventdev
* Around 10 patches under review.
* Will start merging after v1 deadline.
* next-baseband
* Some patches merged and some under review.
* next-virtio
* 2 series to post and some fixes.
* next-crypto
* 60 patches in queue.
* Some new APIs and changes to APIs.
* next-dts
* Lots of patches. For framework and test suites.
* Merging will start soon.
* main
* Closing out some patches from previous release.
* Looking at iavf driver.
* Patches starting to arrive.
* DPDK Summit Montreal September 24-25, 2024
* https://events.linuxfoundation.org/dpdk-summit/
LTS
---
Status of the current LTSes
* 23.11.2 - Released.
* 22.11.6 - Released.
* 21.11.8 - RC will be sent this week.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13516 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-09-12
@ 2024-09-12 8:52 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-09-12 8:52 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2542 bytes --]
Release status meeting minutes 2024-09-12
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 7 October 2024
- PMD features freeze (-rc2): 28 October 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Ethdev patches from previous release.
* 2 New PMD: net/sxe, net/xsc
* 2 Updating: net/r8169, net/zxdh. Also Napatech: net/ntnic.
* next-net-intel
* Base code updates applied.
* Other base code and fixes in flight.
* next-net-mlx
* No updates this week.
* next-net-mvl
* Around 40 patches under review.
* next-eventdev
* Around 10 patches under review.
* next-baseband
* Some reviews this week. Progressing.
* next-virtio
* 1 VDP series to review.
* 2 new series posted and some fixes.
* next-crypto
* 60 patches in queue.
* Some new APIs and changes to APIs.
* next-dts
* Framework and test suites merged.
* main
* Big series cleaning up logs in drivers.
* DPDK Summit Montreal September 24-25, 2024
* https://events.linuxfoundation.org/dpdk-summit/
LTS
---
Status of the current LTSes
* 23.11.2 - Released.
* 22.11.6 - Released.
* 21.11.8 - RC sent. Testing in progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13451 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-09-19
@ 2024-09-19 9:00 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-09-19 9:00 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 3143 bytes --]
Release status meeting minutes 2024-09-19
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 7 October 2024
- PMD features freeze (-rc2): 28 October 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Ethdev patches from previous release.
* 2 New PMD: net/sxe, net/xsc
* 2 Updating: net/r8169, net/zxdh. Also Napatech: net/ntnic.
* next-net-intel
* 4 base code updates applied.
* Ready for merge.
* next-net-mlx
* No updates this week.
* next-net-mvl
* Around 40 patches under review.
* Merging has started.
* next-eventdev
* Around 10 patches under review.
* Merging has started.
* next-baseband
* Some patches queued.
* 2 series under review for merge.
* next-virtio
* 1 VDP series to review.
* 2 new series posted and some fixes.
* Some patches/series queued.
* next-crypto
* 60 patches in queue.
* Some PMD fixes merged.
* New PMD from ZTE for compression and crypto.
* Some new APIs and changes to APIs.
* The series on "cryptodev: replace LIST_END enumerators with APIs" needs review:
https://patches.dpdk.org/project/dpdk/patch/20240905101438.3888274-1-gakhil@marvell.com/
* next-dts
* Paul Szczepanek and Patrick Robb will be the new maintainers for DTS.
* Working through backlog.
* main
* Some series under review.
* Series on "VFIO hotplug with multiprocess" needs review.
https://patchwork.dpdk.org/project/dpdk/list/?series=33028
* Big series cleaning up logs in drivers.
* DPDK Summit Montreal September 24-25, 2024
* https://events.linuxfoundation.org/dpdk-summit/
* No Release Status meeting next week dues to summit.
LTS
---
Status of the current LTSes
* 23.11.2 - Released.
* 22.11.6 - Released.
* 21.11.8 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15177 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-10-03
@ 2024-10-03 10:43 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-10-03 10:43 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 3208 bytes --]
Release status meeting minutes 2024-10-03
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 7 October 2024 - Update: Friday 11 October
- PMD features freeze (-rc2): 28 October 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Working on Ethdev
- Some merged.
- Some patches from previous release.
- Some ethdev patches will be merged after RC1
* 2 New PMD: net/sxe, net/xsc - under review
* 2 Updating: net/r8169, net/zxdh. Also Napatech: net/ntnic.
* next-net-intel
* 4 base code updates applied.
* ~ 70 patches on tree
* Ready for merge.
* next-net-mlx
* No updates this week.
* next-net-mvl
* Around 40 patches under review.
* Some patches merged and some in progress.
* Will send PR next week
* next-eventdev
* Around 10 patches under review.
* Two specification changes from Intel and Marvell
* Merging has started.
* next-baseband
* Almost ready for PR
* 1 other series under review for merge.
* next-virtio
* Almost ready for PR
* Other patches can go in RC2
* next-crypto
* 60 patches in queue.
* Some PMD fixes merged.
* New PMD from ZTE for compression and crypto.
* Some new APIs and changes to APIs.
* The series on "cryptodev: replace LIST_END enumerators with APIs" needs review:
https://patches.dpdk.org/project/dpdk/patch/20240905101438.3888274-1-gakhil@marvell.com/
* next-dts
* Capabilities merged.
* Working through roadmap patches.
* main
* IPv6 patchset to review
* Series on "VFIO hotplug with multiprocess" needs review.
https://patchwork.dpdk.org/project/dpdk/list/?series=33028
* Big series cleaning up logs in drivers.
* RC1 will move to Friday 11 October
LTS
---
Status of the current LTSes
* 23.11.2 - Released.
* 22.11.6 - Released.
* 21.11.8 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 DST over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 15343 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-10-17
@ 2024-10-17 9:03 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-10-17 9:03 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2676 bytes --]
Release status meeting minutes 2024-10-17
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 18 October 2024
- PMD features freeze (-rc2): 28 October 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Most ethdev merged for RC1
* Most driver patches merged apart from new one which
will be merged post RC1
* 2 New PMD: net/sxe, net/xsc - under review
* 2 Updating: net/r8169, net/zxdh. Also Napatech: net/ntnic.
* Bonding needs a maintainer
* next-net-intel
* 4 base code updates applied.
* Tree pulled for RC1
* Some patchsets pending for RC2
* next-net-mlx
* No updates this week.
* next-net-mvl
* Merged for RC1.
* Some patches for RC2.
* next-eventdev
* Merged for RC1.
* Some patches for RC2.
* next-baseband
* No updates this week.
* next-virtio
* No updates this week.
* next-crypto
* No updates this week.
* next-dts
* Capabilities merged.
* ~10 other patches waiting for dependency to be merged.
* main
* Lots of patches merged ahead of RC1.
* RC1 targeted for Friday 18 October
**Note**:
We will look to move this meeting to a US friendly time slot at
the start of November.
LTS
---
Status of the current LTSes
* 23.11.2 - Released.
* 22.11.6 - Released.
* 21.11.8 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 DST over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14167 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-10-17
@ 2024-10-24 9:39 15% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-10-24 9:39 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 3015 bytes --]
Release status meeting minutes 2024-10-17
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 19 October 2024
- PMD features freeze (-rc2): 6 November 2024
- Builtin applications features freeze (-rc3): 4 November 2024
- Release: 18 November 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Most ethdev merged for RC1
* Most driver patches merged apart from new ones which
will be merged post RC1
* 2 New PMD: net/sxe, net/xsc - under review
* 2 Updating: net/r8169, net/zxdh. Also Napatech: net/ntnic.
* Bonding needs a maintainer
* next-net-intel
* 5 base code updates merged into RC1
* Some patchsets pending for RC2
* Fixed needed for Ubuntu build error:
https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Ubuntu_24.04/x86_64
* next-net-mlx
* 30 patches on list for RC2.
* next-net-mvl
* 15 patches in queue for RC2.
* next-eventdev
* 20 patches in queue for RC2.
* next-baseband
* Looking at series for ACC.
* next-virtio
* One series under review. Should be ready for merge this week.
* next-crypto
* Will target RC2 merge next week.
* next-dts
* Working on doc patch and large merge.
* main
* RC1 released on 19 October
* Please note: all subtree maintainers should rebase to RC1
due to some CI fixes.
* Thomas will be out of office next week, please merge to the
subtrees as much as possible this week.
* Power library needs review.
* RC2 targeting 6 November 2024
**Note**:
We will look to move this meeting to a US friendly time slot at
the start of November.
LTS
---
Status of the current LTSes
* 23.11.2 - Released.
* 22.11.6 - Released.
* 21.11.8 - Released.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 DST over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 14769 bytes --]
^ permalink raw reply [relevance 15%]
* DPDK Release Status Meeting 2024-11-14
@ 2024-11-14 10:04 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-11-14 10:04 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2641 bytes --]
Release status meeting minutes 2024-11-14
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the current/updated working dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 19 October 2024
- PMD features freeze (-rc2): 12 November 2024
- Builtin applications features freeze (-rc3): targeted for 19 November 2024
- Release: targeted for 29 November 2024
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* Napatech driver merged.
* Realtec driver merged.
* next-net-intel
* Some fixes to merge in RC3.
* next-net-mlx
* Some patches merged/planned for RC3.
* next-net-mvl
* Some bug fixes to merge in RC3. ~8 patches.
* next-eventdev
* 2 bug fixes to merge in RC3.
* next-baseband
* Ready for RC3/release.
* next-virtio
* Ready for RC3/release.
* next-crypto
* 3-4 fix patches to merge.
* ZTE driver deferred to next release.
* next-dts
* Pydantic series merged.
* main
* RC2 release on 12 November
* Added improved announcement support.
* Added Coverity fixes.
* Merging Broadcom branch.
* Merging DTS.
* RC3 targeted for 19 November 2024
* RC4 targeted for 26 November 2024
* Release targeted for 29 November 2024
**Note**:
We will look to move this meeting to a US friendly time slot at
the start of November.
LTS
---
Status of the current LTSes
* 23.11.3 - In progress.
* 22.11.7 - In progress.
* 21.11.9 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 DST over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13934 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-11-21
@ 2024-11-24 18:56 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-11-24 18:56 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2311 bytes --]
Release status meeting minutes 2024-11-21
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
Release Dates
-------------
The following are the current/updated working dates for 24.11:
- Proposal deadline (RFC/v1 patches): 7 September 2024
- API freeze (-rc1): 19 October 2024
- PMD features freeze (-rc2): 12 November 2024
- Builtin applications features freeze (-rc3): 20 November 2024
- Release: 29 November 2023
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* RC3 released.
* next-net-intel
* Most fixes merged in RC3.
* next-net-mlx
* Merged for RC3.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-baseband
* No update.
* next-virtio
* No update.
* next-crypto
* Merged for RC3.
* next-dts
* No merges past RC3 except for fixes.
* main
* Docs and minor fixes only for RC4.
* RC3 released on 20 November
* RC4 targeted for 26 November 2024
* Release targeted for 29 November 2024
**Note**:
We will look to move this meeting to a US friendly time slot at
the start of December.
LTS
---
Status of the current LTSes
* 23.11.3 - In progress.
* 22.11.7 - In progress.
* 21.11.9 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 DST over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13118 bytes --]
^ permalink raw reply [relevance 16%]
* DPDK Release Status Meeting 2024-11-28
@ 2024-11-28 11:53 16% Mcnamara, John
0 siblings, 0 replies; 140+ results
From: Mcnamara, John @ 2024-11-28 11:53 UTC (permalink / raw)
To: dev; +Cc: thomas, Marchand, David
[-- Attachment #1: Type: text/plain, Size: 2404 bytes --]
Release status meeting minutes 2024-11-28
=========================================
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-------------
The following are the proposed working dates for 25.03:
- Proposal deadline (RFC/v1 patches): 4 January 2025
- API freeze (-rc1): 7 February 2025
- PMD features freeze (-rc2): 28 February 2025
- Builtin applications features freeze (-rc3): 7 March 2025
- Release: 14 March 2025
https://core.dpdk.org/roadmap/#dates
Subtrees
--------
* next-net
* RC4 released.
* next-net-intel
* Some doc/fix patches for post RC4.
* next-net-mlx
* No update.
* next-net-mvl
* No update.
* next-eventdev
* No update.
* next-baseband
* Nothing beyond RC4.
* next-virtio
* 2 patches posted. 1 fix and 1 revert.
* next-crypto
* Nothing beyond RC4.
* next-dts
* Up to date in RC4.
* main
* RC4 release.
* Prepping for release.
* Release targeted for 29 November 2024
* The following are the proposed dates for DPDK 25.03:
V1: Jan 4
RC1: Feb 7
RC2: Feb 28
RC3: Mar 7
RC4: Mar 14
Rel: Mar 21
**Note**:
We will look to move this meeting to a US friendly time slot at
the start of December.
LTS
---
Status of the current LTSes
* 23.11.3 - In progress.
* 22.11.7 - In progress.
* 21.11.9 - In progress.
* 20.11.10 - Will only be updated with CVE and critical fixes.
* 19.11.15 - Will only be updated with CVE and critical fixes.
* Distros
* Debian 12 contains DPDK v22.11
* Ubuntu 24.04 contains DPDK v23.11
* Ubuntu 23.04 contains DPDK v22.11
* RHEL 8/9 contains DPDK 23.11
Defects
-------
* Bugzilla links, 'Bugs', added for hosted projects
* https://www.dpdk.org/hosted-projects/
DPDK Release Status Meetings
----------------------------
The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.
The meeting occurs on every Thursday at 9:30 DST over Jitsi on https://meet.jit.si/DPDK
You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.
[-- Attachment #2: Type: text/html, Size: 13889 bytes --]
^ permalink raw reply [relevance 16%]
Results 1-140 of 140 | reverse | sort options + mbox downloads above
-- links below jump to the message on this page --
2018-05-18 16:47 15% [dpdk-dev] DPDK Release Status Meeting 17/05/2018 Mcnamara, John
2018-05-24 16:29 15% [dpdk-dev] DPDK Release Status Meeting 24/05/2018 Mcnamara, John
2018-05-31 17:18 15% [dpdk-dev] DPDK Release Status Meeting 31/05/2018 Mcnamara, John
2018-06-13 20:43 15% [dpdk-dev] DPDK Release Status Meeting 06/07/2018 Mcnamara, John
2018-06-18 8:41 15% [dpdk-dev] DPDK Release Status Meeting 14/07/2018 Mcnamara, John
2018-06-22 12:13 15% [dpdk-dev] DPDK Release Status Meeting 21/07/2018 Mcnamara, John
2018-06-28 10:31 15% [dpdk-dev] DPDK Release Status Meeting 28/07/2018 Mcnamara, John
2018-07-26 10:52 15% [dpdk-dev] DPDK Release Status Meeting 26/07/2018 Mcnamara, John
2018-08-02 12:25 16% [dpdk-dev] DPDK Release Status Meeting 02/08/2018 Mcnamara, John
2019-01-25 9:24 14% [dpdk-dev] DPDK Release Status Meeting 24/01/2018 Mcnamara, John
2019-01-25 13:42 ` Jay Rolette
2019-01-25 21:16 ` Aaron Conole
2019-02-01 16:57 10% ` Mcnamara, John
2019-03-01 16:34 15% [dpdk-dev] DPDK Release Status Meeting 28/2/2019 Mcnamara, John
2019-03-28 12:03 [dpdk-dev] DPDK Release Status Meeting 28/3/2019 Ferruh Yigit
2019-03-28 12:48 ` David Marchand
2019-04-01 15:47 8% ` Mcnamara, John
2019-04-01 15:47 8% ` Mcnamara, John
2019-04-03 13:26 3% [dpdk-dev] [PATCH v1] doc: fix spelling errors reported by aspell John McNamara
2019-04-03 13:26 3% ` John McNamara
2019-04-26 15:14 3% [dpdk-dev] [PATCH v2 1/2] " John McNamara
2019-04-26 15:14 3% ` John McNamara
2019-05-23 11:46 14% [dpdk-dev] DPDK Release Status Meeting 23/5/2019 Mcnamara, John
2019-08-02 11:35 16% [dpdk-dev] DPDK Release Status Meeting 1/8/2019 Mcnamara, John
2019-11-28 20:54 15% [dpdk-dev] DPDK Release Status Meeting 28/11/2019 Mcnamara, John
2020-03-31 9:55 15% [dpdk-dev] DPDK Release Status Meeting 26/03/2020 Mcnamara, John
2020-06-17 15:34 15% [dpdk-dev] DPDK Release Status Meeting 11/06/2020 Mcnamara, John
2020-08-13 18:55 16% [dpdk-dev] DPDK Release Status Meeting 13/08/2020 Mcnamara, John
2021-03-18 19:36 15% [dpdk-dev] DPDK Release Status Meeting 18/03/2021 Mcnamara, John
2021-06-11 14:39 16% [dpdk-dev] DPDK Release Status Meeting 11/06/2021 Mcnamara, John
2021-06-18 16:03 15% [dpdk-dev] DPDK Release Status Meeting 17/06/2021 Mcnamara, John
2021-06-28 15:42 15% [dpdk-dev] DPDK Release Status Meeting 24/06/2021 Mcnamara, John
2021-07-01 16:30 15% [dpdk-dev] DPDK Release Status Meeting 01/07/2021 Mcnamara, John
2021-07-15 22:28 15% [dpdk-dev] DPDK Release Status Meeting 15/07/2021 Mcnamara, John
2021-09-03 16:31 16% [dpdk-dev] DPDK Release Status Meeting 2021-09-02 Mcnamara, John
2021-09-17 15:32 15% [dpdk-dev] DPDK Release Status Meeting 2021-09-16 Mcnamara, John
2021-09-30 19:38 15% [dpdk-dev] DPDK Release Status Meeting 2021-09-23 Mcnamara, John
2021-09-30 19:59 15% [dpdk-dev] DPDK Release Status Meeting 2021-09-30 Mcnamara, John
2021-10-27 15:53 15% [dpdk-dev] DPDK Release Status Meeting 2021-10-21 Mcnamara, John
2021-10-28 13:35 15% [dpdk-dev] DPDK Release Status Meeting 2021-10-28 Mcnamara, John
2021-11-05 7:49 16% [dpdk-dev] DPDK Release Status Meeting 2021-11-28 Mcnamara, John
2021-11-12 16:19 15% DPDK Release Status Meeting 2021-11-11 Mcnamara, John
2021-11-19 16:41 16% DPDK Release Status Meeting 2021-11-18 Mcnamara, John
2021-12-07 8:42 16% DPDK Release Status Meeting 2021-12-02 Mcnamara, John
2021-12-10 16:35 16% DPDK Release Status Meeting 2021-12-09 Mcnamara, John
2022-01-20 13:03 15% DPDK Release Status Meeting 2022-01-20 Mcnamara, John
2022-01-28 8:42 15% DPDK Release Status Meeting 2022-01-27 Mcnamara, John
2022-02-10 17:56 15% DPDK Release Status Meeting 2022-02-10 Mcnamara, John
2022-03-06 13:44 16% DPDK Release Status Meeting 2022-03-03 Mcnamara, John
2022-03-10 20:38 16% DPDK Release Status Meeting 2022-03-10 Mcnamara, John
2022-04-15 12:26 15% DPDK Release Status Meeting 2022-04-14 Mcnamara, John
2022-04-21 16:02 15% DPDK Release Status Meeting 2022-04-20 Mcnamara, John
2022-05-09 19:39 15% DPDK Release Status Meeting 2022-05-05 Mcnamara, John
2022-05-20 19:30 15% DPDK Release Status Meeting 2022-19-05 Mcnamara, John
2022-06-09 19:39 15% DPDK Release Status Meeting 2022-06-09 Mcnamara, John
2022-06-16 10:31 15% DPDK Release Status Meeting 2022-06-16 Mcnamara, John
2022-06-23 9:26 15% DPDK Release Status Meeting 2022-06-23 Mcnamara, John
2022-06-30 10:47 15% DPDK Release Status Meeting 2022-06-30 Mcnamara, John
2022-08-05 14:26 16% DPDK Release Status Meeting 2022-08-05 Mcnamara, John
2022-08-18 10:38 16% DPDK Release Status Meeting 2022-08-18 Mcnamara, John
2022-08-25 13:43 15% DPDK Release Status Meeting 2022-08-25 Mcnamara, John
2022-09-01 8:58 15% DPDK Release Status Meeting 2022-09-01 Mcnamara, John
2022-09-15 21:49 15% DPDK Release Status Meeting 2022-09-15 Mcnamara, John
2022-09-22 18:24 15% DPDK Release Status Meeting 2022-09-22 Mcnamara, John
2022-10-06 14:27 14% DPDK Release Status Meeting 2022-10-06 Mcnamara, John
2022-10-06 15:14 6% DPDK Deprecation Notice Review Meeting 2022-09-30 Mcnamara, John
2022-10-13 15:48 15% DPDK Release Status Meeting 2022-10-13 Mcnamara, John
2022-10-21 9:31 15% DPDK Release Status Meeting 2022-10-20 Mcnamara, John
2022-10-27 18:55 15% DPDK Release Status Meeting 2022-10-27 Mcnamara, John
2022-11-03 20:25 15% DPDK Release Status Meeting 2022-11-03 Mcnamara, John
2022-11-11 11:21 15% DPDK Release Status Meeting 2022-11-010 Mcnamara, John
2022-11-18 19:42 16% DPDK Release Status Meeting 2022-11-17 Mcnamara, John
2022-11-24 15:42 15% DPDK Release Status Meeting 2022-11-24 Mcnamara, John
2022-12-01 19:01 15% DPDK Release Status Meeting 2022-12-01 Mcnamara, John
2022-12-08 13:51 15% DPDK Release Status Meeting 2022-12-08 Mcnamara, John
2023-01-24 10:33 15% DPDK Release Status Meeting 2023-01-19 Mcnamara, John
2023-01-26 19:02 15% DPDK Release Status Meeting 2023-01-26 Mcnamara, John
2023-02-03 12:35 15% DPDK Release Status Meeting 2023-02-02 Mcnamara, John
2023-02-10 16:42 15% DPDK Release Status Meeting 2023-02-09 Mcnamara, John
2023-02-27 8:41 15% DPDK Release Status Meeting 2023-02-23 Mcnamara, John
2023-03-03 16:08 15% DPDK Release Status Meeting 2023-03-02 Mcnamara, John
2023-03-09 17:32 15% DPDK Release Status Meeting 2023-03-09 Mcnamara, John
2023-03-23 11:28 15% DPDK Release Status Meeting 2023-03-23 Mcnamara, John
2023-04-07 10:43 15% DPDK Release Status Meeting 2023-04-06 Mcnamara, John
2023-04-24 19:23 15% Mcnamara, John
2023-05-02 13:26 15% DPDK Release Status Meeting 2023-04-27 Mcnamara, John
2023-05-04 10:24 15% DPDK Release Status Meeting 2023-05-04 Mcnamara, John
2023-05-11 13:57 15% DPDK Release Status Meeting 2023-05-11 Mcnamara, John
2023-06-01 15:42 15% DPDK Release Status Meeting 2023-06-01 Mcnamara, John
2023-06-08 18:40 15% DPDK Release Status Meeting 2023-06-08 Mcnamara, John
2023-06-15 17:59 15% DPDK Release Status Meeting 2023-06-15 Mcnamara, John
2023-06-23 13:18 15% DPDK Release Status Meeting 2023-06-22 Mcnamara, John
2023-06-29 11:01 15% DPDK Release Status Meeting 2023-06-29 Mcnamara, John
2023-07-16 18:11 16% DPDK Release Status Meeting 2023-07-13 Mcnamara, John
2023-07-21 14:24 16% DPDK Release Status Meeting 2023-07-20 Mcnamara, John
2023-08-10 19:02 16% DPDK Release Status Meeting 2023-08-10 Mcnamara, John
2023-08-17 8:48 16% DPDK Release Status Meeting 2023-08-17 Mcnamara, John
2023-08-24 10:54 15% Mcnamara, John
2023-08-31 8:28 15% ` Mcnamara, John
2023-09-07 10:43 15% DPDK Release Status Meeting 2023-09-07 Mcnamara, John
2023-09-21 12:16 15% DPDK Release Status Meeting 2023-09-21 Mcnamara, John
2023-09-29 15:26 15% DPDK Release Status Meeting 2023-09-28 Mcnamara, John
2023-10-05 9:04 15% DPDK Release Status Meeting 2023-10-05 Mcnamara, John
2023-10-12 18:56 16% DPDK Release Status Meeting 2023-10-12 Mcnamara, John
2023-10-19 19:41 15% DPDK Release Status Meeting 2023-10-19 Mcnamara, John
2023-10-26 22:27 15% DPDK Release Status Meeting 2023-10-26 Mcnamara, John
2023-11-02 10:58 16% DPDK Release Status Meeting 2023-11-02 Mcnamara, John
2023-11-09 10:07 16% DPDK Release Status Meeting 2023-11-09 Mcnamara, John
2023-11-16 21:13 15% DPDK Release Status Meeting 2023-11-16 Mcnamara, John
2023-11-24 8:53 15% DPDK Release Status Meeting 2023-11-23 Mcnamara, John
2023-12-12 14:23 15% DPDK Release Status Meeting 2023-12-07 Mcnamara, John
2023-12-14 13:39 16% DPDK Release Status Meeting 2023-12-14 Mcnamara, John
2024-01-18 19:59 16% DPDK Release Status Meeting 2024-01-18 Mcnamara, John
2024-01-25 16:26 16% DPDK Release Status Meeting 2024-01-25 Mcnamara, John
2024-02-05 14:35 16% DPDK Release Status Meeting 2024-02-01 Mcnamara, John
2024-02-15 17:27 16% DPDK Release Status Meeting 2024-02-15 Mcnamara, John
2024-02-22 10:19 16% DPDK Release Status Meeting 2024-02-22 Mcnamara, John
2024-03-05 13:15 16% DPDK Release Status Meeting 2024-02-29 Mcnamara, John
2024-03-07 10:05 16% DPDK Release Status Meeting 2024-03-07 Mcnamara, John
2024-03-14 10:16 16% DPDK Release Status Meeting 2024-03-14 Mcnamara, John
2024-03-21 14:49 16% DPDK Release Status Meeting 2024-03-21 Mcnamara, John
2024-03-28 11:30 16% DPDK Release Status Meeting 2024-03-28 Mcnamara, John
2024-04-11 9:50 15% DPDK Release Status Meeting 2024-04-11 Mcnamara, John
2024-04-18 14:51 15% DPDK Release Status Meeting 2024-04-18 Mcnamara, John
2024-04-25 9:04 15% DPDK Release Status Meeting 2024-04-25 Mcnamara, John
2024-05-09 8:46 16% DPDK Release Status Meeting 2024-05-09 Mcnamara, John
2024-05-16 8:56 15% DPDK Release Status Meeting 2024-05-16 Mcnamara, John
2024-06-06 13:15 15% DPDK Release Status Meeting 2024-06-06 Mcnamara, John
2024-06-18 10:42 15% DPDK Release Status Meeting 2024-06-13 Mcnamara, John
2024-06-20 10:59 15% DPDK Release Status Meeting 2024-06-20 Mcnamara, John
2024-06-27 16:04 16% DPDK Release Status Meeting 2024-06-27 Mcnamara, John
2024-07-09 13:40 16% DPDK Release Status Meeting 2024-07-04 Mcnamara, John
2024-07-18 9:18 15% DPDK Release Status Meeting 2024-07-18 Mcnamara, John
2024-07-25 9:00 15% DPDK Release Status Meeting 2024-07-25 Mcnamara, John
2024-08-22 9:54 16% DPDK Release Status Meeting 2024-08-22 Mcnamara, John
2024-09-05 8:58 16% DPDK Release Status Meeting 2024-09-05 Mcnamara, John
2024-09-12 8:52 16% DPDK Release Status Meeting 2024-09-12 Mcnamara, John
2024-09-19 9:00 15% DPDK Release Status Meeting 2024-09-19 Mcnamara, John
2024-10-03 10:43 15% DPDK Release Status Meeting 2024-10-03 Mcnamara, John
2024-10-17 9:03 16% DPDK Release Status Meeting 2024-10-17 Mcnamara, John
2024-10-24 9:39 15% Mcnamara, John
2024-11-14 10:04 16% DPDK Release Status Meeting 2024-11-14 Mcnamara, John
2024-11-24 18:56 16% DPDK Release Status Meeting 2024-11-21 Mcnamara, John
2024-11-28 11:53 16% DPDK Release Status Meeting 2024-11-28 Mcnamara, John
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).