From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 606] x540-AT2: Can not create rte_flow VF (Linux driver)
Date: Mon, 28 Dec 2020 08:17:54 +0000 [thread overview]
Message-ID: <bug-606-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=606
Bug ID: 606
Summary: x540-AT2: Can not create rte_flow VF (Linux driver)
Product: DPDK
Version: 18.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: eventdev
Assignee: dev@dpdk.org
Reporter: vanthanh2721997@gmail.com
Target Milestone: ---
Hi all,
I'm trying to direct a given flow directly to a VF's specific queue and my VF
unbind DPDK ( Linux Driver).
As a guide:
https://doc.dpdk.org/guides/sample_app_ug/flow_filtering.html
Bind DPDK driver:
./dpdk-devbind -b igb_uio 0000:04:00.1
Create VF:
echo 1 > /sys/bus/pci/devices/0000:04:00.1/max_vfs
Create action :
struct rte_flow_action_vf vf = {.id = 0};
action[0].type = RTE_FLOW_ACTION_TYPE_QUEUE;
action[0].conf = &queue;
action[1].type = RTE_FLOW_ACTION_TYPE_VF;
action[1].conf = &vf;
action[2].type = RTE_FLOW_ACTION_TYPE_END;
Results:
EAL: Detected 24 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL: probe driver:8086:1528 net_ixgbe.
:: initializing port: 0 done.
PMD: ether type anti-spoofing is not supported.
Flow can't be created 16 message: Not supported action
I have questions :
1. Can I use rte_flow to direct traffic to VF(Linux Driver) with PF(bind DPDK
driver)?
2. What is " ether type anti-spoofing is not supported "?
3. How to set-up rte_flow to direct to VF ?
Brgs,
thanhnv118
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-12-28 8:17 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-606-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).