Message ID | cover.1606136884.git.zhouguoyang@huawei.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7F735A04B1; Mon, 23 Nov 2020 14:09:01 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CF1AA37AF; Mon, 23 Nov 2020 14:08:59 +0100 (CET) Received: from szxga06-in.huawei.com (szxga06-in.huawei.com [45.249.212.32]) by dpdk.org (Postfix) with ESMTP id 41DD737AF for <dev@dpdk.org>; Mon, 23 Nov 2020 14:08:58 +0100 (CET) Received: from DGGEMS410-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga06-in.huawei.com (SkyGuard) with ESMTP id 4CfnXT2MfVzhgVR; Mon, 23 Nov 2020 21:08:41 +0800 (CST) Received: from tester.localdomain (10.175.119.39) by DGGEMS410-HUB.china.huawei.com (10.3.19.210) with Microsoft SMTP Server id 14.3.487.0; Mon, 23 Nov 2020 21:08:45 +0800 From: Guoyang Zhou <zhouguoyang@huawei.com> To: <dev@dpdk.org> CC: <ferruh.yigit@intel.com>, <bluca@debian.org>, <cloud.wangxiaoyun@huawei.com>, <luoxianjun@huawei.com>, <yin.yinshi@huawei.com>, <luojiachen@huawei.com>, <zhouguoyang@huawei.com>, <chenlizhong@huawei.com>, <zhaohui8@huawei.com>, <chenchanghu@huawei.com> Date: Mon, 23 Nov 2020 21:12:44 +0800 Message-ID: <cover.1606136884.git.zhouguoyang@huawei.com> X-Mailer: git-send-email 1.8.3.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.175.119.39] X-CFilter-Loop: Reflected Subject: [dpdk-dev] [PATCH v1 0/2] remove some limitations and operations X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Series |
remove some limitations and operations
|
|
Message
Guoyang Zhou
Nov. 23, 2020, 1:12 p.m. UTC
The maximum number of queues on the chip can be any value greater than 0, it does not have to be the power of two, and remove the operation of optical modules in the link function. -- v1: - remove the limitation for max queue num - remove the operation of optical modules in the link function Guoyang Zhou (2): net/hinic/base: remove the limitation for max queue num net/hinic: remove the operation of optical modules drivers/net/hinic/base/hinic_pmd_niccfg.c | 38 ------------------------------- drivers/net/hinic/base/hinic_pmd_niccfg.h | 2 -- drivers/net/hinic/base/hinic_pmd_nicio.c | 5 ---- drivers/net/hinic/hinic_pmd_ethdev.c | 14 ------------ 4 files changed, 59 deletions(-)
Comments
On 11/23/2020 1:12 PM, Guoyang Zhou wrote: > The maximum number of queues on the chip can be any value greater > than 0, it does not have to be the power of two, and remove the > operation of optical modules in the link function. > > -- > v1: > - remove the limitation for max queue num > - remove the operation of optical modules in the link function > > Guoyang Zhou (2): > net/hinic/base: remove the limitation for max queue num > net/hinic: remove the operation of optical modules > Hi Guoyang, How critical is this set, can you please describe the impact of the fixes? If they are not critical, let's postpone them to next release, since the release is a few days away. btw, both patches has [1] as a fixed patch, but that patch looks unrelated with both, that patch only cleans up the uninit/destroy path. Can you please elaborate why that patch is fixed? As far as I can see the condition removed in first patch introduced in v19.08 ([2]) and the calls in second patch added in v19.11 ([3]). [1] Fixes: 511b7371d32b ("net/hinic: fix hugepage memory leaks") [2] Fixes: 828d3e15a9dc ("net/hinic/base: support context and work queue") [3] Fixes: 54ac33869932 ("net/hinic: set link down and up")
On 11/23/2020 4:09 PM, Ferruh Yigit wrote: > On 11/23/2020 1:12 PM, Guoyang Zhou wrote: >> The maximum number of queues on the chip can be any value greater >> than 0, it does not have to be the power of two, and remove the >> operation of optical modules in the link function. >> >> -- >> v1: >> - remove the limitation for max queue num >> - remove the operation of optical modules in the link function >> >> Guoyang Zhou (2): >> net/hinic/base: remove the limitation for max queue num >> net/hinic: remove the operation of optical modules >> > > Hi Guoyang, > > How critical is this set, can you please describe the impact of the fixes? > > If they are not critical, let's postpone them to next release, since the release > is a few days away. > Hi Guoyang, I can see that a v2 has been sent but it is still not clear if you are OK to defer the patches, can you please share your thoughts on it? Thanks, ferruh > btw, both patches has [1] as a fixed patch, but that patch looks unrelated with > both, that patch only cleans up the uninit/destroy path. > Can you please elaborate why that patch is fixed? > > As far as I can see the condition removed in first patch introduced in v19.08 > ([2]) and the calls in second patch added in v19.11 ([3]). > > > > [1] > Fixes: 511b7371d32b ("net/hinic: fix hugepage memory leaks") > > > [2] > Fixes: 828d3e15a9dc ("net/hinic/base: support context and work queue") > > [3] > Fixes: 54ac33869932 ("net/hinic: set link down and up")
Hi ferruh, I hope that these two patches can be applied. Because in that way, the version can be stable. Thanks, Guoyang zhou 在 2020/11/24 17:31, Ferruh Yigit 写道: > On 11/23/2020 4:09 PM, Ferruh Yigit wrote: >> On 11/23/2020 1:12 PM, Guoyang Zhou wrote: >>> The maximum number of queues on the chip can be any value greater >>> than 0, it does not have to be the power of two, and remove the >>> operation of optical modules in the link function. >>> >>> -- >>> v1: >>> - remove the limitation for max queue num >>> - remove the operation of optical modules in the link function >>> >>> Guoyang Zhou (2): >>> net/hinic/base: remove the limitation for max queue num >>> net/hinic: remove the operation of optical modules >>> >> >> Hi Guoyang, >> >> How critical is this set, can you please describe the impact of the fixes? >> >> If they are not critical, let's postpone them to next release, since the release >> is a few days away. >> > > Hi Guoyang, > > I can see that a v2 has been sent but it is still not clear if you are OK to > defer the patches, can you please share your thoughts on it? > > Thanks, > ferruh > >> btw, both patches has [1] as a fixed patch, but that patch looks unrelated with >> both, that patch only cleans up the uninit/destroy path. >> Can you please elaborate why that patch is fixed? >> >> As far as I can see the condition removed in first patch introduced in v19.08 >> ([2]) and the calls in second patch added in v19.11 ([3]). >> >> >> >> [1] >> Fixes: 511b7371d32b ("net/hinic: fix hugepage memory leaks") >> >> >> [2] >> Fixes: 828d3e15a9dc ("net/hinic/base: support context and work queue") >> >> [3] >> Fixes: 54ac33869932 ("net/hinic: set link down and up") >