diff options
author | Jens Axboe <axboe@kernel.dk> | 2018-01-10 11:30:56 -0700 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2018-01-10 11:47:43 -0700 |
commit | 76a86f9d027b342b8759a4b2f9f7fe046e284220 (patch) | |
tree | 05037d9a7d2b1057a01202fc989295e0f2ac51c2 /block/blk.h | |
parent | 5d75d3f2e736d6c8be79b677e10edb6af1bf7ed6 (diff) | |
download | linux-76a86f9d027b342b8759a4b2f9f7fe046e284220.tar.bz2 |
block: remove REQ_ATOM_POLL_SLEPT
We don't need this to be an atomic flag, it can be a regular
flag. We either end up on the same CPU for the polling, in which
case the state is sane, or we did the sleep which would imply
the needed barrier to ensure we see the right state.
Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com>
Reviewed-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk.h')
-rw-r--r-- | block/blk.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/block/blk.h b/block/blk.h index a68dbe312ea3..eb306c52121e 100644 --- a/block/blk.h +++ b/block/blk.h @@ -124,8 +124,6 @@ void blk_account_io_done(struct request *req); */ enum rq_atomic_flags { REQ_ATOM_COMPLETE = 0, - - REQ_ATOM_POLL_SLEPT, }; /* |