XenのSR-IOVｲﾝﾌﾟﾘについて、いくつか解説があったのでメモ。
http://www.usenix.org/event/wiov08/tech/full_papers/levasseur/levasseur_html/
http://www.usenix.org/event/wiov08/tech/full_papers/dong/dong_html/
http://www.mjmwired.net/kernel/Documentation/PCI/pci-iov-howto.txt
この資料にPCI hot plug機能を使ってVirtual Functionを追加するとある。
--
3.1.1 VF assignment
The VF, appearing as a "light-weight" PCIe function when enabled in hardware, doesn't respond to ordinary PCI bus scan for vendor ID and device ID used in OS to discover PCI function, and thus can't be enumerated by dom0 Linux. Xen SR-IOV networking architecture utilizes Linux PCI hot plug API to dynamically add VFs to dom0 Linux when VFs are enabled and vice versa when VFs are disabled so that existing direct I/O architecture works for VF too.
--
http://www.usenix.org/event/wiov08/tech/full_papers/levasseur/levasseur_html/
http://www.usenix.org/event/wiov08/tech/full_papers/dong/dong_html/
http://www.mjmwired.net/kernel/Documentation/PCI/pci-iov-howto.txt
この資料にPCI hot plug機能を使ってVirtual Functionを追加するとある。
--
3.1.1 VF assignment
The VF, appearing as a "light-weight" PCIe function when enabled in hardware, doesn't respond to ordinary PCI bus scan for vendor ID and device ID used in OS to discover PCI function, and thus can't be enumerated by dom0 Linux. Xen SR-IOV networking architecture utilizes Linux PCI hot plug API to dynamically add VFs to dom0 Linux when VFs are enabled and vice versa when VFs are disabled so that existing direct I/O architecture works for VF too.
--
コメントする