On 14-May-18 12:29 PM, Burakov, Anatoly wrote:
On 14-May-18 9:21 AM, Burakov, Anatoly wrote:
On 11-May-18 11:25 AM, Remy Horton wrote:
On 03/05/2018 18:18, Anatoly Burakov wrote:
[..]
Also, fixup unit tests to account for the new behavior.
Tried running the tests but it fails on a boundary check:
RTE>>memzone_autotest
test basic memzone API
[...]
1GB Huge pages available
test alignment for memzone_reserve
check alignments and lengths
check overlapping
test boundary alignment for memzone_reserve
check_memzone_bounded(MZ_TEST_bounded_128): invalid memzone boundary
128 crossed
Test Failed
RTE>>
Hi Remy,
Passes here, but i'll look into it, thanks for the report.
This failure is not caused by this patchset, and you should get similar
failures on master if you get these while testing my patchset. I am not
able to reproduce this issue, but i'll double-check the bounded reserve
code with a fine-toothed comb anyway.
Further investigation showed that this is indeed related to the new
code. So, v5 has a bug too, i'll fix it for v6.
--
Thanks,
Anatoly
