From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Damodharam Ammepalli <damodharam.ammepalli@broadcom.com>,
dev@dpdk.org, huangdengdui@huawei.com,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH v6 1/2] ethdev: Add link_speed lanes support
Date: Fri, 27 Sep 2024 10:20:57 -0700 [thread overview]
Message-ID: <CACZ4nhupHSx-dY+iK3QsRHs84Y2Yst+CALqyWke9H+9nOLW3SQ@mail.gmail.com> (raw)
In-Reply-To: <de5c5858-ac0e-4963-8f37-6747b763f85c@amd.com>
[-- Attachment #1: Type: text/plain, Size: 2570 bytes --]
On Thu, Sep 26, 2024 at 5:39 PM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
>
> On 9/26/2024 10:43 PM, Damodharam Ammepalli wrote:
> > Update the eth_dev_ops structure with new function vectors
> > to get, get capabilities and set ethernet link speed lanes.
> > Update the testpmd to provide required config and information
> > display infrastructure.
> >
> > The supporting ethernet controller driver will register callbacks
> > to avail link speed lanes config and get services. This lanes
> > configuration is applicable only when the nic is forced to fixed
> > speeds. In Autonegiation mode, the hardware automatically
> > negotiates the number of lanes.
> >
> > These are the new commands.
> >
> > testpmd> show port 0 speed_lanes capabilities
> >
> > Supported speeds Valid lanes
> > -----------------------------------
> > 10 Gbps 1
> > 25 Gbps 1
> > 40 Gbps 4
> > 50 Gbps 1 2
> > 100 Gbps 1 2 4
> > 200 Gbps 2 4
> > 400 Gbps 4 8
> > testpmd>
> >
> > testpmd>
> > testpmd> port stop 0
> > testpmd> port config 0 speed_lanes 4
> > testpmd> port config 0 speed 200000 duplex full
> > testpmd> port start 0
> > testpmd>
> > testpmd> show port info 0
> >
> > ********************* Infos for port 0 *********************
> > MAC address: 14:23:F2:C3:BA:D2
> > Device name: 0000:b1:00.0
> > Driver name: net_bnxt
> > Firmware-version: 228.9.115.0
> > Connect to socket: 2
> > memory allocation on the socket: 2
> > Link status: up
> > Link speed: 200 Gbps
> > Active Lanes: 4
> > Link duplex: full-duplex
> > Autoneg status: Off
> >
> > Signed-off-by: Damodharam Ammepalli <damodharam.ammepalli@broadcom.com>
> >
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@amd.com>
Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>
> Suggested patch title:
> ethdev: support link speed lanes
>
> <...>
>
> > +/**
> > + * @warning
> > + * @b EXPERIMENTAL: this API may change, or be removed, without prior notice
> > + *
> > + * Get Active lanes.
> > + *
> > + * @param port_id
> > + * The port identifier of the Ethernet device.
> > + * @param lanes
> > + * Driver updates lanes with the number of active lanes.
> > + * On a supported NIC on link up, lanes will be a non-zero value irrespective whether the
> > + * link is Autonegotiated or Fixed speed. No information is dispalyed for error.
> >
>
> s/dispalyed/displayed/
>
> I can fix while merging
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
next prev parent reply other threads:[~2024-09-27 17:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 17:50 [PATCH v5 0/2] " Damodharam Ammepalli
2024-09-04 17:50 ` [PATCH v5 1/2] ethdev: " Damodharam Ammepalli
2024-09-22 17:02 ` Ferruh Yigit
2024-09-24 22:59 ` Damodharam Ammepalli
2024-09-25 15:00 ` Damodharam Ammepalli
2024-09-25 21:35 ` Ferruh Yigit
2024-09-26 21:43 ` [PATCH v6 0/2] " Damodharam Ammepalli
2024-09-26 21:43 ` [PATCH v6 1/2] ethdev: " Damodharam Ammepalli
2024-09-27 0:39 ` Ferruh Yigit
2024-09-27 17:20 ` Ajit Khaparde [this message]
2024-09-26 21:43 ` [PATCH v6 2/2] net/bnxt: code refactor for supporting speed lanes Damodharam Ammepalli
2024-09-27 17:17 ` Ajit Khaparde
2024-09-27 0:41 ` [PATCH v6 0/2] Add link_speed lanes support Ferruh Yigit
2024-09-27 22:23 ` Ferruh Yigit
2024-09-25 21:35 ` [PATCH v5 1/2] ethdev: " Ferruh Yigit
2024-09-04 17:50 ` [PATCH v5 2/2] net/bnxt: code refactor for supporting speed lanes Damodharam Ammepalli
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=CACZ4nhupHSx-dY+iK3QsRHs84Y2Yst+CALqyWke9H+9nOLW3SQ@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=damodharam.ammepalli@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=huangdengdui@huawei.com \
--cc=kalesh-anakkur.purayil@broadcom.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).