jansol
jansol
I would rather just make remote work with LOADABLE_DRIVERS=ON. There's just the question of what to do about that one function that is (currently) called once during init.
It's not trivial since it needs a bit of special casing, but it should not be particularly difficult either. There just was no acute need to spend the time to...
AIUI `pocl_remote_init_device_ops` is called separately for each device? Meanwhile `pocl_remote_setup_peer_mesh` iterates over *servers* which likely do not have a 1:1 correspondence with devices. Currently `pocl_remote_setup_peer_mesh` assumes that all servers are...
Ah, in that case yes that should indeed Just Work :tm:
A REST client seems something that should be a shipped-but-disabled-by-default plugin like Blender does with a lot of things? That way it won't clutter the UI and increase startup times...
#1433 should fix the RDMA CI
Can you retry but add `--log_filter=err,warn,general` to the pocld command line arguments? The client log looks like the server is returning an error from clCreateBuffer, would be good to know...
Ah, it's tripping up over your AMD-APP platform with 0 devices for some reason. In the interim you can set `OCL_ICD_VENDORS=/etc/OpenCL/vendors/mesa.icd` in the environment of pocld to make the OpenCL...
Ah, that did indeed happen occasionally. Might just work if you try running it again. I have a potential fix as part of #1381
Yeah the socket polling code sometimes thinks there is something to read but then ends up with 0 bytes and if it happens in the wrong spot it can fail...