WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-community] PCI Single Root IO Virtualization

To: <xen-community@xxxxxxxxxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-community] PCI Single Root IO Virtualization
From: "Guruprasad Swaminathan, Chennai" <guruprasadswami@xxxxxx>
Date: Thu, 29 May 2008 13:54:27 +0530
Delivery-date: Sat, 31 May 2008 18:39:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-archive: <http://lists.xensource.com/archives/html/xen-community>
List-help: <mailto:xen-community-request@lists.xensource.com?subject=help>
List-id: Community Discussion <xen-community.lists.xensource.com>
List-post: <mailto:xen-community@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-community>, <mailto:xen-community-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-community>, <mailto:xen-community-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-community-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjBYuOKA2yM6XRbRBi1XXaUyLsLCwAABT0g
Thread-topic: PCI Single Root IO Virtualization

 

Hi all,

I am enclosing with this mail the specification document of the PCI-SIG for Single Root I/O Virtualization.

I read the PCI SIG specification document for SR-IOV. The document described about how any I/O request in a machine with SR-IOV coming from the virtual machine bypasses the hypervisor and is handled directly by the device. The document also describes a software layer in hypervisor known as PCI-Manager which will configure the virtual functions to handle the I/O requests of the VMs.  The I/O requests of the virtual machines will be processed faster as the hypervisor will not be involved during the transactions.

 

But the document does not explain about how actually the I/O requests are handled by the virtual functions in the device that are responsible for handling the requests. Nor does it describe about the role of the device drivers (which are present in the Dom0) during the I/O requests and how I/O requests can happen without the involvement of the device drivers. Besides, the actual data flow from domU’s to dom0 and the role of the PCIM during data transfer is also unclear. Can anybody help us in understanding the same ?

 

Thanks and regards,

S.GURU PRASAD

 

DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.

-----------------------------------------------------------------------------------------------------------------------

Attachment: SR-IOV spec.pdf
Description: SR-IOV spec.pdf

_______________________________________________
Xen-community mailing list
Xen-community@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-community
<Prev in Thread] Current Thread [Next in Thread>