| Message ID | 20220624072401.21839-1-lihuisong@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 mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C043EA0032; Fri, 24 Jun 2022 09:25:52 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 15019427EC; Fri, 24 Jun 2022 09:25:49 +0200 (CEST) Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by mails.dpdk.org (Postfix) with ESMTP id D1C9540A82 for <dev@dpdk.org>; Fri, 24 Jun 2022 09:25:46 +0200 (CEST) Received: from dggemv703-chm.china.huawei.com (unknown [172.30.72.57]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4LTpTx1X0vzSgvZ; Fri, 24 Jun 2022 15:22:13 +0800 (CST) Received: from kwepemm600004.china.huawei.com (7.193.23.242) by dggemv703-chm.china.huawei.com (10.3.19.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Fri, 24 Jun 2022 15:25:37 +0800 Received: from localhost.localdomain (10.69.192.56) by kwepemm600004.china.huawei.com (7.193.23.242) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Fri, 24 Jun 2022 15:25:36 +0800 From: Huisong Li <lihuisong@huawei.com> To: <aman.deep.singh@intel.com>, <yuying.zhang@intel.com>, <ferruh.yigit@xilinx.com>, <andrew.rybchenko@oktetlabs.ru> CC: <dev@dpdk.org>, <thomas@monjalon.net>, <huangdaode@huawei.com>, <liudongdong3@huawei.com>, <lihuisong@huawei.com> Subject: [PATCH V5 0/7] app/testpmd: fix RSS and flow type Date: Fri, 24 Jun 2022 15:23:54 +0800 Message-ID: <20220624072401.21839-1-lihuisong@huawei.com> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20220429102445.23711-1-lihuisong@huawei.com> References: <20220429102445.23711-1-lihuisong@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.69.192.56] X-ClientProxiedBy: dggems701-chm.china.huawei.com (10.3.19.178) To kwepemm600004.china.huawei.com (7.193.23.242) X-CFilter-Loop: Reflected X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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 |
| Series |
app/testpmd: fix RSS and flow type
|
|
Message
lihuisong (C)
June 24, 2022, 7:23 a.m. UTC
This patchset fix RSS related code and remove duplicated flow type to string table. --- v5: - resolve a warning in testpmd_funcs.rst file v4: - delete 'rss_offload_table[]' and use 'rss_type_table[]' - add an 'char_num_per_line' parameter to control RSS types display. - add 2/7, 3/7 and 6/7 patch. v3: - add 'rss_offload_table[]' to display supported RSS offload. - add patch 3/4 and 4/4. v2: - resovle compilation failure when disable i40e and ixgbe. Ferruh Yigit (2): app/testpmd: compact RSS types output in some commands app/testpmd: remove duplicated flow type to string table Huisong Li (5): app/testpmd: fix supported RSS offload display app/testpmd: unify the name of L2 payload offload app/testpmd: refactor config all RSS command app/testpmd: unify RSS types display app/testpmd: reorder elements in RSS type table array app/test-pmd/cmdline.c | 127 +++------- app/test-pmd/config.c | 263 +++++++++++++------- app/test-pmd/testpmd.h | 8 + doc/guides/testpmd_app_ug/testpmd_funcs.rst | 11 +- drivers/net/i40e/i40e_testpmd.c | 41 +-- 5 files changed, 228 insertions(+), 222 deletions(-)
Comments
Hi Ferruh, This patchset has been sent. However, a merge conflict is displayed on the CI. In fact, I'm do it based on the latest mainline, and there are nothing conflict. Can you help me re-trigger the build? Thanks, huisong 在 2022/6/24 15:23, Huisong Li 写道: > This patchset fix RSS related code and remove duplicated flow type to > string table. > > --- > v5: > - resolve a warning in testpmd_funcs.rst file > > v4: > - delete 'rss_offload_table[]' and use 'rss_type_table[]' > - add an 'char_num_per_line' parameter to control RSS types display. > - add 2/7, 3/7 and 6/7 patch. > > v3: > - add 'rss_offload_table[]' to display supported RSS offload. > - add patch 3/4 and 4/4. > > v2: > - resovle compilation failure when disable i40e and ixgbe. > > Ferruh Yigit (2): > app/testpmd: compact RSS types output in some commands > app/testpmd: remove duplicated flow type to string table > > Huisong Li (5): > app/testpmd: fix supported RSS offload display > app/testpmd: unify the name of L2 payload offload > app/testpmd: refactor config all RSS command > app/testpmd: unify RSS types display > app/testpmd: reorder elements in RSS type table array > > app/test-pmd/cmdline.c | 127 +++------- > app/test-pmd/config.c | 263 +++++++++++++------- > app/test-pmd/testpmd.h | 8 + > doc/guides/testpmd_app_ug/testpmd_funcs.rst | 11 +- > drivers/net/i40e/i40e_testpmd.c | 41 +-- > 5 files changed, 228 insertions(+), 222 deletions(-) >
On Fri, Jun 24, 2022 at 10:55 AM lihuisong (C) <lihuisong@huawei.com> wrote: > > Hi Ferruh, > > This patchset has been sent. However, a merge conflict is displayed on > the CI. > In fact, I'm do it based on the latest mainline, and there are nothing > conflict. > > Can you help me re-trigger the build? There may be different reasons why (likely on your side), but patchwork does not see the patches you sent as a single series. For example, patch 4 is seen as part of the v2 series. The CI tools rely on patchwork. So the various CI won't be able to apply them. Please resend.
Hi David, 在 2022/6/24 16:59, David Marchand 写道: > On Fri, Jun 24, 2022 at 10:55 AM lihuisong (C) <lihuisong@huawei.com> wrote: >> Hi Ferruh, >> >> This patchset has been sent. However, a merge conflict is displayed on >> the CI. >> In fact, I'm do it based on the latest mainline, and there are nothing >> conflict. >> >> Can you help me re-trigger the build? > There may be different reasons why (likely on your side), but > patchwork does not see the patches you sent as a single series. > For example, patch 4 is seen as part of the v2 series. > > The CI tools rely on patchwork. > So the various CI won't be able to apply them. > > Please resend. Thanks. It's the patchwork problem. This patchset are assigned to two series. As shown in the link below: http://patches.dpdk.org/project/dpdk/list/?series=&submitter=2085&state=&q=&archive=&delegate= If I resend, but this patchset hasn't changed. Do I need to change the version number of this patchset?
On 6/24/2022 10:54 AM, lihuisong (C) wrote: > CAUTION: This message has originated from an External Source. Please use > proper judgment and caution when opening attachments, clicking links, or > responding to this email. > > > Hi David, > > 在 2022/6/24 16:59, David Marchand 写道: >> On Fri, Jun 24, 2022 at 10:55 AM lihuisong (C) <lihuisong@huawei.com> >> wrote: >>> Hi Ferruh, >>> >>> This patchset has been sent. However, a merge conflict is displayed on >>> the CI. >>> In fact, I'm do it based on the latest mainline, and there are nothing >>> conflict. >>> >>> Can you help me re-trigger the build? >> There may be different reasons why (likely on your side), but >> patchwork does not see the patches you sent as a single series. >> For example, patch 4 is seen as part of the v2 series. >> >> The CI tools rely on patchwork. >> So the various CI won't be able to apply them. >> >> Please resend. > Thanks. It's the patchwork problem. This patchset are assigned to two > series. > As shown in the link below: > http://patches.dpdk.org/project/dpdk/list/?series=&submitter=2085&state=&q=&archive=&delegate= > > > If I resend, but this patchset hasn't changed. > Do I need to change the version number of this patchset? Hi Huisong, I think both are OK, but just to clarify which one is latest, I think there is no harm to increase the version.
在 2022/6/24 18:44, Ferruh Yigit 写道: > On 6/24/2022 10:54 AM, lihuisong (C) wrote: >> CAUTION: This message has originated from an External Source. Please >> use proper judgment and caution when opening attachments, clicking >> links, or responding to this email. >> >> >> Hi David, >> >> 在 2022/6/24 16:59, David Marchand 写道: >>> On Fri, Jun 24, 2022 at 10:55 AM lihuisong (C) >>> <lihuisong@huawei.com> wrote: >>>> Hi Ferruh, >>>> >>>> This patchset has been sent. However, a merge conflict is displayed on >>>> the CI. >>>> In fact, I'm do it based on the latest mainline, and there are nothing >>>> conflict. >>>> >>>> Can you help me re-trigger the build? >>> There may be different reasons why (likely on your side), but >>> patchwork does not see the patches you sent as a single series. >>> For example, patch 4 is seen as part of the v2 series. >>> >>> The CI tools rely on patchwork. >>> So the various CI won't be able to apply them. >>> >>> Please resend. >> Thanks. It's the patchwork problem. This patchset are assigned to two >> series. >> As shown in the link below: >> http://patches.dpdk.org/project/dpdk/list/?series=&submitter=2085&state=&q=&archive=&delegate= >> >> >> If I resend, but this patchset hasn't changed. >> Do I need to change the version number of this patchset? > > Hi Huisong, > > I think both are OK, but just to clarify which one is latest, I think > there is no harm to increase the version. Get it. V6 will be sent. > .
On 6/25/2022 2:09 AM, lihuisong (C) wrote: > > 在 2022/6/24 18:44, Ferruh Yigit 写道: >> On 6/24/2022 10:54 AM, lihuisong (C) wrote: >>> CAUTION: This message has originated from an External Source. Please >>> use proper judgment and caution when opening attachments, clicking >>> links, or responding to this email. >>> >>> >>> Hi David, >>> >>> 在 2022/6/24 16:59, David Marchand 写道: >>>> On Fri, Jun 24, 2022 at 10:55 AM lihuisong (C) >>>> <lihuisong@huawei.com> wrote: >>>>> Hi Ferruh, >>>>> >>>>> This patchset has been sent. However, a merge conflict is displayed on >>>>> the CI. >>>>> In fact, I'm do it based on the latest mainline, and there are nothing >>>>> conflict. >>>>> >>>>> Can you help me re-trigger the build? >>>> There may be different reasons why (likely on your side), but >>>> patchwork does not see the patches you sent as a single series. >>>> For example, patch 4 is seen as part of the v2 series. >>>> >>>> The CI tools rely on patchwork. >>>> So the various CI won't be able to apply them. >>>> >>>> Please resend. >>> Thanks. It's the patchwork problem. This patchset are assigned to two >>> series. >>> As shown in the link below: >>> http://patches.dpdk.org/project/dpdk/list/?series=&submitter=2085&state=&q=&archive=&delegate= >>> >>> >>> >>> If I resend, but this patchset hasn't changed. >>> Do I need to change the version number of this patchset? >> >> Hi Huisong, >> >> I think both are OK, but just to clarify which one is latest, I think >> there is no harm to increase the version. > Get it. V6 will be sent. Thank you.