Skip to content

Commit 5cc1bdc

Browse files
committed
review
1 parent c704384 commit 5cc1bdc

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

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

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

172-
!!! tip "How to check if the CXI provider is available"
172+
!!! tip "How to check the CXI provider works inside a container"
173173

174-
You can check if the CXI provider is available using `fi_info`
175-
(within the container):
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:
176180

177181
```bash
178182
fi_info -p cxi
179183
```
180184

181-
??? example "CXI provider available"
185+
??? example "CXI provider is working"
182186
```console
183187
$ fi_info -p cxi
184188
provider: cxi
@@ -189,7 +193,7 @@ The hook is activated by setting the `com.hooks.cxi.enabled` annotation, which
189193
protocol: FI_PROTO_CXI
190194
```
191195

192-
??? example "CXI provider not available"
196+
??? example "CXI provider not working"
193197
```console
194198
$ fi_info -p cxi
195199
fi_getinfo: -61 (No data available)

0 commit comments

Comments
 (0)