引導式測驗 · 中等 等級
使用 NVIDIA 容器工具包測驗的 GPU 容器
將主機 GPU 驅動程式與容器 CUDA 庫分開,並追蹤公開和驗證 NVIDIA 裝置所需的執行時間步驟。
問題 1 的 8
哪個元件通常在核心層級管理物理 NVIDIA GPU?
預覽每個問題8 問題
當您參加測驗時,就會出現答案和解釋。
- 哪個元件通常在核心層級管理物理 NVIDIA GPU?
- The host driver
- The CUDA container image alone
- 模型檢查點
- The Python package lockfile
- NVIDIA Container Toolkit 提供什麼作用?
- A replacement GPU kernel driver stored in each image
- Runtime integration that exposes devices and driver interfaces to containers
- A framework-neutral model accuracy benchmark
- A compiler that converts all Python into CUDA
- 為什麼有 CUDA 函式庫的容器仍然無法初始化 GPU?
- CUDA libraries always replace the host driver
- The container necessarily needs its own physical GPU
- The host driver or runtime integration may be incompatible or missing
- The model file does not contain a device node
- 在容器中看到 GPU 證明了什麼?
- That memory allocation can never fail
- That the model's accuracy is acceptable
- That CUDA and driver versions are identical
- Device visibility, but not that every application kernel will run correctly
- 為什麼更新映像內的 CUDA 套件與更新主機驅動程式不同?
- Both update the same kernel module automatically
- They are different software layers with different responsibilities
- The container cannot contain any runtime libraries
- Driver versions are determined by the model weights
- Which test is stronger than checking device visibility alone?
- Inspect the model filename
- Read the image tag
- Run a small representative framework operation on the GPU
- Confirm the container starts without a GPU request
- What should an incident record include for reproducibility?
- Only the framework version and model architecture
- Only the host driver and GPU model
- Image tag and Python version without runtime configuration
- Image digest, host driver, toolkit and runtime configuration
- What does GPU containerization not provide by itself?
- A fully independent hardware driver environment
- Packaged user-space dependencies
- A way to request devices at launch
- An image filesystem