summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorOmar Sandoval <osandov@fb.com>2016-09-17 21:20:54 +0200
committerJens Axboe <axboe@fb.com>2016-09-17 21:39:06 +0200
commit5c64a8df0ca88c79c9cb74674c2481e5f7ede511 (patch)
treea10aa8ab518921ee8f16511076a15ff2b64e52ec /kernel
parentsbitmap: re-initialize allocation hints after resize (diff)
downloadlinux-5c64a8df0ca88c79c9cb74674c2481e5f7ede511.tar.xz
linux-5c64a8df0ca88c79c9cb74674c2481e5f7ede511.zip
sbitmap: don't update the allocation hint on clear after resize
If we have a bunch of high-numbered bits allocated and then we resize the struct sbitmap_queue, when those bits get cleared, we'll update the hint and then have to re-randomize it repeatedly. Avoid that by checking that the cleared bit is still a valid hint. No measurable performance difference in the common case. Signed-off-by: Omar Sandoval <osandov@fb.com> Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions