From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw111579-111581 [PATCH] [v2, 4/4] ethdev: add meter color mark flow action
Date: Sun, 22 May 2022 07:09:25 -0400 (EDT) [thread overview]
Message-ID: <20220522110925.CBE4E6D4C2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3338 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/111579
_apply patch failure_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Sunday, May 22 2022 10:51:02
Applied on: CommitID:26d734b5d280b96f91f00f5e0c6c7eff99facef2
Apply patch set 111579-111581 failed:
Checking patch doc/guides/prog_guide/traffic_metering_and_policing.rst...
error: while searching for:
to the list of meter actions (``struct rte_mtr_meter_policy_params::actions``)
specified per color as show in :numref:`figure_rte_mtr_chaining`.
Protocol based input color selection
------------------------------------
error: patch failed: doc/guides/prog_guide/traffic_metering_and_policing.rst:107
Checking patch doc/guides/rel_notes/release_22_07.rst...
Hunk #1 succeeded at 64 (offset -9 lines).
Checking patch lib/ethdev/rte_flow.h...
Checking patch lib/ethdev/rte_mtr.c...
Checking patch lib/ethdev/rte_mtr.h...
Hunk #1 succeeded at 524 (offset -99 lines).
Hunk #2 succeeded at 600 (offset -99 lines).
Checking patch lib/ethdev/rte_mtr_driver.h...
Hunk #3 succeeded at 169 (offset -38 lines).
Checking patch lib/ethdev/version.map...
error: while searching for:
rte_mtr_color_in_protocol_priority_get;
rte_mtr_color_in_protocol_set;
rte_mtr_meter_vlan_table_update;
};
INTERNAL {
error: patch failed: lib/ethdev/version.map:285
Applying patch doc/guides/prog_guide/traffic_metering_and_policing.rst with 1 reject...
Rejected hunk #1.
Applied patch doc/guides/rel_notes/release_22_07.rst cleanly.
Applied patch lib/ethdev/rte_flow.h cleanly.
Applied patch lib/ethdev/rte_mtr.c cleanly.
Applied patch lib/ethdev/rte_mtr.h cleanly.
Applied patch lib/ethdev/rte_mtr_driver.h cleanly.
Applying patch lib/ethdev/version.map with 1 reject...
Rejected hunk #1.
diff a/doc/guides/prog_guide/traffic_metering_and_policing.rst b/doc/guides/prog_guide/traffic_metering_and_policing.rst (rejected hunks)
@@ -107,6 +107,13 @@ traffic meter and policing library.
to the list of meter actions (``struct rte_mtr_meter_policy_params::actions``)
specified per color as show in :numref:`figure_rte_mtr_chaining`.
+#. The ``rte_mtr_meter_profile_get()`` and ``rte_mtr_meter_policy_get()``
+ API functions are available for getting the object pointers directly.
+ These pointers allow quick access to profile/policy objects and are
+ required by the ``RTE_FLOW_ACTION_TYPE_METER_MARK`` action.
+ This action may omit the polciy definition to preovide a flexibility
+ to match a color later with the ``RTE_FLOW_ITEM_TYPE_METER_COLOR`` item.
+
Protocol based input color selection
------------------------------------
diff a/lib/ethdev/version.map b/lib/ethdev/version.map (rejected hunks)
@@ -285,6 +285,8 @@ EXPERIMENTAL {
rte_mtr_color_in_protocol_priority_get;
rte_mtr_color_in_protocol_set;
rte_mtr_meter_vlan_table_update;
+ rte_mtr_meter_profile_get;
+ rte_mtr_meter_policy_get;
};
INTERNAL {
Checking patch doc/guides/prog_guide/rte_flow.rst...
Checking patch doc/guides/rel_notes/release_22_07.rst...
error: doc/guides/rel_notes/release_22_07.rst: does not match index
Checking patch lib/ethdev/rte_flow.h...
error: lib/ethdev/rte_flow.h: does not match index
Applied patch doc/guides/prog_guide/rte_flow.rst cleanly.
https://lab.dpdk.org/results/dashboard/patchsets/22229/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-05-22 11:09 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=20220522110925.CBE4E6D4C2@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).