• Shaohua Li's avatar
    raid5: get_active_stripe avoids device_lock · e240c183
    Shaohua Li authored
    For sequential workload (or request size big workload), get_active_stripe can
    find cached stripe. In this case, we always hold device_lock, which exposes a
    lot of lock contention for such workload. If stripe count isn't 0, we don't
    need hold the lock actually, since we just increase its count. And this is the
    hot code path for such workload. Unfortunately we must delete the BUG_ON.
    Signed-off-by: default avatarShaohua Li <shli@fusionio.com>
    Signed-off-by: default avatarNeilBrown <neilb@suse.de>
    e240c183
raid5.c 197 KB