From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Huisong Li <lihuisong@huawei.com>,
dev@dpdk.org, thomas@monjalon.net,
Jingjing Wu <jingjing.wu@intel.com>,
Beilei Xing <beilei.xing@intel.com>
Cc: liuyonglong@huawei.com
Subject: Re: [PATCH 02/11] doc: add Traffic Manager feature for iavf
Date: Tue, 28 Nov 2023 10:35:19 +0000 [thread overview]
Message-ID: <80c18c37-4080-4efd-83b3-27cf385cf36f@amd.com> (raw)
In-Reply-To: <20231128060934.2446-3-lihuisong@huawei.com>
On 11/28/2023 6:09 AM, Huisong Li wrote:
> Add Traffic Manager feature for iavf.
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---
> doc/guides/nics/features/iavf.ini | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/doc/guides/nics/features/iavf.ini b/doc/guides/nics/features/iavf.ini
> index db4f92ce71..385799c650 100644
> --- a/doc/guides/nics/features/iavf.ini
> +++ b/doc/guides/nics/features/iavf.ini
> @@ -35,6 +35,7 @@ Inner L4 checksum = Y
> Packet type parsing = Y
> Rx descriptor status = Y
> Tx descriptor status = Y
> +Traffic manager = Y
> Inline crypto = Y
> Basic stats = Y
> Multiprocess aware = Y
Can you please keep the order in the default.ini and other files same,
here 'Inline crypto' seems put into wrong order that is causing the
confusion,
but new fields seems need to go between 'VLAN filter' & 'CRC offload'.
next prev parent reply other threads:[~2023-11-28 10:35 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 6:09 [PATCH 00/11] add Traffic Manager feature Huisong Li
2023-11-28 6:09 ` [PATCH 01/11] doc: " Huisong Li
2023-11-28 10:32 ` Ferruh Yigit
2023-11-28 10:36 ` Hemant Agrawal
2023-11-28 10:54 ` Dumitrescu, Cristian
2023-11-28 6:09 ` [PATCH 02/11] doc: add Traffic Manager feature for iavf Huisong Li
2023-11-28 10:35 ` Ferruh Yigit [this message]
2023-11-28 11:33 ` lihuisong (C)
2023-11-28 11:47 ` lihuisong (C)
2023-11-28 11:55 ` Ferruh Yigit
2023-11-28 12:11 ` lihuisong (C)
2023-11-28 6:09 ` [PATCH 03/11] doc: add Traffic Manager feature for i40e Huisong Li
2023-11-28 6:09 ` [PATCH 04/11] doc: add Traffic Manager feature for ixgbe Huisong Li
2023-11-28 6:09 ` [PATCH 05/11] doc: add Traffic Manager feature for cnxk Huisong Li
2023-11-28 6:09 ` [PATCH 06/11] doc: add Traffic Manager feature for hns3 Huisong Li
2023-11-28 6:09 ` [PATCH 07/11] doc: add Traffic Manager feature for txgbe Huisong Li
2023-11-28 6:09 ` [PATCH 08/11] doc: add Traffic Manager feature for mvpp2 Huisong Li
2023-11-28 10:39 ` Ferruh Yigit
2023-11-28 11:34 ` lihuisong (C)
2023-11-28 6:09 ` [PATCH 09/11] doc: add Traffic Manager feature for dpaa2 Huisong Li
2023-11-28 10:36 ` Hemant Agrawal
2023-11-28 6:09 ` [PATCH 10/11] doc: add Traffic Manager feature for ipn3ke Huisong Li
2023-11-28 7:10 ` Xu, Rosen
2023-11-28 6:09 ` [PATCH 11/11] doc: add Traffic Manager feature for ice Huisong Li
2023-11-28 10:41 ` Ferruh Yigit
2023-11-28 11:35 ` lihuisong (C)
2023-11-28 12:40 ` [PATCH v2 00/11] add Traffic Manager feature Huisong Li
2023-11-28 12:40 ` [PATCH v2 01/11] doc: " Huisong Li
2023-11-28 12:40 ` [PATCH v2 02/11] doc: add Traffic Manager feature for iavf Huisong Li
2023-11-28 12:40 ` [PATCH v2 03/11] doc: add Traffic Manager feature for i40e Huisong Li
2023-11-28 12:40 ` [PATCH v2 04/11] doc: add Traffic Manager feature for ixgbe Huisong Li
2023-11-28 12:41 ` [PATCH v2 05/11] doc: add Traffic Manager feature for cnxk Huisong Li
2023-11-28 12:41 ` [PATCH v2 06/11] doc: add Traffic Manager feature for hns3 Huisong Li
2023-12-11 7:17 ` Jie Hai
2023-11-28 12:41 ` [PATCH v2 07/11] doc: add Traffic Manager feature for txgbe Huisong Li
2023-11-28 12:41 ` [PATCH v2 08/11] doc: add Traffic Manager feature for mvpp2 Huisong Li
2023-11-28 12:41 ` [PATCH v2 09/11] doc: add Traffic Manager feature for dpaa2 Huisong Li
2023-11-28 12:41 ` [PATCH v2 10/11] doc: add Traffic Manager feature for ipn3ke Huisong Li
2023-11-28 12:41 ` [PATCH v2 11/11] doc: add Traffic Manager feature for ice Huisong Li
2023-12-11 3:25 ` [PATCH v2 00/11] add Traffic Manager feature lihuisong (C)
2024-01-11 6:36 ` lihuisong (C)
2024-02-19 2:52 ` lihuisong (C)
2024-03-11 17:33 ` 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=80c18c37-4080-4efd-83b3-27cf385cf36f@amd.com \
--to=ferruh.yigit@amd.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=thomas@monjalon.net \
/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).