0bfaaace8f
Purpose: With this patch, (1)We can support using different sock implementations in one application together. (2)For one IP address managed by kernel, we can use different method to listen/connect, e.g., posix, or uring. With this patch, we can designate the specified sock implementation if impl_name is not NULL and valid. Otherwise, spdk_sock_listen/connect will try to use the sock implementations in the list by order if impl_name is NULL. Without this patch, the app will always use the same type of sock implementation if the order is fixed. For example, if we have posix and uring together, the first one will always be uring. Signed-off-by: Ziye Yang <ziye.yang@intel.com> Change-Id: Ic49563f5025085471d356798e522ff7ab748f586 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478140 Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> |
||
|---|---|---|
| .. | ||
| hello_world | ||
| Makefile | ||