netdev - Re: [NET-NEXT PATCH 2/2] igb: Correctly determine pci-e function number in virtual environment

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] [day] [month] [year] [list]

Message-Id: <20081210.011100.167309841.davem@davemloft.net>
Date:	Wed, 10 Dec 2008 01:11:00 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	jeffrey.t.kirsher@...el.com
Cc:	netdev@...r.kernel.org, jeff@...zik.org,
	alexander.h.duyck@...el.com
Subject: Re: [NET-NEXT PATCH 2/2] igb: Correctly determine pci-e function
 number in virtual environment

From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Date: Tue, 09 Dec 2008 18:42:16 -0800

> When running in a virtual environment the ports of an 82575/6 can appear to
> be single function devices which is not correct.  To resolve this we rely
> on the function number stored in the status register.
> 
> Signed-off-by: Alexander Duyck <alexander.h.duyck@...el.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>

Also applied, thanks!

I noticed that there is a LRO Kconfig option for this driver.
That should be eliminated and LRO enabled by default since
for the cases where LRO causes trouble (routing, bridging,
etc.) we'll make ethtool calls to disable LRO on the device.
--
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