From: Greg Law <glaw@solarflare.com>
To: Masroor Vettuparambil <Masroor.Vettuparambil@neterion.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen support for PCI-SIG I/O Virtualization
Date: Fri, 18 Jan 2008 17:31:16 +0000 [thread overview]
Message-ID: <4790E264.2010207@solarflare.com> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD7702DE578A@nekter>
Hi Masroor,
Masroor Vettuparambil wrote:
> hi Greg,
>
> thanks for the comment.
> I have yet to go through ur work. Please provide a quick link.
>
> I would like to know whether your proprietary mechanism supports virtual
> functions just like in IOV.
> If so, can you brief me on how this is accessed from the host and
> assigned to guest domains?
> Infact I am more interested how this is happening in IOV method.
The framework is deliberately very generic. Essentially it is just a
way for netfront to have a plugin which can handle tx/rx of packets
directly. How this works (IOV, proprietary, whatever) is not the
concern of the framework: you write netfront and netback plugins to
implement it as required by your hardware.
The framework is not really intended to avoid you needing to write lots
of code - it's not a "library". Rather it's the minimum amount of
infrastructure required so that VMs can be migrated between different
hosts with different types of smart NICs (or no smart NICs).
No one has written an implementation of plugins that use IOV yet, but
I'm pretty confident it will work without major changes.
As for the code, a good place to start is the definition of struct
netfront_accel_hooks in linux/drivers/xen/netfront/netfront.h
The set of patches were posted to xen-devel by Kieran Mansley Fri, 18
May 2007. Sadly, I'm not sure what the change set number is, but you
can get more info here: http://lwn.net/Articles/235124/
g
--
Greg Law Solarflare Communications +44 1223 518 040
prev parent reply other threads:[~2008-01-18 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 8:39 Xen support for PCI-SIG I/O Virtualization Masroor Vettuparambil
2008-01-16 17:55 ` Greg Law
2008-01-17 0:20 ` Woller, Thomas
2008-01-17 11:28 ` Greg Law
2008-01-17 12:02 ` Masroor Vettuparambil
2008-01-18 17:31 ` Greg Law [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=4790E264.2010207@solarflare.com \
--to=glaw@solarflare.com \
--cc=Masroor.Vettuparambil@neterion.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.