-
Notifications
You must be signed in to change notification settings - Fork 530
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.
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
App Controlled Execution Config #3034
Conversation
} else {*/ | ||
CxPlatWorkerCount = CxPlatProcMaxCount(); | ||
ProcessorList = NULL; | ||
//} |
Check notice
Code scanning / CodeQL
Commented-out code
/*if (Config && Config->ProcessorCount) { | ||
CxPlatWorkerCount = Config->ProcessorCount; | ||
ProcessorList = Config->ProcessorList; | ||
} else {*/ |
Check notice
Code scanning / CodeQL
Commented-out code
"CxPlatThreadCreate"); | ||
goto Error; | ||
#ifndef _KERNEL_MODE // Not supported on kernel mode | ||
if (ExecProfile != QUIC_EXECUTION_PROFILE_TYPE_MAX_THROUGHPUT) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does max throughput related flag works without splitpartitioning?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Max throughput just means separate threads for UDP and QUIC now.
Description
Refactors the MsQuic API to allow for the application to explicitly configure the execution of MsQuic internals. This is the next step to allow the app to fully control execution.
Testing
Existing CI
Documentation
to-do