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

Separate stress testing from the poison block testing #46

Open
rhempel opened this issue Jul 26, 2020 · 0 comments
Open

Separate stress testing from the poison block testing #46

rhempel opened this issue Jul 26, 2020 · 0 comments

Comments

@rhempel
Copy link
Owner

rhempel commented Jul 26, 2020

Currently the stress testing mechanism is built into the poison block testing. This needs an awkward data structure to manage calling the correct version of the allocation functions. Even worse, the stress test results are slightly different for 8 byte blocks and higher block sizes due to the extra memory that must be allocated to handle the poison areas.
Ideally, we need to separate the stress testing from poison testing, and also update the poison data area size to correctly allocate extra memory depending on the block size to that the number of blocks allocated during poison testing remains the same regardless of the block size.

@rhempel rhempel closed this as completed Mar 21, 2021
@rhempel rhempel reopened this Mar 21, 2021
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

No branches or pull requests

1 participant