DPDK patches and discussions
 help / color / mirror / 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>,
	张永肃 <zhangyongsu@bytedance.com>,
	duanxiongchun@bytedance.com
Subject: Re: [dpdk-dev] [External] RE: mlx5: the default rule makes VF rep cannot get packets
Date: Mon, 25 Nov 2019 16:32:39 +0800	[thread overview]
Message-ID: <CF9BBDC8-9FDC-4D13-BAE0-F51A729D3307@bytedance.com> (raw)
In-Reply-To: <AM4PR05MB3265EA76BF78EEBACCDAE61AD24A0@AM4PR05MB3265.eurprd05.prod.outlook.com>

Hi,


I see.

I am going to try OFED 4.7 official version and see if it works. 

Thanks.

> 在 2019年11月25日,下午4:28,Slava Ovsiienko <viacheslavo@mellanox.com> 写道:
> 
> Hi,
>  
> please, see below.
>  
> From: 贺鹏 <hepeng.0320@bytedance.com <mailto:hepeng.0320@bytedance.com>> 
> Sent: Monday, November 25, 2019 9:44
> To: Slava Ovsiienko <viacheslavo@mellanox.com <mailto:viacheslavo@mellanox.com>>
> Cc: dev@dpdk.org <mailto:dev@dpdk.org>; Matan Azrad <matan@mellanox.com <mailto:matan@mellanox.com>>
> Subject: Re: [External] RE: mlx5: the default rule makes VF rep cannot get packets
>  
> Hi, 
> 在 2019年11月25日,下午3:32,Slava Ovsiienko <viacheslavo@mellanox.com <mailto: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 ?
>  
> I think so. If there is no any DPDK rule in Table 0, everything works OK, right?
> It means the default rule (hidden from DPDK) in table 0 works, and packets go to the vport 0
> (contains all representors). If we insert jump to table 1 – nothing works, it means the default
> rule in table 1 fails. This one is not established by DPDK, but by the driver.
>  
> With best regards, Slava
>  
>  
>  
> 
> 
> With best regards, Slava
>  
> From: 贺鹏 <hepeng.0320@bytedance.com <mailto:hepeng.0320@bytedance.com>> 
> Sent: Monday, November 25, 2019 9:27
> To: dev@dpdk.org <mailto:dev@dpdk.org>; Matan Azrad <matan@mellanox.com <mailto:matan@mellanox.com>>; Slava Ovsiienko <viacheslavo@mellanox.com <mailto: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	other threads:[~2019-11-25  8:32 UTC|newest]

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   ` [dpdk-dev] [External] " 贺鹏
2019-11-25  8:28     ` Slava Ovsiienko
2019-11-25  8:32       ` 贺鹏 [this message]

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=CF9BBDC8-9FDC-4D13-BAE0-F51A729D3307@bytedance.com \
    --to=hepeng.0320@bytedance.com \
    --cc=dev@dpdk.org \
    --cc=duanxiongchun@bytedance.com \
    --cc=matan@mellanox.com \
    --cc=viacheslavo@mellanox.com \
    --cc=zhangyongsu@bytedance.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).