From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
Lijun Ou <oulijun@huawei.com>,
"Ye, Xiaolong" <xiaolong.ye@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"linuxarm@huawei.com" <linuxarm@huawei.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: configure rxd and txd number correctly
Date: Tue, 21 Apr 2020 18:24:50 +0100 [thread overview]
Message-ID: <d672e212-d888-0ff9-87ff-b4c400b9f8df@intel.com> (raw)
In-Reply-To: <DM6PR11MB2537E6AD673C9A9CB03570CBEFD50@DM6PR11MB2537.namprd11.prod.outlook.com>
On 4/21/2020 12:50 PM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Lijun Ou
>> Sent: Saturday, April 18, 2020 4:45 AM
>> To: Ye, Xiaolong <xiaolong.ye@intel.com>; Zhang, Qi Z
>> <qi.z.zhang@intel.com>
>> Cc: dev@dpdk.org; linuxarm@huawei.com
>> Subject: [dpdk-dev] [PATCH v2] app/testpmd: configure rxd and txd number
>> correctly
>>
>> When users configure rxds and txds by used port config cmd based on
>> testpmd application, it will not be able to configure rxd and txd according to
>> the max capability range supported by the actual NIC hardware. Due testpmd
>> defects, it can only configure a fixed range to 0 to 2048.
>> The final result is that an incorrect printing prompt appears and cannot be
>> applied using rxd && txd according to the actual capabilities supported by the
>> device.
>> In order to solve the above problems, we modify the testpmd. First by calling
>> the rte_eth_dev_info_get api to obtain the max and min rx/tx capability
>> supported by the hns3, and then use this range to compare with the actual
>> value by users configured and make reasonable limitation.
>>
>> Signed-off-by: Lijun Ou <oulijun@huawei.com>
>> Signed-off-by: Huisong Li <lihuisong@huawei.com>
>> Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com>
>
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-04-21 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 3:44 Lijun Ou
2020-04-21 11:50 ` Iremonger, Bernard
2020-04-21 17:24 ` Ferruh Yigit [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=d672e212-d888-0ff9-87ff-b4c400b9f8df@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=linuxarm@huawei.com \
--cc=oulijun@huawei.com \
--cc=qi.z.zhang@intel.com \
--cc=xiaolong.ye@intel.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).