summaryrefslogtreecommitdiff
path: root/include/net/sock.h
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2021-11-18 11:49:52 +0000
committerDavid S. Miller <davem@davemloft.net>2021-11-18 11:49:52 +0000
commit718cc29daa669cb1a8fee8f43309045018b0d4e0 (patch)
treef97157d71651624483a0e823bbfdb238dce4d201 /include/net/sock.h
parent867ae8a7993b26fc742703f748663cc2ac421db7 (diff)
parent339f28964147db9cb5c45d84a9b9d86a8ceb9260 (diff)
Merge branch '10GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue
Tony Nguyen says: ==================== 10GbE Intel Wired LAN Driver Updates 2021-11-17 Radoslaw Tyl says: The change is a consequence of errors reported by the ixgbevf driver while starting several virtual guests at the same time on ESX host. During this, VF was not able to communicate correctly with the PF, as a result reported "PF still in reset state. Is the PF interface up?" and then goes to locked state. The only thing left was to reload the VF driver on the guest OS. The background of the problem is that the current PFU and VFU semaphore locking mechanism between sender and receiver may cause overriding Mailbox memory (VFMBMEM), in such scenario receiver of the original message will read the invalid, corrupted or one (or more) message may be lost. This change is actually as a support for communication with PF ESX driver and does not contains changes and support for ixgbe driver. For maintain backward compatibility, previous communication method has been preserved in the form of LEGACY functions. In the future there is a plan to add a support for a 1.5 mailbox API communication also to ixgbe driver. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/net/sock.h')
0 files changed, 0 insertions, 0 deletions