Alexey Marchuk 48f38636ce tcp: Cleanup nvme_tcp_pdu structure ... With the recent changes which added usage of writev_async to both TCP target and initiator, nvme_tcp_pdu::writev_offset becomes useless since it is not updated in data path. This field is only used in UT. Remove this field from nvme_tcp_pdu structure, now nvme_tcp_build_iovs builds iov which fully describes the PDU. Update UT accordingly. Field padding_valid_bytes is not used at all, delete it too Change-Id: I2d6040ae64d6847cb455f59f65ec5677de8e5192 Signed-off-by: Alexey Marchuk <alexeymar@mellanox.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/483374 Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>		2020-02-04 18:18:49 +00:00
..
.gitignore	nvme/tcp: add unit test to verify the bug in nvmf_tcp_pdu_set_data_buf	2019-07-01 08:28:20 +00:00
Makefile	nvme/tcp: add unit test to verify the bug in nvmf_tcp_pdu_set_data_buf	2019-07-01 08:28:20 +00:00
nvme_tcp_ut.c	tcp: Cleanup nvme_tcp_pdu structure	2020-02-04 18:18:49 +00:00