> This allow address could be reused to avoid rdma_bind_addr error
> out.
Seems we are proposing to allow multiple connections on same source ip
port pair?
>
> Signed-off-by: Jack Wang <jinpu.w...@ionos.com>
> ---
> migration/rdma.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/migration/rdma.c b/migration/rdma.c
> index 2e223170d06d..b498ef013c77 100644
> --- a/migration/rdma.c
> +++ b/migration/rdma.c
> @@ -2705,6 +2705,7 @@ static int qemu_rdma_dest_init(RDMAContext *rdma, Error
> **errp)
> char ip[40] = "unknown";
> struct rdma_addrinfo *res, *e;
> char port_str[16];
> + int reuse = 1;
>
> for (idx = 0; idx < RDMA_WRID_MAX; idx++) {
> rdma->wr_data[idx].control_len = 0;
> @@ -2740,6 +2741,12 @@ static int qemu_rdma_dest_init(RDMAContext *rdma,
> Error **errp)
> goto err_dest_init_bind_addr;
> }
>
> + ret = rdma_set_option(listen_id, RDMA_OPTION_ID,
> RDMA_OPTION_ID_REUSEADDR,
> + &reuse, sizeof reuse);
maybe we can just write '1' directly on the argument list of 'rdma_set_option'.
Assuming reuseaddr does not effect core rdma transport? change seems ok to me.
Thanks,
Pankaj
> + if (ret) {
> + ERROR(errp, "Error: could not set REUSEADDR option");
> + goto err_dest_init_bind_addr;
> + }
> for (e = res; e != NULL; e = e->ai_next) {
> inet_ntop(e->ai_family,
> &((struct sockaddr_in *) e->ai_dst_addr)->sin_addr, ip, sizeof
> ip);
> --
> 2.25.1
>
