dm: use unlocked variants of queue flag check/set
authorJens Axboe <jens.axboe@oracle.com>
Tue, 29 Apr 2008 17:12:35 +0000 (19:12 +0200)
committerLinus Torvalds <torvalds@linux-foundation.org>
Tue, 29 Apr 2008 17:21:12 +0000 (10:21 -0700)
dm.c already provides mutual exclusion through ->map_lock.

Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
drivers/md/dm-table.c

index 73326e7c54bfccbf7ba6122b4252ae003bf75e28..94116eaf47099ccad9f8ca458afd3c4f1e835435 100644 (file)
@@ -873,13 +873,11 @@ void dm_table_set_restrictions(struct dm_table *t, struct request_queue *q)
        q->max_hw_sectors = t->limits.max_hw_sectors;
        q->seg_boundary_mask = t->limits.seg_boundary_mask;
        q->bounce_pfn = t->limits.bounce_pfn;
-       /* XXX: the below will probably go bug. must ensure there can be no
-        * concurrency on queue_flags, and use the unlocked versions...
-        */
+
        if (t->limits.no_cluster)
-               queue_flag_clear(QUEUE_FLAG_CLUSTER, q);
+               queue_flag_clear_unlocked(QUEUE_FLAG_CLUSTER, q);
        else
-               queue_flag_set(QUEUE_FLAG_CLUSTER, q);
+               queue_flag_set_unlocked(QUEUE_FLAG_CLUSTER, q);
 
 }