All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Pankaj Gupta <pankaj.gupta@ionos.com>
Cc: Jinpu Wang <jinpu.wang@ionos.com>,
	qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [PATCH 1/2] migration/rdma: Increase the backlog from 5 to 128
Date: Wed, 2 Feb 2022 09:20:03 +0000	[thread overview]
Message-ID: <YfpMw1yvYUHkIMqV@work-vm> (raw)
In-Reply-To: <CALzYo31esyL6pZ+LCy4qAGw9AZPj4ZdRpxLAxO9uYWzrQ63N2A@mail.gmail.com>

* Pankaj Gupta (pankaj.gupta@ionos.com) wrote:
> > > > >  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.these many
> 
> Or maybe we first increase it to 20 or 32? or so to avoid memory
> overhead if we are not
> using these many connections at the same time.

Can you explain why you're requiring more than 1?  Is this with multifd
patches?

Dave

> > Maybe you can also share any testing data for multiple concurrent live
> > migrations using RDMA, please.
> >
> > Thanks,
> > Pankaj
> >
> > Thanks,
> > Pankaj
> 
-- 
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK



  reply	other threads:[~2022-02-02  9:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 15:11 [PATCH 1/2] migration/rdma: Increase the backlog from 5 to 128 Jack Wang
2022-02-01 15:11 ` [PATCH 2/2] migration/rdma: set the REUSEADDR option for destination Jack Wang
2022-02-01 18:39   ` Pankaj Gupta
2022-02-01 20:43     ` Jinpu Wang
2022-02-02  4:57       ` Pankaj Gupta
2022-02-02 10:15   ` Dr. David Alan Gilbert
2022-02-02 10:51     ` Jinpu Wang
2022-02-01 18:19 ` [PATCH 1/2] migration/rdma: Increase the backlog from 5 to 128 Pankaj Gupta
2022-02-01 20:32   ` Jinpu Wang
2022-02-02  6:27     ` Pankaj Gupta
2022-02-02  6:37       ` Pankaj Gupta
2022-02-02  9:20         ` Dr. David Alan Gilbert [this message]
2022-02-02  9:55           ` Jinpu Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YfpMw1yvYUHkIMqV@work-vm \
    --to=dgilbert@redhat.com \
    --cc=jinpu.wang@ionos.com \
    --cc=pankaj.gupta@ionos.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.