summaryrefslogtreecommitdiffstats
path: root/fs/cachefiles
diff options
context:
space:
mode:
authorJavier González <javier@javigon.com>2018-10-09 13:12:11 +0200
committerJens Axboe <axboe@kernel.dk>2018-10-09 08:25:08 -0600
commitd672d92d9c433c365fd6cdb4da1c02562b5f1178 (patch)
tree042e915cb46e7dfffa3261f82969cb7c9089b886 /fs/cachefiles
parent9bd1f875c047a8a619a3e5233c1eb23eace02f31 (diff)
downloadlinux-d672d92d9c433c365fd6cdb4da1c02562b5f1178.tar.bz2
lightnvm: pblk: guarantee mw_cunits on read buffer
OCSSD 2.0 defines the amount of data that the host must buffer per chunk to guarantee reads through the geometry field mw_cunits. This value is the base that pblk uses to determine the size of its read buffer. Currently, this size is set to be the closes power-of-2 to mw_cunits times the number of parallel units available to the pblk instance for each open line (currently one). When an entry (4KB) is put in the buffer, the L2P table points to it. As the buffer wraps up, the L2P is updated to point to addresses on the device, thus guaranteeing mw_cunits at a chunk level. However, given that pblk cannot write to the device under ws_min (normally ws_opt), there might be a window in which the buffer starts wrapping up and updating L2P entries before the mw_cunits value in a chunk has been surpassed. In order not to violate the mw_cunits constrain in this case, account for ws_opt on the read buffer creation. Signed-off-by: Javier González <javier@cnexlabs.com> Signed-off-by: Matias Bjørling <mb@lightnvm.io> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs/cachefiles')
0 files changed, 0 insertions, 0 deletions