From: "Kallol Biswas" <kallol@nucleodyne.com>
To: 'Konrad Rzeszutek Wilk' <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: NIC: Queue assignment to guest OS
Date: Tue, 19 Apr 2011 16:24:59 -0700 [thread overview]
Message-ID: <005801cbfee9$00ef50f0$02cdf2d0$@com> (raw)
In-Reply-To: <20110419204532.GA13003@dumpdata.com>
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
network
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@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-04-19 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 1:17 NIC: Queue assignment to guest OS Kallol Biswas
2011-04-19 18:47 ` Konrad Rzeszutek Wilk
2011-04-19 18:50 ` Kallol Biswas
2011-04-19 20:45 ` Konrad Rzeszutek Wilk
2011-04-19 23:24 ` Kallol Biswas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005801cbfee9$00ef50f0$02cdf2d0$@com' \
--to=kallol@nucleodyne.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).