From: Stephen Hemminger <stephen@networkplumber.org>
To: kys@microsoft.com, haiyangz@microsoft.com, sthemmin@microsoft.com
Cc: devel@linuxdriverproject.org, netdev@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: [PATCH v2 0/2] hv_netvsc: associate VF and PV device by serial number
Date: Fri, 14 Sep 2018 12:54:55 -0700 [thread overview]
Message-ID: <20180914195457.20433-1-sthemmin@microsoft.com> (raw)
The Hyper-V implementation of PCI controller has concept of 32 bit serial number
(not to be confused with PCI-E serial number). This value is sent in the protocol
from the host to indicate SR-IOV VF device is attached to a synthetic NIC.
Using the serial number (instead of MAC address) to associate the two devices
avoids lots of potential problems when there are duplicate MAC addresses from
tunnels or layered devices.
The patch set is broken into two parts, one is for the PCI controller
and the other is for the netvsc device. Normally, these go through different
trees but sending them together here for better review. The PCI changes
were submitted previously, but the main review comment was "why do you
need this?". This is why.
v2 - slot name can be shorter.
remove locking when creating pci_slots; see comment for explaination
Stephen Hemminger (2):
PCI: hv: support reporting serial number as slot information
hv_netvsc: pair VF based on serial number
drivers/net/hyperv/netvsc.c | 3 ++
drivers/net/hyperv/netvsc_drv.c | 58 ++++++++++++++++-------------
drivers/pci/controller/pci-hyperv.c | 37 ++++++++++++++++++
3 files changed, 73 insertions(+), 25 deletions(-)
--
2.18.0
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: kys@microsoft.com, haiyangz@microsoft.com, sthemmin@microsoft.com
Cc: devel@linuxdriverproject.org, linux-pci@vger.kernel.org,
netdev@vger.kernel.org
Subject: [PATCH v2 0/2] hv_netvsc: associate VF and PV device by serial number
Date: Fri, 14 Sep 2018 12:54:55 -0700 [thread overview]
Message-ID: <20180914195457.20433-1-sthemmin@microsoft.com> (raw)
The Hyper-V implementation of PCI controller has concept of 32 bit serial number
(not to be confused with PCI-E serial number). This value is sent in the protocol
from the host to indicate SR-IOV VF device is attached to a synthetic NIC.
Using the serial number (instead of MAC address) to associate the two devices
avoids lots of potential problems when there are duplicate MAC addresses from
tunnels or layered devices.
The patch set is broken into two parts, one is for the PCI controller
and the other is for the netvsc device. Normally, these go through different
trees but sending them together here for better review. The PCI changes
were submitted previously, but the main review comment was "why do you
need this?". This is why.
v2 - slot name can be shorter.
remove locking when creating pci_slots; see comment for explaination
Stephen Hemminger (2):
PCI: hv: support reporting serial number as slot information
hv_netvsc: pair VF based on serial number
drivers/net/hyperv/netvsc.c | 3 ++
drivers/net/hyperv/netvsc_drv.c | 58 ++++++++++++++++-------------
drivers/pci/controller/pci-hyperv.c | 37 ++++++++++++++++++
3 files changed, 73 insertions(+), 25 deletions(-)
--
2.18.0
next reply other threads:[~2018-09-15 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 19:54 Stephen Hemminger [this message]
2018-09-14 19:54 ` [PATCH v2 0/2] hv_netvsc: associate VF and PV device by serial number Stephen Hemminger
2018-09-14 19:54 ` [PATCH v2 1/2] PCI: hv: support reporting serial number as slot information Stephen Hemminger
2018-09-14 19:54 ` Stephen Hemminger
2018-09-14 19:54 ` [PATCH v2 2/2] hv_netvsc: pair VF based on serial number Stephen Hemminger
2018-09-14 19:54 ` Stephen Hemminger
2018-09-20 13:43 ` Lorenzo Pieralisi
2018-09-17 14:59 ` [PATCH v2 0/2] hv_netvsc: associate VF and PV device by " David Miller
2018-09-20 14:18 ` Lorenzo Pieralisi
2018-09-20 16:50 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180914195457.20433-1-sthemmin@microsoft.com \
--to=stephen@networkplumber.org \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.