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/
Home Products Support Community News


RE: [Xen-devel] NIC: Queue assignment to guest OS

To: "'Konrad Rzeszutek Wilk'" <konrad.wilk@xxxxxxxxxx>
Subject: RE: [Xen-devel] NIC: Queue assignment to guest OS
From: "Kallol Biswas" <kallol@xxxxxxxxxxxxxx>
Date: Tue, 19 Apr 2011 16:24:59 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 19 Apr 2011 16:25:58 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=nucleodyne.com; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-ACL-Warn:X-Source:X-Source-Args:X-Source-Dir; b=IYwT7rhUHioTP7bWOYBd4LBVJtutNMnPF3zCf+E6vplq6K4JauDnOwcL1RE9LKSaCnJWQ6IP+sfzZ1L9KrXGZkh1bh1zlYlTbQt4kUCpKpUI5szDB94NZDaeTgCgh9GV;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110419204532.GA13003@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <003801cbfb0a$de67a410$9b36ec30$@com> <20110419184750.GB7427@xxxxxxxxxxxx> <8DE07D65-675C-4AF7-8B4F-AA643173250F@xxxxxxxxxxxxxx> <20110419204532.GA13003@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acv+0tuJL+M6Zvu/T9GiEq7+0DgN1gAFQVDQ
If it is ok to modify host the network driver how should we do it in Xen?
What modules/driver should be changed.
The idea is to avoid backend/frontend implementation, and give direct HW
access to guest for maximum performance. There are certain issues with
guests accessing HW directly, one of them is guest to guest communication,
and another is VM migration.

Sorry again, legal agreement prevents us to disclose anything in previous
implementation; we overcame these issues in a certain way. Xen NIC folks
should be able to address the issues.

> > 
> > How did you do this in other virtualization frameworks?

I am still at loss here how you guys managed this without ripping the
driver of a NIC card and passed the MSI-X to a guest and the full PCI device
to _all_ of them and managed to negotiate some form of locking.

Xen-devel mailing list

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>