[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/2] migration/rdma: Increase the backlog from 5 to 128
From: |
Pankaj Gupta |
Subject: |
Re: [PATCH 1/2] migration/rdma: Increase the backlog from 5 to 128 |
Date: |
Wed, 2 Feb 2022 07:27:53 +0100 |
> > > So it can handle more incoming requests.
> > >
> > > Signed-off-by: Jack Wang <jinpu.wang@ionos.com>
> > > ---
> > > migration/rdma.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/migration/rdma.c b/migration/rdma.c
> > > index c7c7a384875b..2e223170d06d 100644
> > > --- a/migration/rdma.c
> > > +++ b/migration/rdma.c
> > > @@ -4238,7 +4238,7 @@ void rdma_start_incoming_migration(const char
> > > *host_port, Error **errp)
> > >
> > > trace_rdma_start_incoming_migration_after_dest_init();
> > >
> > > - ret = rdma_listen(rdma->listen_id, 5);
> > > + ret = rdma_listen(rdma->listen_id, 128);
> >
> > 128 backlog seems too much to me. Any reason for choosing this number.
> > Any rationale to choose this number?
> >
> 128 is the default value of SOMAXCONN, I can use that if it is preferred.
AFAICS backlog is only applicable with RDMA iWARP CM mode. Maybe we
can increase it to 128.
Maybe you can also share any testing data for multiple concurrent live
migrations using RDMA, please.
Thanks,
Pankaj
Thanks,
Pankaj
[PATCH 2/2] migration/rdma: set the REUSEADDR option for destination, Jack Wang, 2022/02/01
Re: [PATCH 2/2] migration/rdma: set the REUSEADDR option for destination, Dr. David Alan Gilbert, 2022/02/02