block: unify request timeout handling
Right now SCSI and others do their own command timeout handling. Move those bits to the block layer. Instead of having a timer per command, we try to be a bit more clever and simply have one per-queue. This avoids the overhead of having to tear down and setup a timer for each command, so it will result in a lot less timer fiddling. Signed-off-by:Mike Anderson <andmike@linux.vnet.ibm.com> Signed-off-by:
Jens Axboe <jens.axboe@oracle.com>
Showing
- block/Makefile 2 additions, 2 deletionsblock/Makefile
- block/blk-core.c 7 additions, 0 deletionsblock/blk-core.c
- block/blk-settings.c 12 additions, 0 deletionsblock/blk-settings.c
- block/blk-softirq.c 18 additions, 12 deletionsblock/blk-softirq.c
- block/blk-timeout.c 155 additions, 0 deletionsblock/blk-timeout.c
- block/blk.h 24 additions, 0 deletionsblock/blk.h
- block/elevator.c 8 additions, 0 deletionsblock/elevator.c
- drivers/ata/libata-eh.c 7 additions, 6 deletionsdrivers/ata/libata-eh.c
- drivers/ata/libata.h 1 addition, 1 deletiondrivers/ata/libata.h
- drivers/scsi/aacraid/aachba.c 1 addition, 1 deletiondrivers/scsi/aacraid/aachba.c
- drivers/scsi/gdth.c 38 additions, 22 deletionsdrivers/scsi/gdth.c
- drivers/scsi/gdth.h 1 addition, 1 deletiondrivers/scsi/gdth.h
- drivers/scsi/gdth_proc.c 0 additions, 66 deletionsdrivers/scsi/gdth_proc.c
- drivers/scsi/gdth_proc.h 0 additions, 3 deletionsdrivers/scsi/gdth_proc.h
- drivers/scsi/ibmvscsi/ibmvscsi.c 1 addition, 1 deletiondrivers/scsi/ibmvscsi/ibmvscsi.c
- drivers/scsi/ide-scsi.c 1 addition, 1 deletiondrivers/scsi/ide-scsi.c
- drivers/scsi/ipr.c 2 additions, 1 deletiondrivers/scsi/ipr.c
- drivers/scsi/ips.c 1 addition, 1 deletiondrivers/scsi/ips.c
- drivers/scsi/libiscsi.c 9 additions, 8 deletionsdrivers/scsi/libiscsi.c
- drivers/scsi/libsas/sas_ata.c 1 addition, 1 deletiondrivers/scsi/libsas/sas_ata.c
Please register or sign in to comment