1. 20 Jul, 2016 1 commit
  2. 15 Apr, 2016 4 commits
  3. 11 Apr, 2016 2 commits
  4. 05 Apr, 2016 1 commit
  5. 04 Apr, 2016 2 commits
  6. 18 Mar, 2016 1 commit
    • Arnd Bergmann's avatar
      scsi: fc: use get/put_unaligned64 for wwn access · ef3fb242
      Arnd Bergmann authored
      A bug in the gcc-6.0 prerelease version caused at least one
      driver (lpfc) to have excessive stack usage when dealing with
      wwn data, on the ARM architecture.
      
      lpfc_scsi.c: In function 'lpfc_find_next_oas_lun':
      lpfc_scsi.c:117:1: warning: the frame size of 1152 bytes is larger than 1024 bytes [-Wframe-larger-than=]
      
      I have reported this as a gcc regression in
      https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70232
      
      However, using a better implementation of wwn_to_u64() not only
      helps with the particular gcc problem but also leads to better
      object code for any version or architecture.
      
      The kernel already provides get_unaligned_be64() and
      put_unaligned_be64() helper functions that provide an
      optimized implementation with the desired semantics.
      
      The lpfc_find_next_oas_lun() function in the example that
      grew from 1146 bytes to 5144 bytes when moving from gcc-5.3
      to gcc-6.0 is now 804 bytes, as the optimized
      get_unaligned_be64() load can be done in three instructions.
      The stack usage is now down to 28 bytes from 128 bytes with
      gcc-5.3 before.
      Signed-off-by: 's avatarArnd Bergmann <arnd@arndb.de>
      Reviewed-by: 's avatarHannes Reinicke <hare@suse.de>
      Reviewed-by: 's avatarEwan Milne <emilne@redhat.com>
      Signed-off-by: 's avatarMartin K. Petersen <martin.petersen@oracle.com>
      ef3fb242
  7. 05 Mar, 2016 1 commit
  8. 23 Feb, 2016 5 commits
  9. 27 Jan, 2016 1 commit
  10. 23 Dec, 2015 1 commit
  11. 18 Dec, 2015 2 commits
  12. 02 Dec, 2015 3 commits
  13. 30 Nov, 2015 1 commit
  14. 25 Nov, 2015 1 commit
  15. 19 Nov, 2015 1 commit
  16. 09 Nov, 2015 1 commit
  17. 28 Aug, 2015 5 commits
  18. 26 Aug, 2015 1 commit
  19. 03 Aug, 2015 1 commit
  20. 30 Jul, 2015 1 commit
    • Chris Leech's avatar
      iSCSI: let session recovery_tmo sysfs writes persist across recovery · 9c8108a4
      Chris Leech authored
      The iSCSI session recovery_tmo setting is writeable in sysfs, but it's
      also set every time a connection is established when parameters are set
      from iscsid over netlink.  That results in the timeout being reset to
      the default value after every recovery.
      
      The DM multipath tools want to use the sysfs interface to lower the
      default timeout when there are multiple paths to fail over.  It has
      caused confusion that we have a writeable sysfs value that seem to keep
      resetting itself.
      
      This patch adds an in-kernel flag that gets set once a sysfs write
      occurs, and then ignores netlink parameter setting once it's been
      modified via the sysfs interface.  My thinking here is that the sysfs
      interface is much simpler for external tools to influence the session
      timeout, but if we're going to allow it to be modified directly we
      should ensure that setting is maintained.
      Signed-off-by: 's avatarChris Leech <cleech@redhat.com>
      Reviewed-by: 's avatarMike Christie <michaelc@cs.wisc.edu>
      Signed-off-by: 's avatarJames Bottomley <JBottomley@Odin.com>
      9c8108a4
  21. 23 Jul, 2015 2 commits
  22. 14 Jul, 2015 1 commit
  23. 01 Jun, 2015 1 commit