From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Sunyang Wu <sunyang.wu@jaguarmicro.com>, maobibo@loongson.cn
Subject: |WARNING| pw159472 [PATCH] doc: update flow-perf.rst --query-rate option description
Date: Fri, 26 Dec 2025 10:05:21 +0800 [thread overview]
Message-ID: <202512260205.5BQ25LjR3407820@localhost.localdomain> (raw)
In-Reply-To: <20251226015057.49408-1-sunyang.wu@jaguarmicro.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/159472
_apply patch failure_
Submitter: Sunyang Wu <sunyang.wu@jaguarmicro.com>
Date: Fri, 26 Dec 2025 09:50:57 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: cd60dcd503b91956f966a1f6d595b35d256ac00f
Apply patch set 159472 failed:
Checking patch doc/guides/tools/flow-perf.rst...
error: while searching for:
* ``--query-rate``
Enable query rate calculations.
The application measures the rate of flow rule query operations.
After inserting the specified number of flow rules, the application
queries each rule sequentially and measures the total time taken.
The query rate is calculated as the number of query operations divided
by the total time.
Example usage with query rate calculation:
.. code-block:: console
sudo ./dpdk-test-flow_perf -a 08:00.0 -- --ingress --ether --ipv4 --queue --rules-count=100000 --query-rate
The query rate measurement follows the same window-based approach as
insertion and deletion rate measurements, using the window size
configured via --rules-batch.
* ``--dump-socket-mem``
Dump the memory stats for each socket before the insertion and after.
error: patch failed: doc/guides/tools/flow-perf.rst:89
error: doc/guides/tools/flow-perf.rst: patch does not apply
prev parent reply other threads:[~2025-12-26 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251226015057.49408-1-sunyang.wu@jaguarmicro.com>
2025-12-26 1:51 ` |SUCCESS| " checkpatch
2025-12-26 2:05 ` qemudev [this message]
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=202512260205.5BQ25LjR3407820@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=sunyang.wu@jaguarmicro.com \
--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).