SR-IOV: Difference between revisions
(Template migration to LLM-Optimized Wiki Template) |
(Fix: remove --- horizontal lines (7 removed)) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 18: | Line 18: | ||
* 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | * 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | ||
== Purpose == | == Purpose == | ||
| Line 28: | Line 27: | ||
* Non-goals: 다른 주제로의 확장 | * Non-goals: 다른 주제로의 확장 | ||
== Key Concepts == | == Key Concepts == | ||
| Line 42: | Line 40: | ||
|} | |} | ||
== Detailed Explanation == | == Detailed Explanation == | ||
| Line 51: | Line 48: | ||
<references /> | <references /> | ||
== Best Practices == | == Best Practices == | ||
| Line 59: | Line 55: | ||
* 테스트 환경에서 먼저 검증 | * 테스트 환경에서 먼저 검증 | ||
== References == | == References == | ||
| Line 65: | Line 60: | ||
* [https://wiki.hpcmate.com SR-IOV] | * [https://wiki.hpcmate.com SR-IOV] | ||
== Related Pages == | == Related Pages == | ||
| Line 74: | Line 68: | ||
* [[Network]] | * [[Network]] | ||
[[Category:Server]] | [[Category:Server]] | ||
== Knowledge Graph == | |||
Related | |||
→ [[Linux]] | |||
→ [[Server]] | |||
→ [[Hardware]] | |||
→ [[Network]] | |||
[[Category:Reference]] | [[Category:Reference]] | ||
Latest revision as of 11:30, 17 July 2026
Overview
SR-IOV에 대한 기술 문서입니다.
Summary
- 무엇인가? - SR-IOV
- 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
- 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
Purpose
이 문서가 존재하는 이유
- Goal: SR-IOV에 대한 기술 정보 제공
- Scope: SR-IOV의 개념, 사용법, 설정
- Non-goals: 다른 주제로의 확장
Key Concepts
| Concept | Description | Related |
|---|---|---|
| SR-IOV | HPC/서버 환경에서 중요한 기술 개념 | Linux, Server |
Detailed Explanation
SR-IOV (Single Root - I/O Virtualization) is a technology that allows a single PCIe device to appear as multiple separate physical devices to the host system. Disabling SR-IOV can affect how the GPU is exposed to the operating system and drivers[1] SR-IOV is commonly used in conjunction with an SR-IOV enabled hypervisor to provide virtual machines direct hardware access to network resources hence increasing its performance. NVIDIA adapters are capable of exposing up to 127 virtual instances (Virtual Functions (VFs) for each port in the NVIDIA ConnectX® family cards. These virtual functions can then be provisioned separately. Each VF can be seen as an additional device connected to the Physical Function. It shares the same resources with the Physical Function, and its number of ports equals those of the Physical Function[2]
Best Practices
- 최신 버전 사용 권장
- 공식 문서 참고
- 테스트 환경에서 먼저 검증
References
Related Pages
Knowledge Graph
Related