diff options
author | Rafael Antognolli <[email protected]> | 2019-09-30 14:08:11 -0700 |
---|---|---|
committer | Rafael Antognolli <[email protected]> | 2019-10-03 12:40:33 -0700 |
commit | cdc331c6f9f6b2ffc035018de4445dba9b67c1f7 (patch) | |
tree | 2b500145a6204047ab212293af97f8fdc4a0696f /src/util/debug.c | |
parent | 0103d4747a39ddc46f51cc3e97f85414765913fb (diff) |
anv/block_pool: Align anv_block_pool state to 64 bits.
On 64 bits platforms, some atomic operations like __sync_fetch_and_add()
have constant time, but on 32 bits platforms they are implemented with a
loop and might take much longer.
Additionally, it seems like if their operands are not aligned to 64
bits, they also require extra memory accesses. From the Intel
Architecture's Developer Manual Vol. 1, 4.1.1:
"A word or doubleword operand that crosses a 4-byte boundary or a
quadword operand that crosses an 8-byte boundary is considered
unaligned and requires two separate memory bus cycles for access."
Forcing the u64 field to be aligned to 64 bits seems to make the unit
tests that are stressing this finish much faster.
Reviewed-by: Jason Ekstrand <[email protected]>
Diffstat (limited to 'src/util/debug.c')
0 files changed, 0 insertions, 0 deletions