1. 05 1月, 2011 1 次提交
    • J
      [S390] qdio: outbound tasklet scan threshold · 3d6c76ff
      Jan Glauber 提交于
      Introduce a scan treshold for the qdio outbound queues. By setting the
      threshold the driver can tell qdio after how much used SBALs qdio
      should schedule the outbound tasklet that scans the queue for finished
      SBALs. The threshold is specific by the drivers because a
      Hipersockets device is much faster in utilizing outbound buffers than a
      ZFCP or OSA device.
      
      The default values after how many used SBALs the tasklet should run are:
      
      OSA:          > 31 SBALs
      Hipersockets: > 7 SBALs
      zfcp:         > 55 SBALs
      Signed-off-by: NJan Glauber <jang@linux.vnet.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      3d6c76ff
  2. 09 9月, 2010 1 次提交
  3. 28 7月, 2010 1 次提交
  4. 17 5月, 2010 1 次提交
  5. 08 3月, 2010 1 次提交
  6. 27 2月, 2010 1 次提交
  7. 22 6月, 2009 1 次提交
  8. 26 3月, 2009 1 次提交
    • J
      [S390] qdio: report SIGA errors directly · d303b6fd
      Jan Glauber 提交于
      Errors from SIGA instructions are stored in the per queue qdio_error
      and reported back when the queue handler is called. That opens a race
      when multiple error conditions occur simultanously.
      
      Report SIGA errors immediately in the return value of do_QDIO so the
      upper layer can react and SIGA errors no longer interfere with other
      errors.
      
      Move the SIGA error handling in qeth from the outbound handler to
      qeth_flush_buffers.
      Signed-off-by: NJan Glauber <jang@linux.vnet.ibm.com>
      d303b6fd
  9. 25 12月, 2008 1 次提交
  10. 11 10月, 2008 1 次提交
  11. 02 8月, 2008 1 次提交
  12. 17 7月, 2008 1 次提交
  13. 29 4月, 2008 1 次提交
  14. 26 1月, 2008 1 次提交
  15. 08 5月, 2007 1 次提交
  16. 16 12月, 2006 1 次提交
  17. 04 10月, 2006 1 次提交
  18. 02 2月, 2006 1 次提交
  19. 07 1月, 2006 1 次提交
  20. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4