05dc895bea
When entering the if case to order the list, there is bug should be fixed. The original code does not address this. The way this happens is when there is a connection left in the socks_with_data list between polls and there are enough new events detected that it would exceed the maximal number of events. A connection is left on this list between polls if it isn't fully drained via reads by the upper layer on each poll loop. Currently, the maximal socket event num is 32. Then we did not hit this issue in our normal test cases. But when you use NVMe-oF tcp target to test which is described in #2105, there are more than 32 active sockets, and it exceeeds the maximal num of events of polling (32), so we will trigger this issue. Fixes issue #2015 Change-Id: I9384476fdba8826f5fe55a5d2594e3f4ed3832ba Signed-off-by: Ziye Yang <ziye.yang@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8541 Community-CI: Mellanox Build Bot Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
|---|---|---|
| .. | ||
| accel | ||
| bdev | ||
| blob | ||
| blobfs | ||
| env_dpdk | ||
| event | ||
| sock | ||
| Makefile | ||