Skip to content

Conversation

@sylvestre
Copy link
Contributor

@github-actions
Copy link

GNU testsuite comparison:

Note: The gnu test tests/dd/no-allocate is now being skipped but was previously passing.

// reasonably large chunks for typical workloads.
const MIN_AUTOMATIC_BUF_SIZE: usize = 512 * 1024; // 512 KiB
const FALLBACK_AUTOMATIC_BUF_SIZE: usize = 32 * 1024 * 1024; // 32 MiB
// On 32-bit systems, use a smaller max buffer (256 MiB) to avoid allocation
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To confirm my understanding, this is only a temporary fix right? I was trying to replicate the behaviour in GNU and it appears they have a mechanism to determine the available memory and gracefully fallback to smaller and smaller amounts that I was not able to get an allocation failure. I'm thinking this would be a good band-aid solution for now but would be good to add a TODO or keep the issue with the description that we're missing some compatibility when it comes to the memory allocation fallbacks

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants