1. 03 6月, 2016 2 次提交
    • D
      net: vrf: set operstate and mtu at link create · b87ab6b8
      David Ahern 提交于
      The VRF device exists to define L3 domains and guide FIB lookups. As
      such its operstate is not relevant. Seeing 'state UNKNOWN' in the
      output of 'ip link show' can be confusing, so set operstate at link
      create.
      
      Similarly, the MTU for a VRF device is not used; any fragmentation
      of the payload is done on the output path based on the real egress
      device. An MTU of 1500 on the VRF device while enslaved devices
      have a higher MTU can lead to confusion. Since the VRF MTU is not
      relevant set to 64k similar to what is done for loopback.
      Signed-off-by: NDavid Ahern <dsa@cumulusnetworks.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b87ab6b8
    • B
      net: ethernet: wiznet: Remove create_workqueue · 41cae08c
      Bhaktipriya Shridhar 提交于
      alloc_workqueue replaces deprecated create_workqueue().
      
      A dedicated workqueue has been used since the workitems are involved
      in normal device operation. Workitems &priv->rx_work and &priv->tx_work,
      map to w5100_rx_work and w5100_tx_work respectively and are involved in
      receiving and transmitting packets. Forward progress under
      memory pressure is a requirement here.
      
      create_workqueue has been replaced with alloc_workqueue with max_active
      as 0 since there is no need for throttling the number of active work
      items.
      
      Since the driver may be used in memory reclaim path,
      WQ_MEM_RECLAIM has been set to guarantee forward progress.
      
      flush_workqueue is unnecessary since destroy_workqueue() itself calls
      drain_workqueue() which flushes repeatedly till the workqueue
      becomes empty. Hence the call to flush_workqueue() has been dropped.
      Signed-off-by: NBhaktipriya Shridhar <bhaktipriya96@gmail.com>
      Acked-by: NTejun Heo <tj@kernel.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      41cae08c
  2. 02 6月, 2016 6 次提交
  3. 01 6月, 2016 8 次提交
  4. 30 5月, 2016 8 次提交
  5. 29 5月, 2016 1 次提交
    • G
      Eliminate bad hash multipliers from hash_32() and hash_64() · ef703f49
      George Spelvin 提交于
      The "simplified" prime multipliers made very bad hash functions, so get rid
      of them.  This completes the work of 689de1d6.
      
      To avoid the inefficiency which was the motivation for the "simplified"
      multipliers, hash_64() on 32-bit systems is changed to use a different
      algorithm.  It makes two calls to hash_32() instead.
      
      drivers/media/usb/dvb-usb-v2/af9015.c uses the old GOLDEN_RATIO_PRIME_32
      for some horrible reason, so it inherits a copy of the old definition.
      Signed-off-by: NGeorge Spelvin <linux@sciencehorizons.net>
      Cc: Antti Palosaari <crope@iki.fi>
      Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>
      ef703f49
  6. 28 5月, 2016 15 次提交