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

Curl_addrinfo: use one malloc instead of three #5533

Closed
wants to merge 1 commit into from

Conversation

@bagder
Copy link
Member

bagder commented Jun 6, 2020

To reduce the amount of allocations needed for creating a Curl_addrinfo
struct from a struct hostent, make one larger malloc instead of three
separate smaller ones.

@bagder bagder changed the title Curl_he2ai: use one malloc instead of three Curl_addrinfo: use one malloc instead of three Jun 7, 2020
bagder added a commit that referenced this pull request Jun 7, 2020
To reduce the amount of allocations needed for creating a Curl_addrinfo
struct, make one larger malloc instead of three separate smaller ones.

Closes #5533
@bagder bagder force-pushed the bagder/curl_he2ai-lessmalloc branch from eb14f7a to c71b702 Jun 7, 2020
bagder added a commit that referenced this pull request Jun 8, 2020
To reduce the amount of allocations needed for creating a Curl_addrinfo
struct, make one larger malloc instead of three separate smaller ones.

Closes #5533
@bagder bagder force-pushed the bagder/curl_he2ai-lessmalloc branch from c71b702 to 7104f72 Jun 8, 2020
To reduce the amount of allocations needed for creating a Curl_addrinfo
struct, make one larger malloc instead of three separate smaller ones.

Closes #5533
@bagder bagder force-pushed the bagder/curl_he2ai-lessmalloc branch from 7104f72 to 12c178b Jun 8, 2020
@bagder bagder closed this in 54d3769 Jun 8, 2020
@bagder bagder deleted the bagder/curl_he2ai-lessmalloc branch Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant
You can’t perform that action at this time.