From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Serhii Iliushyk <sil-plv@napatech.com>, maobibo@loongson.cn
Subject: |WARNING| pw157991 [PATCH v1 1/1] doc: refactoring the guide for NTNIC PMD
Date: Thu, 23 Oct 2025 00:12:24 +0800 [thread overview]
Message-ID: <202510221612.59MGCOcA3509172@localhost.localdomain> (raw)
In-Reply-To: <20251022164015.507050-2-sil-plv@napatech.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/157991
_apply patch failure_
Submitter: Serhii Iliushyk <sil-plv@napatech.com>
Date: Wed, 22 Oct 2025 18:40:14 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 098fd1e446965570a7daba2e65e01c99faa0c43d
Apply patch set 157991 failed:
Checking patch doc/guides/nics/ntnic.rst...
error: while searching for:
Supported NICs
--------------
- NT200A02 2x100G SmartNIC
- FPGA ID 9563 (Inline Flow Management)
- NT400D11 2x100G SmartNIC
- FPGA ID 9569 (Inline Flow Management)
- NT400D13 2x100G SmartNIC
- FPGA ID 9574 (Inline Flow Management)
All information about NT200A02 and NT400D13 can be found by links below:
- https://www.napatech.com/products/nt200a02-smartnic-inline/
- https://www.napatech.com/products/nt400d11-smartnic-programmable/
- https://www.napatech.com/products/nt400d13-smartnic-programmable/
- https://www.napatech.com/support/resources/data-sheets/link-inline-software-for-napatech/
Features
--------
- FW version
- Speed capabilities
- Link status (Link update only)
- Unicast MAC filter
- Multicast MAC filter
- Promiscuous mode (Enable only. The device always run promiscuous mode)
- Flow API support.
- Support for multiple rte_flow groups.
- Multiple TX and RX queues.
- Scattered and gather for TX and RX.
- Jumbo frame support.
- Traffic mirroring.
- VLAN filtering.
- Packet modification: NAT, TTL decrement, DSCP tagging
- Tunnel types: GTP.
- Encapsulation and decapsulation of GTP data.
- RX VLAN stripping via raw decap.
- TX VLAN insertion via raw encap.
- CAM and TCAM based matching.
- Exact match of 140 million flows and policies.
- Tunnel HW offload: Packet type, inner/outer RSS, IP and UDP checksum verification.
- RSS hash
- RSS key update
- RSS based on VLAN or 5-tuple.
- RSS using different combinations of fields: L3 only, L4 only or both,
and source only, destination only or both.
- Several RSS hash keys, one for each flow type.
- Default RSS operation with no hash key specification.
- Port and queue statistics.
- RMON statistics in extended stats.
- Link state information.
- Flow statistics
- Flow aging support
- Flow metering, including meter policy API.
- Flow update. Update of the action list for specific flow
- Asynchronous flow support
- MTU update
Limitations
~~~~~~~~~~~
error: patch failed: doc/guides/nics/ntnic.rst:23
error: doc/guides/nics/ntnic.rst: patch does not apply
next parent reply other threads:[~2025-10-22 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251022164015.507050-2-sil-plv@napatech.com>
2025-10-22 16:12 ` qemudev [this message]
2025-10-22 16:41 ` |SUCCESS| " checkpatch
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=202510221612.59MGCOcA3509172@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=sil-plv@napatech.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).