1. 16 Oct, 2015 38 commits
  2. 15 Oct, 2015 2 commits
    • Lendacky, Thomas's avatar
      amd-xgbe: Use system workqueue for device restart · 96aec911
      Lendacky, Thomas authored
      A previous patch switched from using the system workqueue to the device
      workqueue for various operations. During a device restart the device
      workqueue is flushed so the restart cannot use this workqueue or else
      a deadlock results.  Move the device restart back to using the system
      workqueue.
      Signed-off-by: default avatarTom Lendacky <thomas.lendacky@amd.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      96aec911
    • David S. Miller's avatar
      Merge branch 'switchdev-locking' · 74661bee
      David S. Miller authored
      Jiri Pirko says:
      
      ====================
      switchdev: change locking
      
      This is something which I'm currently struggling with.
      Callers of attr_set and obj_add/del often hold not only RTNL, but also
      spinlock (bridge). So in that case, the driver implementing the op cannot sleep.
      
      The way rocker is dealing with this now is just to invoke driver operation
      and go out, without any checking or reporting of the operation status.
      
      Since it would be nice to at least put a warning in case the operation fails,
      it makes sense to do this in delayed work directly in switchdev core
      instead of implementing this in separate drivers. And that is what this patchset
      is introducing.
      
      So from now on, the locking of switchdev mod ops is consistent. Caller either
      holds rtnl mutex or in case it does not, caller sets defer flag, telling
      switchdev core to process the op later, in deferred queue.
      
      Function to force to process switchdev deferred ops can be called by op
      caller in appropriate location, for example after it releases
      spin lock, to force switchdev core to process pending ops.
      
      v1->v2:
      - rebased on current net-next head (including Scott's ageing patchset)
      v2->v3:
      - fixed comment s/of/or/ typo suggested by Nik
      v3->v4:
      - the actual patchset is sent instead of different branch I send in v3 :/
      v4->v5:
      - added patch to "const" attr param
      - reworked deferred ops infrastructure (mainly patch number 1 and
        internal users (patch 3 and 5)) - resolves the issue pointed out
        by John
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      74661bee