All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: "Wang, Wei W" <wei.w.wang@intel.com>
Cc: "Wang, Lei4" <lei4.wang@intel.com>,
	 "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	 "peterx@redhat.com" <peterx@redhat.com>,
	"leobras@redhat.com" <leobras@redhat.com>,
	 "Daniel Berrange" <berrange@redhat.com>
Subject: Re: [PATCH] multifd: Set a higher "backlog" default value for listen()
Date: Fri, 19 May 2023 13:32:33 +0200	[thread overview]
Message-ID: <87fs7sy2su.fsf@secure.mitica> (raw)
In-Reply-To: <DS0PR11MB63736463A526A0D1A0D64568DC7C9@DS0PR11MB6373.namprd11.prod.outlook.com> (Wei W. Wang's message of "Fri, 19 May 2023 03:33:22 +0000")

"Wang, Wei W" <wei.w.wang@intel.com> wrote:
> On Friday, May 19, 2023 10:52 AM, Wang, Lei4 wrote:
>> > We can change it to uint16_t or uint32_t, but need to see if listening
>> > on a larger value is OK to everyone.
>> 
>> Is there any use case to use >256 migration channels? If not, then I suppose
>> it's no need to increase it.
>
> People can choose to use more than 256 channels to boost performance.

See my other email, I doubt it any time soon O:-)

> If it is determined that using larger than 256 channels doesn't increase performance
> on all the existing platforms, then we need to have it reflected in the code explicitly,
> e.g. fail with errors messages when user does:
> migrate_set_parameter multifd-channels 512


(qemu) migrate_set_parameter multifd-channels 300
Error: Parameter 'multifd-channels' expects uint8_t

So I think that is working.

>> 
>> >
>> > Man page of listen mentions that the  maximum length of the queue for
>> > incomplete sockets can be set using
>> > /proc/sys/net/ipv4/tcp_max_syn_backlog,
>> > and it is 4096 by default on my machine



  reply	other threads:[~2023-05-19 11:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  8:52 [PATCH] multifd: Set a higher "backlog" default value for listen() Lei Wang
2023-05-18  9:13 ` Wang, Wei W
2023-05-18 11:44   ` Juan Quintela
2023-05-18 12:29   ` Daniel P. Berrangé
2023-05-18 12:42     ` Juan Quintela
2023-05-18 15:17       ` Wang, Wei W
2023-05-18 15:28         ` Juan Quintela
2023-05-18  9:16 ` Juan Quintela
2023-05-19  1:30   ` Wang, Lei
2023-05-19  2:44     ` Wang, Wei W
2023-05-19  2:51       ` Wang, Lei
2023-05-19  3:33         ` Wang, Wei W
2023-05-19 11:32           ` Juan Quintela [this message]
2023-05-19 11:22       ` Juan Quintela
2023-05-19 15:17         ` Peter Xu

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=87fs7sy2su.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=berrange@redhat.com \
    --cc=lei4.wang@intel.com \
    --cc=leobras@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wei.w.wang@intel.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.