From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1571] Documentation of non root table
Date: Mon, 28 Oct 2024 15:18:54 +0000 [thread overview]
Message-ID: <bug-1571-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1571
Bug ID: 1571
Summary: Documentation of non root table
Product: DPDK
Version: 24.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: lucas@easy-way.app
Target Milestone: ---
Created attachment 294
--> https://bugs.dpdk.org/attachment.cgi?id=294&action=edit
Problem in DPDK Doc
Regarding MLX5 NIC Driver documentation:
Send to kernel action (RTE_FLOW_ACTION_TYPE_SEND_TO_KERNEL):
! Supported on non-root table.
! Supported in isolated mode.
! In HW steering (dv_flow_en = 2): - not supported on guest port.
What is non-root table ?
I later discovered that I should use RTE_FLOW_ACTION_TYPE_JUMP and later use
rte_flow_attr with the new group
I would like to request this update to the DPDK documentation, follow the link
below:
https://doc.dpdk.org/guides/nics/mlx5.html
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3198 bytes --]
reply other threads:[~2024-10-28 15:18 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=bug-1571-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).