linux-stable.git/drivers/lightnvm, branch v4.16.2

lightnvm: pblk: refactor pblk_ppa_comp function

2018-01-05T15:50:12+00:00

Shorten function to simply return the value of the if statement.

Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: pblk: add iostat support

2018-01-05T15:50:12+00:00

Since pblk registers its own block device, the iostat accounting is
not automatically done for us. Therefore, add the necessary
accounting logic to satisfy the iostat interface.

Signed-off-by: Javier González 
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: pblk: print instance name on instance info

2018-01-05T15:50:12+00:00

Add the instance name to the information printed out on target creation.

Signed-off-by: Javier González 
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: pblk: free write buffer on init failure

2018-01-05T15:50:12+00:00

Refactor the way we free the write buffer to ensure that all entries get
freed in case of an error on the init sequence.

Signed-off-by: Javier González 
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: pblk: ensure kthread alloc. before kicking it

2018-01-05T15:50:12+00:00

When creating the write thread, ensure that the kthread has been created
before initializing the timer responsible from kicking it. Otherwise, if
the kthread creation fails or gets killed from used space, we risk
kicking an empty thread structure.

Also, since the kthread creation can be interrupted form user space,
adapt the error path to not report an error when this happens, since it
is intentional that the instance creation is aborted.

Signed-off-by: Javier González 
Updated source to reflect the new timer_setup API.
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: pblk: do not log recovery read errors

2018-01-05T15:50:12+00:00

On scan recovery, reads can fail. This happens because the first page
for each line is read in order to determined if the line has been used
(and thus needs to be recovered), or not. This can lead to "empty page"
read errors.

Since these errors are normal, do not log them, as they are confusing
when reviewing the logs.

Signed-off-by: Javier González 
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: pblk: ignore high ecc errors on recovery

2018-01-05T15:50:12+00:00

On recovery, do not stop L2P recovery if reads report high ECC error
as the data is still available.

Signed-off-by: Javier González 
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: set target over-provision on create ioctl

2018-01-05T15:50:12+00:00

Allow to set the over-provision percentage on target creation. In case
that the value is not provided, fall back to the default value set by
the target.

In pblk, set the default OP to 11% of the total size of the device

Signed-off-by: Javier González 
Signed-off-by: Hans Holmberg 
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: pblk: use exact free block counter in RL

2018-01-05T15:50:12+00:00

Until now, pblk's rate-limiter has used a heuristic to reserve space for
GC I/O given that the over-provision area was fixed.

In preparation for allowing to define the over-provision area on target
creation, define a dedicated free_block counter in the rate-limiter to
track the number of blocks being used for user data.

Signed-off-by: Javier González 
Signed-off-by: Hans Holmberg 
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: pblk: remove pblk_gc_stop

2018-01-05T15:50:12+00:00

pblk_gc_stop just sets pblk->gc->gc_active to zero, ignoring
the flush parameter. This is plain confusing, so remove the
function and set the gc active flag at the call points instead.

Signed-off-by: Hans Holmberg 
Signed-off-by: Javier González 
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe