From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: 贺鹏 <hepeng.0320@bytedance.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Matan Azrad" <matan@mellanox.com>
Subject: Re: [dpdk-dev] mlx5: the default rule makes VF rep cannot get packets
Date: Mon, 25 Nov 2019 07:32:08 +0000 [thread overview]
Message-ID: <AM4PR05MB3265C8C4239287889B6669D4D24A0@AM4PR05MB3265.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <0B649466-6BA1-4E28-A176-71C51CB7A00A@bytedance.com>
Hi,
What OFED version do you use? Or OOB kernel driver/rdma-core?
Target table (1 in the mentioned patch) is created on the flow creation as empty one.
The default rule for the empty ingress table in FDB (transfer attribute in testpmd command)
– go to vport 0 (to wire/VF representors), it is established by kernel/rdma-core, In your setup
it does not work.
With best regards, Slava
From: 贺鹏 <hepeng.0320@bytedance.com>
Sent: Monday, November 25, 2019 9:27
To: dev@dpdk.org; Matan Azrad <matan@mellanox.com>; Slava Ovsiienko <viacheslavo@mellanox.com>
Subject: mlx5: the default rule makes VF rep cannot get packets
Hi,
We found the patch "net/mlx5: revert default rules amount optimization",
which installs a rule directing all egress traffic from VF to table 1, results in
VF representors get no packets, even if there is no offload rules installed.
I’ve tested both l2fwd and ovs-dpdk. However, PF rep works just fine.
We are using dpdk 19.11-rc3 for evaluation.
next prev parent reply other threads:[~2019-11-25 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 7:27 贺鹏
2019-11-25 7:32 ` Slava Ovsiienko [this message]
2019-11-25 7:43 ` [dpdk-dev] [External] " 贺鹏
2019-11-25 8:28 ` Slava Ovsiienko
2019-11-25 8:32 ` 贺鹏
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=AM4PR05MB3265C8C4239287889B6669D4D24A0@AM4PR05MB3265.eurprd05.prod.outlook.com \
--to=viacheslavo@mellanox.com \
--cc=dev@dpdk.org \
--cc=hepeng.0320@bytedance.com \
--cc=matan@mellanox.com \
/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).