1. 18 10月, 2016 1 次提交
    • J
      ethernet/intel: use core min/max MTU checking · 91c527a5
      Jarod Wilson 提交于
      e100: min_mtu 68, max_mtu 1500
      - remove e100_change_mtu entirely, is identical to old eth_change_mtu,
        and no longer serves a purpose. No need to set min_mtu or max_mtu
        explicitly, as ether_setup() will already set them to 68 and 1500.
      
      e1000: min_mtu 46, max_mtu 16110
      
      e1000e: min_mtu 68, max_mtu varies based on adapter
      
      fm10k: min_mtu 68, max_mtu 15342
      - remove fm10k_change_mtu entirely, does nothing now
      
      i40e: min_mtu 68, max_mtu 9706
      
      i40evf: min_mtu 68, max_mtu 9706
      
      igb: min_mtu 68, max_mtu 9216
      - There are two different "max" frame sizes claimed and both checked in
        the driver, the larger value wasn't relevant though, so I've set max_mtu
        to the smaller of the two values here to retain identical behavior.
      
      igbvf: min_mtu 68, max_mtu 9216
      - Same issue as igb duplicated
      
      ixgb: min_mtu 68, max_mtu 16114
      - Also remove pointless old == new check, as that's done in dev_set_mtu
      
      ixgbe: min_mtu 68, max_mtu 9710
      
      ixgbevf: min_mtu 68, max_mtu dependent on hardware/firmware
      - Some hw can only handle up to max_mtu 1504 on a vf, others 9710
      
      CC: netdev@vger.kernel.org
      CC: intel-wired-lan@lists.osuosl.org
      CC: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
      Signed-off-by: NJarod Wilson <jarod@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      91c527a5
  2. 28 9月, 2016 3 次提交
  3. 24 9月, 2016 1 次提交
    • M
      net: Update API for VF vlan protocol 802.1ad support · 79aab093
      Moshe Shemesh 提交于
      Introduce new rtnl UAPI that exposes a list of vlans per VF, giving
      the ability for user-space application to specify it for the VF, as an
      option to support 802.1ad.
      We adjusted IP Link tool to support this option.
      
      For future use cases, the new UAPI supports multiple vlans. For now we
      limit the list size to a single vlan in kernel.
      Add IFLA_VF_VLAN_LIST in addition to IFLA_VF_VLAN to keep backward
      compatibility with older versions of IP Link tool.
      
      Add a vlan protocol parameter to the ndo_set_vf_vlan callback.
      We kept 802.1Q as the drivers' default vlan protocol.
      Suitable ip link tool command examples:
        Set vf vlan protocol 802.1ad:
          ip link set eth0 vf 1 vlan 100 proto 802.1ad
        Set vf to VST (802.1Q) mode:
          ip link set eth0 vf 1 vlan 100 proto 802.1Q
        Or by omitting the new parameter
          ip link set eth0 vf 1 vlan 100
      Signed-off-by: NMoshe Shemesh <moshe@mellanox.com>
      Signed-off-by: NTariq Toukan <tariqt@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      79aab093
  4. 22 9月, 2016 1 次提交
  5. 19 8月, 2016 4 次提交
  6. 17 8月, 2016 1 次提交
    • K
      igb: fix adjusting PTP timestamps for Tx/Rx latency · 0066c8b6
      Kshitiz Gupta 提交于
      Fix PHY delay compensation math in igb_ptp_tx_hwtstamp() and
      igb_ptp_rx_rgtstamp. Add PHY delay compensation in
      igb_ptp_rx_pktstamp().
      
      In the IGB driver, there are two functions that retrieve timestamps
      received by the PHY - igb_ptp_rx_rgtstamp() and igb_ptp_rx_pktstamp().
      The previous commit only changed igb_ptp_rx_rgtstamp(), and the change
      was incorrect.
      
      There are two instances in which PHY delay compensations should be
      made:
      
      - Before the packet transmission over the PHY, the latency between
        when the packet is timestamped and transmission of the packets,
        should be an add operation, but it is currently a subtract.
      
      - After the packets are received from the PHY, the latency between
        the receiving and timestamping of the packets should be a subtract
        operation, but it is currently an add.
      Signed-off-by: NKshitiz Gupta <kshitiz.gupta@ni.com>
      Fixes: 3f544d2a (igb: adjust ptp timestamps for tx/rx latency)
      Tested-by: NAaron Brown <aaron.f.brown@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      0066c8b6
  7. 30 6月, 2016 6 次提交
  8. 24 6月, 2016 1 次提交
  9. 21 5月, 2016 2 次提交
  10. 14 5月, 2016 4 次提交
  11. 05 5月, 2016 1 次提交
    • F
      drivers: replace dev->trans_start accesses with dev_trans_start · 4d0e9657
      Florian Westphal 提交于
      a trans_start struct member exists twice:
      - in struct net_device (legacy)
      - in struct netdev_queue
      
      Instead of open-coding dev->trans_start usage to obtain the current
      trans_start value, use dev_trans_start() instead.
      
      This is not exactly the same, as dev_trans_start also considers
      the trans_start values of the netdev queues owned by the device
      and provides the most recent one.
      
      For legacy devices this doesn't matter as dev_trans_start can cope
      with netdev trans_start values of 0 (they are ignored).
      
      This is a prerequisite to eventual removal of dev->trans_start.
      
      Cc: linux-rdma@vger.kernel.org
      Signed-off-by: NFlorian Westphal <fw@strlen.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4d0e9657
  12. 07 4月, 2016 5 次提交
  13. 18 3月, 2016 1 次提交
    • J
      mm: introduce page reference manipulation functions · fe896d18
      Joonsoo Kim 提交于
      The success of CMA allocation largely depends on the success of
      migration and key factor of it is page reference count.  Until now, page
      reference is manipulated by direct calling atomic functions so we cannot
      follow up who and where manipulate it.  Then, it is hard to find actual
      reason of CMA allocation failure.  CMA allocation should be guaranteed
      to succeed so finding offending place is really important.
      
      In this patch, call sites where page reference is manipulated are
      converted to introduced wrapper function.  This is preparation step to
      add tracepoint to each page reference manipulation function.  With this
      facility, we can easily find reason of CMA allocation failure.  There is
      no functional change in this patch.
      
      In addition, this patch also converts reference read sites.  It will
      help a second step that renames page._count to something else and
      prevents later attempt to direct access to it (Suggested by Andrew).
      Signed-off-by: NJoonsoo Kim <iamjoonsoo.kim@lge.com>
      Acked-by: NMichal Nazarewicz <mina86@mina86.com>
      Acked-by: NVlastimil Babka <vbabka@suse.cz>
      Cc: Minchan Kim <minchan@kernel.org>
      Cc: Mel Gorman <mgorman@techsingularity.net>
      Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
      Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      fe896d18
  14. 25 2月, 2016 8 次提交
  15. 16 2月, 2016 1 次提交
    • A
      igb: Add workaround for VLAN tag stripping on 82576 · bf456abb
      Alexander Duyck 提交于
      There was a workaround partially implemented for the 82576 that is needed
      in order for VLAN tag stripping to function correctly.  The original code
      had side effects that would make it so the workaround was active on all
      MACs.  I have updated the code so that the workaround is enabled, but
      limited to the 82576, or activated if we exceed the available unicast
      addresses.
      
      The workaround has a side effect of mirroring all of the traffic outgoing
      from the VFs back to the PF.  As such it is not recommended to use the
      82576 in promiscuous mode as it will take a performance hit, though this is
      now consistent with the performance as seen on the out-of-tree igb driver.
      
      I also limited the scope of the UTA bits all being set to only when the
      VMOLR register is enabled.  This should limit the effects of the UTA
      register so that we don't pick up any excess traffic unless promiscuous
      mode has been enabled on the PF, whereas before the PF would have ended up
      in something equivalent to unicast promiscuous mode with VLAN filtering
      otherwise.
      Signed-off-by: NAlexander Duyck <aduyck@mirantis.com>
      Tested-by: NAaron Brown <aaron.f.brown@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      bf456abb