Jim Harris 72da9b7562 reduce: use consistent callback names ... There are a sequence of operations needed for both read and write I/O. For example, on a write I/O, we may need to do a read, modify the chunk, then write the data back to disk. For read I/O, the name of the callback is _read_read_done - the first "read" indicates the I/O type, the second "read" indicates the disk read part of the sequence. The write I/O steps aren't using this same naming convention, so change that here. This will be important in upcoming patches where we'll be adding compress/decompress steps into the I/O pipeline - having a consistent naming strategy will make the code easier to follow. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Icd525874918378118d807acdbe5dd42d5be03126 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/449258 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>		2019-03-28 03:45:29 +00:00
..
Makefile	lib/reduce: add empty library, include, unit tests	2018-11-07 18:11:49 +00:00
reduce.c	reduce: use consistent callback names	2019-03-28 03:45:29 +00:00