1. 16 2月, 2017 8 次提交
  2. 04 2月, 2017 1 次提交
  3. 19 1月, 2017 1 次提交
    • T
      net: Remove usage of net_device last_rx member · 4a7c9726
      Tobias Klauser 提交于
      The network stack no longer uses the last_rx member of struct net_device
      since the bonding driver switched to use its own private last_rx in
      commit 9f242738 ("bonding: use last_arp_rx in slave_last_rx()").
      
      However, some drivers still (ab)use the field for their own purposes and
      some driver just update it without actually using it.
      
      Previously, there was an accompanying comment for the last_rx member
      added in commit 4dc89133 ("net: add a comment on netdev->last_rx")
      which asked drivers not to update is, unless really needed. However,
      this commend was removed in commit f8ff080d ("bonding: remove
      useless updating of slave->dev->last_rx"), so some drivers added later
      on still did update last_rx.
      
      Remove all usage of last_rx and switch three drivers (sky2, atp and
      smc91c92_cs) which actually read and write it to use their own private
      copy in netdev_priv.
      
      Compile-tested with allyesconfig and allmodconfig on x86 and arm.
      
      Cc: Eric Dumazet <eric.dumazet@gmail.com>
      Cc: Jay Vosburgh <j.vosburgh@gmail.com>
      Cc: Veaceslav Falico <vfalico@gmail.com>
      Cc: Andy Gospodarek <andy@greyhouse.net>
      Cc: Mirko Lindner <mlindner@marvell.com>
      Cc: Stephen Hemminger <stephen@networkplumber.org>
      Signed-off-by: NTobias Klauser <tklauser@distanz.ch>
      Acked-by: NEric Dumazet <edumazet@google.com>
      Reviewed-by: NJay Vosburgh <jay.vosburgh@canonical.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4a7c9726
  4. 09 1月, 2017 1 次提交
  5. 04 1月, 2017 4 次提交
  6. 02 12月, 2016 1 次提交
  7. 05 11月, 2016 5 次提交
  8. 28 10月, 2016 1 次提交
  9. 18 10月, 2016 2 次提交
    • D
      ixgbe: Flip to the new dev walk API · 1cd127fc
      David Ahern 提交于
      Convert ixgbe users to new dev walk API. This is just a code conversion;
      no functional change is intended.
      Signed-off-by: NDavid Ahern <dsa@cumulusnetworks.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1cd127fc
    • 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
  10. 14 10月, 2016 1 次提交
  11. 23 9月, 2016 2 次提交
  12. 21 8月, 2016 2 次提交
  13. 19 8月, 2016 2 次提交
  14. 18 8月, 2016 1 次提交
  15. 17 8月, 2016 2 次提交
  16. 22 7月, 2016 3 次提交
  17. 15 7月, 2016 1 次提交
  18. 12 7月, 2016 1 次提交
  19. 30 6月, 2016 1 次提交
    • A
      ixgbe: Error handler for duplicate filter locations in hardware for cls_u32 offloads · 12746fd2
      Amritha Nambiar 提交于
      For u32 classifier filters, avoid overwriting existing filter
      in a hardware location without removing it first, to clean up
      inconsistencies due to duplicate values for filter location.
      
      Verified with the following filters:
      
      Create child hash tables:
      	handle 1: u32 divisor 1
      	handle 2: u32 divisor 1
      
      Link to the child hash table from parent hash table:
      	handle 800:0:11 u32 ht 800: link 1: \
      	offset at 0 mask 0f00 shift 6 plus 0 eat \
      	match ip protocol 6 ff match ip dst 15.0.0.1/32
      
      	handle 800:0:12 u32 ht 800: link 2: \
      	offset at 0 mask 0f00 shift 6 plus 0 eat \
      	match ip protocol 17 ff match ip dst 16.0.0.1/32
      
      Add filter into child hash table:
      	handle 1:0:3 u32 ht 1: \
      	match tcp src 22 ffff action drop
      
      Add another filter to the same location:
      	handle 2:0:3 u32 ht 2: \
      	match tcp src 33 ffff action drop
      Signed-off-by: NAmritha Nambiar <amritha.nambiar@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      12746fd2