1. 18 2月, 2010 2 次提交
  2. 13 1月, 2010 1 次提交
  3. 10 12月, 2009 1 次提交
    • N
      [SCSI] megaraid_sas: make driver PCI legacy I/O port free driver · aeab3fd7
      Noriyuki Fujii 提交于
      On the large servers, I/O port resource may not be assigned to all
      the PCI devices since it is limited (to 64KB on Intel Architecture[1])
      and it may also be fragmented (I/O base register of PCI-to-PCI bridge
      will usually be aligned to a 4KB boundary[2]).
      If no I/O port resource is assigned to devices, those devices do not
      work.
      
      [1] Some machines support 64KB I/O port space per PCI segment.
      [2] Some P2P bridges support optional 1KB aligned I/O base.
      
      Therefore, I made a patch for MegaRAID SAS driver to make PCI legacy
      I/O port free.  I have also tested the patch and it had no problem.
      
      The way to make PCI legacy I/O port free is the same as Fusion-MPT
      driver's and it has been merged into 2.6.30.4.
      
      This has already been fixed in e1000 and lpfc.
      
      As a result of the above, the driver can handle its device even when
      there are a huge number of PCI devices being used on the system and no
      I/O port region assigned to the device.
      Signed-off-by: NNoriyuki Fujii <n-fujii@np.css.fujitsu.com>
      Acked-by: N"Yang, Bo" <Bo.Yang@lsi.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      aeab3fd7
  4. 30 10月, 2009 13 次提交
  5. 21 9月, 2009 1 次提交
  6. 07 4月, 2009 2 次提交
  7. 02 12月, 2008 1 次提交
  8. 02 11月, 2008 1 次提交
    • A
      saner FASYNC handling on file close · 233e70f4
      Al Viro 提交于
      As it is, all instances of ->release() for files that have ->fasync()
      need to remember to evict file from fasync lists; forgetting that
      creates a hole and we actually have a bunch that *does* forget.
      
      So let's keep our lives simple - let __fput() check FASYNC in
      file->f_flags and call ->fasync() there if it's been set.  And lose that
      crap in ->release() instances - leaving it there is still valid, but we
      don't have to bother anymore.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      233e70f4
  9. 09 10月, 2008 1 次提交
  10. 16 8月, 2008 4 次提交
  11. 21 6月, 2008 2 次提交
  12. 03 5月, 2008 1 次提交
  13. 30 4月, 2008 1 次提交
  14. 08 4月, 2008 3 次提交
  15. 07 2月, 2008 1 次提交
  16. 31 1月, 2008 1 次提交
    • J
      [SCSI] remove use_sg_chaining · d3f46f39
      James Bottomley 提交于
      With the sg table code, every SCSI driver is now either chain capable
      or broken (or has sg_tablesize set so chaining is never activated), so
      there's no need to have a check in the host template.
      
      Also tidy up the code by moving the scatterlist size defines into the
      SCSI includes and permit the last entry of the scatterlist pools not
      to be a power of two.
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      d3f46f39
  17. 12 1月, 2008 4 次提交