Releases: SX-Aurora/veoffload
VEO 1.3.2a, API version 4
New release built on official v1.3.2 plus some fixes:
- no fork during DMA, avoid data corruption,
- handle vedl_wait_exception() returning without exception,
- threads consuming 100% CPU, send BLOCKing system call message to VEOS (now all cores available for OpenMP),
- enforcing strict ordering of reqs pushed to queue,
- check if reqs are valid before waiting for them.
This release has veo_api_version(), which returns an integer with the API version. The official release does not have that function, yet.
Please use with the corresponding veoffload-veorun-1.3.2a release.
VEO API version 4
Fixes issue with static veorun linking.
Added veo_proc_create_static() explicit interface for providing own veorun.
Bumped API_VERSION to 4.
VEO API version 3 multithreaded (update 2)
This version eliminates the need for the fake TID and syscall interception. libveo_mt.so is not built any more and not needed to be linked with or preloaded. Some traps might still be hidden, and the one main limitation is that veo_proc_create() still needs to be called from the main thread.
Use this with the veoffload-veorun release 1.2.2a.
VEO API version 3 VH multithreaded (update)
Compared to 1.2.2a this version fixes two issues. An occasional deadlock in veo_call_wait_result() when used from multiple threads, and a very rare issue with request ordering.
I'd recommend to both, link with -lveo_mt and also preload /opt/nec/ve/veos/lib64/libveo_mt.so
export LD_PRELOAD=/opt/nec/ve/veos/lib64/libveo_mt.so
Use this together with https://github.com/SX_Aurora/veoffload-veorun release 1.2.2a!
VEO API v3 multithreaded VH program
With this version, using VEO from multiple threads of a VH program is possible with the limitation that veo_proc_create()
is called from the main thread. All subsequent VEO calls can be executed from other VH threads. This requires linking with both -lveo -lveo_mt
.
VEO API version 3 for veos-1.2.1
This version needs to be installed on veos-1.2.1 systems in order to be able to use OpenMP VEO kernels (with static veorun linking).
VEO API version 3
VEO w/ async memory transfers support. VEO API version 3.
VEO w/ stackargs support
VEO at the level of v1.0.1 with fixed ELF ID (using the official ELF ID) and the patches for stack arguments with intent "in".