Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 23 8月, 2016 1 次提交
  3. 22 8月, 2016 1 次提交
  5. 19 8月, 2016 1 次提交
  7. 15 8月, 2016 2 次提交
    • H
      cxgb4/cxgb4vf: Add set VF mac address support · 858aa65c
      由 Hariprasad Shenai 提交于 
      Add ndo_set_vf_mac support which allows to set the MAC address
for cxgb4vf interfaces from the host
Signed-off-by: NHariprasad Shenai <hariprasad@chelsio.com>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      858aa65c
    • H
      cxgb4: Add control net_device for configuring PCIe VF · 7829451c
      由 Hariprasad Shenai 提交于 
      Issue:
For instance, the current APIs assume a 1-to-1 mapping of Network Ports,
Physical Functions and the SR-IOV Virtual Functions of those Physical
Functions. This is not the case with our cards where any Virtual
Function can be hooked up to any Port -- or any number of Ports the
current Linux APIs also assume only 1 Network Interface/Port can be
accessed per Virtual Function.

Another issue is that these APIs assume that the Administrative Driver
is attached to the Physical Function Associated with a Virtual Function.
This is not the case with our card where all administration is performed
by a Driver which is not attached to any of the Physical Functions which
have SR-IOV PCI Capabilities.

Another consequence of these assumptions is the inability to utilize all
of the cards SR-IOV resources. For instance, our cards have SR-IOV
Capabilities on Physical Functions 0..3 and the administrative Driver
attaches to Physical Function 4. Each of the Physical Functions 0..3 can
support up to 16 Virtual Functions. With the current Linux APIs, a
2-Port card would only be able to use the Virtual Functions on Physical
Function 0..1 and not allow the Virtual Functions on Physical Functions
2..3 to be used since there are no Ports 2..3 on a 2-Port card.

Fix:
Since the control node is always the netdevice for all VF ACL commands.
Created a dummy netdevice for each Physical Function from 0 to 3 through
which one could control their VFs. The device won't be associated with
any port, since it doesn't need to transmit/receive. Its purely used
for VF management purpose only. The device will be registered only when
VF for a particular PF is configured using PCI sysfs interface and
unregistered while pci_disable_sriov() for the PF is called.
Signed-off-by: NHariprasad Shenai <hariprasad@chelsio.com>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      7829451c
  9. 16 6月, 2016 3 次提交
  11. 08 5月, 2016 1 次提交
  13. 30 4月, 2016 1 次提交
  15. 27 4月, 2016 3 次提交
  17. 07 4月, 2016 1 次提交
  19. 22 3月, 2016 3 次提交
  21. 19 2月, 2016 1 次提交
  23. 25 12月, 2015 2 次提交
  25. 24 12月, 2015 3 次提交
  27. 18 12月, 2015 1 次提交
  29. 12 12月, 2015 1 次提交
  31. 22 10月, 2015 3 次提交
  33. 11 10月, 2015 1 次提交
  35. 05 10月, 2015 1 次提交
  37. 29 9月, 2015 1 次提交
  39. 10 9月, 2015 1 次提交
  41. 07 9月, 2015 1 次提交
    • F
      cxgb4: fix usage of uninitialized variable · 46cdc9be
      由 françois romieu 提交于 
      drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c: In function ‘init_one’:
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:4579:8: warning: ‘chip’ may be used uninitialized in this function [-Wmaybe-uninitialized]
   chip |= CHELSIO_CHIP_CODE(CHELSIO_T4, pl_rev);
        ^
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:4571:11: note: ‘chip’ was declared here
  int ver, chip;
           ^

Fixes: d86bd29e ("cxgb4/cxgb4vf: read the correct bits of PL Who Am I register")
Signed-off-by: NFrancois Romieu <romieu@fr.zoreil.com>
Cc: Hariprasad Shenai <hariprasad@chelsio.com>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      46cdc9be
  43. 29 8月, 2015 1 次提交
  45. 13 8月, 2015 2 次提交
  47. 04 8月, 2015 1 次提交
  49. 09 7月, 2015 1 次提交
  51. 01 7月, 2015 1 次提交
  53. 12 6月, 2015 1 次提交