Skip to content

[Nexthop] Enable msi and napi on NH-5010#26206

Open
roy-nexthop wants to merge 3 commits intosonic-net:masterfrom
nexthop-ai:nh-5010-msi-napi
Open

[Nexthop] Enable msi and napi on NH-5010#26206
roy-nexthop wants to merge 3 commits intosonic-net:masterfrom
nexthop-ai:nh-5010-msi-napi

Conversation

@roy-nexthop
Copy link
Contributor

@roy-nexthop roy-nexthop commented Mar 16, 2026

Why I did it

Set use_napi=1 and usemsi=1 on NH-5010 for improved performance of CPU handled traffic.

Work item tracking
  • Microsoft ADO (number only):

How I did it

  • Allow platforms to specify the use_napi setting in platform_env.conf
  • Added a startup service for NH-5010 to configure bcm0/1 to up -- this is required because use_napi=1 forces basedev_suspend=1 which prevents RX DMA and interrupt handling until the base KNET device is brought up

How to verify it

Ran a suite of PFC sonic-mgmt tests against NH-5010

Which release branch to backport (provide reason below if selected)

  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Tested branch (Please provide the tested image version)

Description for the changelog

Enable msi and napi for NH-5010

@roy-nexthop roy-nexthop requested a review from lguohan as a code owner March 16, 2026 18:55
@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@roy-nexthop roy-nexthop force-pushed the nh-5010-msi-napi branch 2 times, most recently from c1745a7 to c089f40 Compare March 19, 2026 23:20
@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

1 similar comment
@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

1 similar comment
@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yijingyan2
Copy link
Contributor

/azpw retry

@mssonicbld
Copy link
Collaborator

Retrying failed(or canceled) jobs...

@mssonicbld
Copy link
Collaborator

Retrying failed(or canceled) stages in build 1065319:
✅Stage Build:

  • Job marvell_prestera_arm64: retried.
    ✅Stage Test:
  • Job impacted-area-kvmtest-t2 by Elastictest: retried.

@yijingyan2
Copy link
Contributor

/azpw ms_conflict

1 similar comment
@yijingyan2
Copy link
Contributor

/azpw ms_conflict

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

5 participants