From: Greg Law <glaw@solarflare.com>
To: "Woller, Thomas" <thomas.woller@amd.com>
Cc: Masroor Vettuparambil <Masroor.Vettuparambil@neterion.com>,
xen-devel@lists.xensource.com
Subject: Re: Xen support for PCI-SIG I/O Virtualization
Date: Thu, 17 Jan 2008 11:28:37 +0000 [thread overview]
Message-ID: <478F3BE5.6060704@solarflare.com> (raw)
In-Reply-To: <683860AD674C7348A0BF0DE3918482F6069EEC65@SAUSEXMB1.amd.com>
Woller, Thomas wrote:
>> Let me know if you want to know more.
> Curious if your patches have any multi-root logic.. Or if only SR.
Actually, our patches do nothing with IOV (SR or MR). They are a
framework which allows one to write plugin drivers for netfront/netback
for accelerated network tx/rx. The framework does not mandate how this
is implemented. We expect it to be used by smart devices which can be
accessed directly from the guest, but even that is not strictly
necessary to use the framework. If the NIC does allow safe access
directly from the guest, it might be that the silicon uses PCI IOV, or
some other mechanism (e.g. our smart NIC uses a proprietary mechanism
which pre-dates IOV).
>
> Do you have specific smart NICs that you recommend that work with your
> patches/Xen?
Yes, ours :)
You can currently buy them as "SMC Tigertron" cards. Our plugin drivers
will be submitted to this list soon.
Cheers,
Greg
--
Greg Law Solarflare Communications +44 1223 518 040
next prev parent reply other threads:[~2008-01-17 11:28 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 [this message]
2008-01-17 12:02 ` Masroor Vettuparambil
2008-01-18 17:31 ` Greg Law
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=478F3BE5.6060704@solarflare.com \
--to=glaw@solarflare.com \
--cc=Masroor.Vettuparambil@neterion.com \
--cc=thomas.woller@amd.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.