linux-kernel - RE: [PATCH 0/16 v6] PCI: Linux kernel SR-IOV support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <78C9135A3D2ECE4B8162EBDCE82CAD77048C24C0@nekter>
Date:	Sat, 8 Nov 2008 10:37:54 -0500
From:	"Leonid Grossman" <Leonid.Grossman@...erion.com>
To:	"Fischer, Anna" <anna.fischer@...com>, "Greg KH" <greg@...ah.com>,
	"Yu Zhao" <yu.zhao@...scape.net>
Cc:	"Matthew Wilcox" <matthew@....cx>,
	"Anthony Liguori" <anthony@...emonkey.ws>,
	"H L" <swdevyid@...oo.com>, <randy.dunlap@...cle.com>,
	<grundler@...isc-linux.org>, "Chiang, Alexander" <achiang@...com>,
	<linux-pci@...r.kernel.org>, <rdreier@...co.com>,
	<linux-kernel@...r.kernel.org>, <jbarnes@...tuousgeek.org>,
	<virtualization@...ts.linux-foundation.org>, <kvm@...r.kernel.org>,
	<mingo@...e.hu>, <keir.fraser@...citrix.com>,
	<eddie.dong@...el.com>, <jun.nakajima@...el.com>, <avi@...hat.com>
Subject: RE: [PATCH 0/16 v6] PCI: Linux kernel SR-IOV support



> -----Original Message-----
> From: Fischer, Anna [mailto:anna.fischer@...com]
> Sent: Saturday, November 08, 2008 3:10 AM
> To: Greg KH; Yu Zhao
> Cc: Matthew Wilcox; Anthony Liguori; H L; randy.dunlap@...cle.com;
> grundler@...isc-linux.org; Chiang, Alexander;
linux-pci@...r.kernel.org;
> rdreier@...co.com; linux-kernel@...r.kernel.org;
jbarnes@...tuousgeek.org;
> virtualization@...ts.linux-foundation.org; kvm@...r.kernel.org;
> mingo@...e.hu; keir.fraser@...citrix.com; Leonid Grossman;
> eddie.dong@...el.com; jun.nakajima@...el.com; avi@...hat.com
> Subject: RE: [PATCH 0/16 v6] PCI: Linux kernel SR-IOV support
> 


> > But would such an api really take advantage of the new IOV
interfaces
> > that are exposed by the new device type?
> 
> I agree with what Yu says. The idea is to have hardware capabilities
to
> virtualize a PCI device in a way that those virtual devices can
represent
> full PCI devices. The advantage of that is that those virtual device
can
> then be used like any other standard PCI device, meaning we can use
> existing
> OS tools, configuration mechanism etc. to start working with them.
Also,
> when
> using a virtualization-based system, e.g. Xen or KVM, we do not need
> to introduce new mechanisms to make use of SR-IOV, because we can
handle
> VFs as full PCI devices.
> 
> A virtual PCI device in hardware (a VF) can be as powerful or complex
as
> you like, or it can be very simple. But the big advantage of SR-IOV is
> that hardware presents a complete PCI device to the OS - as opposed to
> some resources, or queues, that need specific new configuration and
> assignment mechanisms in order to use them with a guest OS (like, for
> example, VMDq or similar technologies).
> 
> Anna


Ditto. 
Taking netdev interface as an example - a queue pair is a great way to
scale across cpu cores in a single OS image, but it is just not a good
way to share device across multiple OS images. 
The best unit of virtualization is a VF that is implemented as a
complete netdev pci device (not a subset of a pci device).
 This way, native netdev device drivers can work for direct hw access to
a VF "as is", and most/all Linux networking features (including VMQ)
will work in a guest.
Also, guest migration for netdev interfaces (both direct and virtual)
can be supported via native Linux mechanism (bonding driver), while Dom0
can retain "veto power" over any guest direct interface operation it
deems privileged (vlan, mac address, promisc mode, bandwidth allocation
between VFs, etc.).
 
Leonid
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/