From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Kallol Biswas <kallol@nucleodyne.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: NIC: Queue assignment to guest OS
Date: Tue, 19 Apr 2011 16:45:32 -0400 [thread overview]
Message-ID: <20110419204532.GA13003@dumpdata.com> (raw)
In-Reply-To: <8DE07D65-675C-4AF7-8B4F-AA643173250F@nucleodyne.com>
On Tue, Apr 19, 2011 at 11:50:35AM -0700, Kallol Biswas wrote:
> Unfortunately other frameworks are not open source, and we can not use the design and expose to all.
Please don't top post.
>
> On Apr 19, 2011, at 11:47 AM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
>
> > On Thu, Apr 14, 2011 at 06:17:17PM -0700, Kallol Biswas wrote:
> >> Hi,
> >>
> >> I have a requirement to assign the transmit and receive queues of a NIC
> >> card to different guest operating systems so that the guests can directly
> >> submit transmit requests to controller and receive packets from NIC
> >> controller without going through a middle layer. The NIC controller is not
> >> SRIOV capable and there are a few MSI-X vectors available.
> >
> > OK. So you want to "export" the rx and tx queue (where each queue is associated
> > with an MSI-X) in the guest.
> >
> >>
> >>
> >>
> >> What would be the best way to implement the requirement in Xen? I am new to
> >> Xen but have experience in a similar virtualization framework.
> >
> > 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.
next prev parent reply other threads:[~2011-04-19 20:45 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 [this message]
2011-04-19 23:24 ` Kallol Biswas
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=20110419204532.GA13003@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=kallol@nucleodyne.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).