From: Yao chuhong <ych@panath.cn>
To: "Ferruh Yigit" <ferruh.yigit@intel.com>,
"shijith.thotton" <shijith.thotton@cavium.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/liquidio fixes unable to update linfovar
Date: Wed, 23 May 2018 08:16:49 +0800 [thread overview]
Message-ID: <tencent_4058F2C95F6A30DE1F812D4F@qq.com> (raw)
In-Reply-To: <55b76479-703a-fc2b-4e05-c4f3fd24e217@intel.com>
hi, Ferruh & Shijith
Sorry, I can't reply the email in time, because it was late at night.
I read your email, Will use commit log suggested by Shijith and the patch Applied to dpdk-next-net/master.
That means my contribution to this bug has been done, right?
Thanks again for your help. Thanks!
------------------ Original ------------------
From: "Ferruh Yigit"<ferruh.yigit@intel.com>;
Date: Wed, May 23, 2018 05:12 AM
To: "chuhong yao"<ych@panath.cn>; "shijith.thotton"<shijith.thotton@cavium.com>;
Cc: "dev"<dev@dpdk.org>;
Subject: Re: [dpdk-dev] [PATCH v2] net/liquidio fixes unable to update linfovar
On 5/22/2018 10:07 PM, Ferruh Yigit wrote:
> On 5/22/2018 3:33 PM, chuhong yao wrote:
>> When I was using VPP +dpdk-18.02+liqudio CN23xx,
>> I encountered such a bug.
>> When VPP called dpdk_device_start to initialize DPDK liqudio drive,
>> I found that initialization failed.
>> The reason for the failure is that VF MTU > PF MTU,
>> but PF MTU has been modified to 9600 (> VF MTU).
>> Finally, I am location that DPDK liqudio drive
>> cannot get the correct PF driver to liqudio network card.
>> It is due to the fact that when VPP calls dpdk_device_start to
>> initialize DPDK liqudio drive,this time,
>> lio_dev->linfo.Link var already exists in the old value, not empty.
>> Cause lio_dev->linfo.Link. Link_status64 != 0
>> statement is set up,
>> and the link info is stopped directly to liqudio card,
>> resulting in no get accurate pf mtu.
>> I did a test model to reproduce the bug,
>> which is to add rte_eth_dev_set_mtu(portid, vf_mtu)
>> to the rte_eth_dev_start function when using
>> dpdk-18.02+liqudio CN23xx+l2fwd.
>> You need to make sure that 1500 < vf_mtu < pf_mtu will be available.
>> At this time, you will have
>> net_liovf[04:00.3]ERROR: lio_dev_mtu_set()
>> VF MTU should be >= 68 and <= 1500. Such a mistake.
>>
>> Signed-off-by: chuhong yao <ych@panath.cn>
>
> Will use commit log suggested by maintainer [1]. Thanks Shijith!
>
>
> [1]
> net/liquidio: fix link state fetching during device start
>
> Clear link state information during device start for fetching new state
> before function completion.
>
> Fixes: 605164c8e79d ("net/liquidio: add API to validate VF MTU")
> Cc: stable@dpdk.org
>
> Signed-off-by: Chuhong Yao <ych@panath.cn>
> Acked-by: Shijith Thotton <shijith.thotton@caviumnetworks.com>
Applied to dpdk-next-net/master, thanks.
搜索
复制
next prev parent reply other threads:[~2018-05-23 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 14:33 [dpdk-dev] [PATCH v2] net/liquidio fixes unable to update linfo var chuhong yao
2018-05-22 21:07 ` Ferruh Yigit
2018-05-22 21:12 ` Ferruh Yigit
2018-05-23 0:16 ` Yao chuhong [this message]
2018-05-23 9:01 ` [dpdk-dev] [PATCH v2] net/liquidio fixes unable to update linfovar Ferruh Yigit
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=tencent_4058F2C95F6A30DE1F812D4F@qq.com \
--to=ych@panath.cn \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=shijith.thotton@cavium.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).