netdev - Re: [ANNOUNCE] New driver vxge for Neterion's X3100 series 10GbEPCIe adapter

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: <20090401050940.GB11687@yzhao-otc.sh.intel.com>
Date:	Wed, 1 Apr 2009 13:09:40 +0800
From:	Yu Zhao <yu.zhao@...el.com>
To:	Ramkrishna Vepa <Ramkrishna.Vepa@...erion.com>
Cc:	"Duyck, Alexander H" <alexander.h.duyck@...el.com>,
	Leonid Grossman <Leonid.Grossman@...erion.com>,
	Netdev <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>
Subject: Re: [ANNOUNCE] New driver vxge for Neterion's X3100 series
	10GbEPCIe adapter

On Wed, Apr 01, 2009 at 11:36:11AM +0800, Ramkrishna Vepa wrote:
> > Yes, and that's what the PCI subsystem does. If the vxge VF is
> identical
> > to its PF, then vxge should be able to drive both PF and VF without
> any
> > modification.
> [Ram] Ok. In that case, is the call to pci_enable/disable_sriov still
> required for vxge?

Yes, the vxge driver first binds the PF once it's loaded (VF doesn't
exist at this time) and calls the SR-IOV API. The VF appears after the
SR-IOV is enabled and then the same copy of the vxge driver can bind
the VF too if you want to use the VF in the native Linux. Though the
hardware is in the SR-IOV mode in this case, it would be equal to the
multi-function mode. Or you can assign the VF to the Xen/KVM guest and
let another copy of vxge driver (may be vxge for Windows, Solaris, BSD,
etc.) running in the guest bind it.

Thanks,
Yu
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html