fae0356697
A previous fix for miscompare had a slight issue with the scenario where we chose an offset and then discover that it's already taken because we've wrapped to this location before the previous IO completed. In such case, we intended to bump the offset to just go to the next block however we only bumped the local variable so the next IO submitted will overwrite the previous. The fix is simply to use the previously incremented target->offset and increment it again for the next IO. Signed-off-by: paul luse <paul.e.luse@intel.com> Change-Id: I26661eb0631ac50cc4f86f42f1d1789d297e204d Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1250 Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| bdevperf.c | ||
| bdevperf.py | ||
| Makefile | ||