DPDK patches and discussions
 help / color / Atom feed
From: 贺鹏 <hepeng.0320@bytedance.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Matan Azrad <matan@mellanox.com>
Subject: Re: [dpdk-dev] [External] RE: mlx5: the default rule makes VF rep cannot get packets
Date: Mon, 25 Nov 2019 15:43:35 +0800
Message-ID: <25D9FEAD-D712-40D9-9BB3-E88F1CA4794B@bytedance.com> (raw)
In-Reply-To: <AM4PR05MB3265C8C4239287889B6669D4D24A0@AM4PR05MB3265.eurprd05.prod.outlook.com>


> 在 2019年11月25日,下午3:32,Slava Ovsiienko <viacheslavo@mellanox.com> 写道:
> Hi,
> What OFED version do you use? Or OOB kernel driver/rdma-core?

OFED 4.6-3.11.

> 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.

The NIC works in switchdev mode; every VF has a representer, and dpdk is polling each rep to get packets. 
If I revert this patch, in the probe stage, DPDK will not install the default rule which directs packets to Table 1, and dpdk can get packets.

The target is to use dpdk as well as action offload together.  

The setup code is in the function  *mlx5_flow_create_esw_table_zero_flow*.
Even for running L2FWD, I cannot get a packet from VF rep.  You mean this is a driver problem ?

> 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.

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25  7:27 [dpdk-dev] " 贺鹏
2019-11-25  7:32 ` Slava Ovsiienko
2019-11-25  7:43   ` 贺鹏 [this message]
2019-11-25  8:28     ` [dpdk-dev] [External] " Slava Ovsiienko
2019-11-25  8:32       ` 贺鹏

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25D9FEAD-D712-40D9-9BB3-E88F1CA4794B@bytedance.com \
    --to=hepeng.0320@bytedance.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=viacheslavo@mellanox.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
	public-inbox-index dev

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox