summaryrefslogtreecommitdiffstats
path: root/include/linux/blk-iopoll.h
Commit message (Collapse)AuthorAgeFilesLines
* block: remove old blk_iopoll_enabled variableJens Axboe2014-03-131-2/+0
| | | | | | | | | | | | | | | | This was a debugging measure to toggle enabled/disabled when testing. But for real production setups, it's not safe to toggle this setting without either reloading drivers of quiescing IO first. Neither of which the toggle enforces. Additionally, it makes drivers deal with the conditional state. Remove it completely. It's up to the driver whether iopoll is enabled or not. Signed-off-by: Jens Axboe <axboe@fb.com>
* block: make blk_iopoll_prep_sched() follow normal 0/1 return conventionJens Axboe2009-09-111-2/+9
| | | | | | | Return 0 if we successfully marked this iopoll structure as ours for scheduling, instead of 1. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
* block: add blk-iopoll, a NAPI like approach for block devicesJens Axboe2009-09-111-0/+41
This borrows some code from NAPI and implements a polled completion mode for block devices. The idea is the same as NAPI - instead of doing the command completion when the irq occurs, schedule a dedicated softirq in the hopes that we will complete more IO when the iopoll handler is invoked. Devices have a budget of commands assigned, and will stay in polled mode as long as they continue to consume their budget from the iopoll softirq handler. If they do not, the device is set back to interrupt completion mode. This patch holds the core bits for blk-iopoll, device driver support sold separately. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
OpenPOWER on IntegriCloud