From: Javier Guerra Giraldez <javier@guerrag.com>
To: "Zhao, Yu" <yu.zhao@intel.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Grant Grundler <grundler@parisc-linux.org>,
Alex Chiang <achiang@hp.com>, Matthew Wilcox <matthew@wil.cx>,
Roland Dreier <rdreier@cisco.com>, Greg KH <greg@kroah.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 0/6 v3] PCI: Linux kernel SR-IOV support
Date: Sat, 27 Sep 2008 13:07:57 -0500 [thread overview]
Message-ID: <200809271308.03547.javier@guerrag.com> (raw)
In-Reply-To: <D8078B8B3B09934AA9F8F2D5FB3F28CE088751B5EF@pdsmsx502.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
On Saturday 27 September 2008, Zhao, Yu wrote:
> Greetings,
>
> Following patches are intended to support SR-IOV capability in the Linux
> kernel. With these patches, people can turn a PCI device with the
> capability into multiple ones from software perspective, which can benefit
> KVM and achieve other purposes such as QoS, security, etc.
sounds great, i think some Infiniband HBAs have this capability; they even
suggested using on Xen for faster (no hypervisor intervention) communication
between DomU's on the same box. (and transparently to out of the box, of
course)
does it need an IOMMU (VT-d), or the whole magic is done by the PCI device?
--
Javier
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-09-27 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 8:27 [PATCH 0/6 v3] PCI: Linux kernel SR-IOV support Zhao, Yu
2008-09-27 18:07 ` Javier Guerra Giraldez [this message]
2008-10-08 2:32 ` Zhao, Yu
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=200809271308.03547.javier@guerrag.com \
--to=javier@guerrag.com \
--cc=achiang@hp.com \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=randy.dunlap@oracle.com \
--cc=rdreier@cisco.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=yu.zhao@intel.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).