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.

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

Allow Multiple Pending Buffers Simultaneously #4018

Open
kamrey2 opened this issue Dec 19, 2023 · 0 comments
Open

Allow Multiple Pending Buffers Simultaneously #4018

kamrey2 opened this issue Dec 19, 2023 · 0 comments
Labels
Area: API Area: Core Related to the shared, core protocol logic Area: Performance feature request A request for new functionality Partner: Windows HTTP By or For the Windows HTTP team
Milestone

Comments

@kamrey2
Copy link

kamrey2 commented Dec 19, 2023

Describe the feature you'd like supported

When data on a QUIC stream is available, MSQuic gives the buffer with the data to the application. The application can hold on to the buffer as long as it needs. The current API allows only a single buffer to be given to the application, i.e. pending, at the time.
Currently htp.sys copies the data from the buffer to its own buffer and gives the buffer back to MSQuic as fast as possible. Http.sys would like to avoid the copy and hold on to the MSQuic buffer until it is given the the application on top of http.sys. To make this new approach performant, http.sys will need to have multiple MSQuic buffers pending at a time.

Proposed solution

N/A

Additional context

No response

@kamrey2 kamrey2 added the feature request A request for new functionality label Dec 19, 2023
@nibanks nibanks added Area: Performance Area: API Area: Core Related to the shared, core protocol logic labels Dec 19, 2023
@nibanks nibanks added this to the Release 2.4 milestone Dec 19, 2023
@nibanks nibanks added the Partner: Windows HTTP By or For the Windows HTTP team label Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: API Area: Core Related to the shared, core protocol logic Area: Performance feature request A request for new functionality Partner: Windows HTTP By or For the Windows HTTP team
Projects
None yet
Development

No branches or pull requests

2 participants