Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

XDP should use all available logical processors for user mode operation #3524

Open
srsubra opened this issue Mar 20, 2023 · 1 comment · May be fixed by #4857
Open

XDP should use all available logical processors for user mode operation #3524

srsubra opened this issue Mar 20, 2023 · 1 comment · May be fixed by #4857
Assignees
@mtfriesen
Labels
Area: Lola Related to low latency work feature request A request for new functionality Partner: SQL By or For the SQL team
Milestone
Future

Comments

@srsubra
Copy link

srsubra commented Mar 20, 2023

Describe the feature you'd like supported

During a recent test with QTIP, it was observed that the system had 4 logical processors
image

but XDP user mode polling seems to happen only for 2 of them leaving the other two underutilized as shown below

image

Proposed solution

XDP should leverage all available logical processors for user mode polling to maximize the perf.

Additional context

No response
@srsubra srsubra added the feature request A request for new functionality label Mar 20, 2023
@nibanks nibanks added the Area: Lola Related to low latency work label Mar 20, 2023
@nibanks nibanks added this to the Release 2.3 milestone Mar 20, 2023
@nibanks nibanks moved this to Should be written in MsQuic Walkthroughs May 8, 2023
@nibanks nibanks modified the milestones: Release 2.3, Release 2.4 Oct 12, 2023
@nibanks nibanks added the Partner: SQL By or For the SQL team label Mar 14, 2024
@nibanks nibanks modified the milestones: Release 2.4, Release 2.5 Aug 29, 2024
@nibanks nibanks modified the milestones: Release 2.5, Future Jan 28, 2025
@mtfriesen
Copy link
Contributor

mtfriesen commented Feb 23, 2025 •
edited
Loading

@nibanks this machine has two cores eligible for RSS and was using those two cores according to the screenshots above. Is the ask to use hyperthreading cores for RSS or to spread the QUIC workers beyond the number of RSS cores?

For context, the default NDIS policy is to only allow RSS on physical processors, not on any additional logical processors on the system. XDP can override this (I think) but the original NDIS policy was based on measurements years ago showing no significant benefit for RSS on hyperthreading cores.

@nibanks nibanks moved this from Planned to In Progress in DPT Iteration Tracker Feb 25, 2025
@mtfriesen mtfriesen linked a pull request Feb 27, 2025 that will close this issue
Draft
3 tasks
@nibanks nibanks moved this from In Progress to Slipped in DPT Iteration Tracker Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mtfriesen mtfriesen

Labels
Area: Lola Related to low latency work feature request A request for new functionality Partner: SQL By or For the SQL team
Projects
DPT Iteration Tracker
Status: Slipped
Milestone
Future
Development

Successfully merging a pull request may close this issue.

Use all CPUs by reprogramming VF RSS microsoft/msquic
3 participants
@mtfriesen @nibanks @srsubra