From owner-freebsd-stable@FreeBSD.ORG Wed Oct 24 07:50:02 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D171BA72 for ; Wed, 24 Oct 2012 07:50:02 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from host.omnilan.net (s1.omnilan.net [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 51BB08FC12 for ; Wed, 24 Oct 2012 07:50:01 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by host.omnilan.net (8.13.8/8.13.8) with ESMTP id q9O7pCNV063902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Oct 2012 09:51:16 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <50879D98.40006@omnilan.de> Date: Wed, 24 Oct 2012 09:49:44 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Jack Vogel Subject: Re: msi-x enabled igb works only if module loaded twice [Was: Re: kldload if_igb twice needed to bring nic into operation] References: <50859F7F.2080308@omnilan.de> <5085A323.8030501@omnilan.de> <50866839.5090204@omnilan.de> <20121023211205.GA21019@alchemy.franken.de> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig494CE36577E2065D27EAD157" Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 07:50:03 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig494CE36577E2065D27EAD157 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable schrieb Jack Vogel am 23.10.2012 23:25 (localtime): > LOL, wow this is interesting. When I first was developing the VF suppor= t, Well, in fact I choose 'kawela' (82576) because I originally wanted to use VFs. But I can't get SR-IOV working with ESXi5.1. I'm using async-drivers, and I have option "max_vfs" available and enabled, also at boot time ESXi detects SR-IOV: cpu0:4096)PCI: 5327: 00:02:00.0: Found Single Root I/O Virtualization support But later on, I get this error: cpu0:4573)<6>igb: : igb_validate_option: max_vfs - SR-IOV VF devices set to 4 cpu0:4573)<4>igb 0000:02:00.0: Failed to initialize SR-IOV virtualization Since I have no VMware support contract and found absoluetly no documentation, I gave up and plugged in a second kawela for passing through into my iSCSI-target-guest. I found some hints that SR-IOV needs additional BIOS features besides VT-x and VT-d, because SR-IOV cards need to allocate additional address space. But that's beyond my PCI knowledge, and my BearTooth board doesn't have such SR-IOV switches, so I'm trying to forget that I've ever heard of SR-IOV :-( Btw, are there plans to support IPSec offload for kawela? =2E.. > There is nothing you can do about this because the issue is in the host= , > not the guest, > well getting the host code fixed is the solution :) > > Hope this helps, Thanks a lot, VMware has to fix more passthrough issues, since 5.1 crashes easily with passthrough-setups and many people report PODs (pink screen of death; I've first seen that with 5.1) But unfortunately there's no way for me to get in contact with VMWare to raise this MSI-X-passthrough topic. This would porbably also fix the mps-msix-problems, but disabling MSI-X for mps doesn't cost that much interrupts. With igb I see 25k irq/s difference between MSI and MSI-X. I don't understand why, but it's too expensive for my single-socket system.= Thanks a lot, -Harry --------------enig494CE36577E2065D27EAD157 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlCHnZ4ACgkQLDqVQ9VXb8i0/gCffArtvym6VL2JDh1Qey5yLQ9u PggAoKe6Z+WqXaAydtPL7m3/AC9Olm1R =llqr -----END PGP SIGNATURE----- --------------enig494CE36577E2065D27EAD157--