diff options
author | 2018-12-11 20:16:13 +0100 | |
---|---|---|
committer | 2018-12-11 12:22:33 -0700 | |
commit | 3bcebc5bac0935d662f30d317e33ffa660bebf93 (patch) | |
tree | a253b85173c905425e6dc5bcdd285399faa2419f /tools/perf/scripts/python/export-to-postgresql.py | |
parent | lightnvm: pblk: stop writes gracefully when running out of lines (diff) | |
download | wireguard-linux-3bcebc5bac0935d662f30d317e33ffa660bebf93.tar.xz wireguard-linux-3bcebc5bac0935d662f30d317e33ffa660bebf93.zip |
lightnvm: pblk: set conservative threshold for user writes
In a worst-case scenario (random writes), OP% of sectors
in each line will be invalid, and we will then need
to move data out of 100/OP% lines to free a single line.
So, to prevent the possibility of running out of lines,
temporarily block user writes when there is less than
100/OP% free lines.
Also ensure that pblk creation does not produce instances
with insufficient over provisioning.
Insufficient over-provising is not a problem on real hardware,
but often an issue when running QEMU simulations (with few lines).
100 lines is enough to create a sane instance with the standard
(11%) over provisioning.
Signed-off-by: Hans Holmberg <hans.holmberg@cnexlabs.com>
Reviewed-by: Javier González <javier@javigon.com>
Signed-off-by: Matias Bjørling <mb@lightnvm.io>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions