From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw117383 [PATCH] doc: clarify deprecation status for flow actions PF and VF
Date: Wed, 5 Oct 2022 07:49:43 -0400 (EDT) [thread overview]
Message-ID: <20221005114943.5661D6D509@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/117383
_apply patch failure_
Submitter: Ivan Malov <Ivan.Malov@oktetlabs.ru>
Date: Wednesday, October 05 2022 11:32:21
Applied on: CommitID:d5262b521d096349e9e96b436f90eee6554ba595
Apply patch set 117383 failed:
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
will be limited to maximum 256 queues.
Also compile time flag ``RTE_ETHDEV_QUEUE_STAT_CNTRS`` will be removed.
* 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.
* ethdev: Actions ``OF_DEC_NW_TTL``, ``SET_IPV4_SRC``, ``SET_IPV4_DST``,
``SET_IPV6_SRC``, ``SET_IPV6_DST``, ``SET_TP_SRC``, ``SET_TP_DST``,
error: patch failed: doc/guides/rel_notes/deprecation.rst:83
Applying patch doc/guides/rel_notes/deprecation.rst with 1 reject...
Rejected hunk #1.
diff a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst (rejected hunks)
@@ -83,8 +83,13 @@ Deprecation Notices
will be limited to maximum 256 queues.
Also compile time flag ``RTE_ETHDEV_QUEUE_STAT_CNTRS`` will be removed.
-* 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.
+* ethdev: Flow actions ``PF`` and ``VF`` have been deprecated since DPDK 21.11
+ and are yet to be removed. That still has not happened because there are net
+ drivers which support combined use of either action ``PF`` or action ``VF``
+ with action ``QUEUE``, namely, i40e, ixgbe and txgbe (L2 tunnel rule).
+ It is unclear whether it is acceptable to just drop support for
+ such a complex use case, so maintainers of the said drivers
+ should take a closer look at this and provide assistance.
* ethdev: Actions ``OF_DEC_NW_TTL``, ``SET_IPV4_SRC``, ``SET_IPV4_DST``,
``SET_IPV6_SRC``, ``SET_IPV6_DST``, ``SET_TP_SRC``, ``SET_TP_DST``,
https://lab.dpdk.org/results/dashboard/patchsets/23780/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-10-05 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221005114943.5661D6D509@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).