DPDK patches and discussions
 help / color / mirror / Atom feed
From: Huisong Li <lihuisong@huawei.com>
To: <dev@dpdk.org>, <ferruh.yigit@amd.com>, <thomas@monjalon.net>,
	Marc Sune <marcdevel@gmail.com>
Cc: <liuyonglong@huawei.com>, <lihuisong@huawei.com>
Subject: [PATCH 01/16] doc: add features for link speeds
Date: Tue, 28 Nov 2023 21:00:05 +0800	[thread overview]
Message-ID: <20231128130021.42394-2-lihuisong@huawei.com> (raw)
In-Reply-To: <20231128130021.42394-1-lihuisong@huawei.com>

Add features for link speeds.

Fixes: 82113036e4e5 ("ethdev: redesign link speed config")
Cc: stable@dpdk.org

Signed-off-by: Huisong Li <lihuisong@huawei.com>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
---
 doc/guides/nics/features.rst         | 11 +++++++++++
 doc/guides/nics/features/default.ini |  1 +
 2 files changed, 12 insertions(+)

diff --git a/doc/guides/nics/features.rst b/doc/guides/nics/features.rst
index 1a1dc16c1e..f4285aba96 100644
--- a/doc/guides/nics/features.rst
+++ b/doc/guides/nics/features.rst
@@ -34,6 +34,17 @@ Supports getting the speed capabilities that the current device is capable of.
 * **[related]  API**: ``rte_eth_dev_info_get()``.
 
 
+.. _nic_features_link_speeds_config:
+
+Link speed configuration
+------------------------
+
+Supports configurating fixed speed and link autonegotiation.
+
+* **[uses]     user config**: ``dev_conf.link_speeds:RTE_ETH_LINK_SPEED_*``.
+* **[related]  API**: ``rte_eth_dev_configure()``.
+
+
 .. _nic_features_link_status:
 
 Link status
diff --git a/doc/guides/nics/features/default.ini b/doc/guides/nics/features/default.ini
index 806cb033ff..4de7d9765f 100644
--- a/doc/guides/nics/features/default.ini
+++ b/doc/guides/nics/features/default.ini
@@ -8,6 +8,7 @@
 ;
 [Features]
 Speed capabilities   =
+Link speed configuration =
 Link status          =
 Link status event    =
 Removal event        =
-- 
2.33.0


  reply	other threads:[~2023-11-28 13:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 13:00 [PATCH 00/16] add link speed configuration feature Huisong Li
2023-11-28 13:00 ` Huisong Li [this message]
2023-11-28 13:00 ` [PATCH 02/16] doc: add link speed configuration feature for i40e Huisong Li
2023-11-28 13:00 ` [PATCH 03/16] doc: add link speed configuration feature for bnxt Huisong Li
2023-11-28 13:00 ` [PATCH 04/16] doc: add link speed configuration feature for igc Huisong Li
2023-11-28 13:00 ` [PATCH 05/16] doc: add link speed configuration feature for ixgbe Huisong Li
2023-11-28 13:00 ` [PATCH 06/16] doc: add link speed configuration feature for atlantic Huisong Li
2023-11-28 13:00 ` [PATCH 07/16] doc: add link speed configuration feature for octeontx Huisong Li
2023-11-28 13:00 ` [PATCH 08/16] doc: add link speed configuration feature for hns3 Huisong Li
2023-11-28 13:00 ` [PATCH 09/16] doc: add link speed configuration feature for ngbe Huisong Li
2023-11-28 13:00 ` [PATCH 10/16] doc: add link speed configuration feature for txgbe Huisong Li
2023-11-28 13:00 ` [PATCH 11/16] doc: add link speed configuration feature for igb Huisong Li
2023-11-28 13:00 ` [PATCH 12/16] doc: add link speed configuration feature for thunderx Huisong Li
2023-11-28 13:00 ` [PATCH 13/16] doc: add link speed configuration feature for ice Huisong Li
2023-11-28 13:00 ` [PATCH 14/16] doc: add link speed configuration feature for ionic Huisong Li
2023-11-28 13:00 ` [PATCH 15/16] doc: add link speed configuration feature for dpaa Huisong Li
2023-11-29  7:57   ` Hemant Agrawal
2023-11-28 13:00 ` [PATCH 16/16] doc: add link speed configuration feature for sfc Huisong Li
2024-03-11 22:27 ` [PATCH 00/16] add link speed configuration feature 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=20231128130021.42394-2-lihuisong@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=liuyonglong@huawei.com \
    --cc=marcdevel@gmail.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).