Skip to content

Commit 5ab761a

Browse files
authored
Add tip on how to check that the CXI provider is available (#233)
1 parent 838ae1a commit 5ab761a

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed

docs/software/container-engine/resource-hook.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -169,6 +169,36 @@ The hook is activated by setting the `com.hooks.cxi.enabled` annotation, which
169169
4194304 23925.61
170170
```
171171

172+
!!! tip "How to check the CXI provider works inside a container"
173+
174+
You might want to check if the CXI provider works inside a container,
175+
i.e. that the CXI hook has been correctly applied.
176+
177+
You can check if the CXI provider is working using `fi_info`,
178+
usually available alongside your `libfabric` installation,
179+
within the container:
180+
181+
```bash
182+
fi_info -p cxi
183+
```
184+
185+
??? example "CXI provider is working"
186+
```console
187+
$ fi_info -p cxi
188+
provider: cxi
189+
fabric: cxi
190+
domain: cxi0
191+
version: 0.1
192+
type: FI_EP_RDM
193+
protocol: FI_PROTO_CXI
194+
```
195+
196+
??? example "CXI provider not working"
197+
```console
198+
$ fi_info -p cxi
199+
fi_getinfo: -61 (No data available)
200+
```
201+
172202
[](){#ref-ce-aws-ofi-hook}
173203
### AWS OFI NCCL hook 
174204

0 commit comments

Comments
 (0)