From: Juan Quintela <quintela@redhat.com>
To: "Wang, Wei W" <wei.w.wang@intel.com>
Cc: "Daniel P.Berrangé" <berrange@redhat.com>,
"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>
Subject: Re: [PATCH] multifd: Set a higher "backlog" default value for listen()
Date: Thu, 18 May 2023 17:28:19 +0200 [thread overview]
Message-ID: <87sfbtbqwc.fsf@secure.mitica> (raw)
In-Reply-To: <DS0PR11MB6373526303940FC5D9892BABDC7F9@DS0PR11MB6373.namprd11.prod.outlook.com> (Wei W. Wang's message of "Thu, 18 May 2023 15:17:08 +0000")
"Wang, Wei W" <wei.w.wang@intel.com> wrote:
> On Thursday, May 18, 2023 8:43 PM, Juan Quintela wrote:
>>
>>
>> Are you using -incoming defer?
>>
>> No? right.
>>
>> With multifd, you should use -incoming defer.
>
> Yes, just confirmed that it works well with deferred incoming.
> I think we should enforce this kind of requirement in the code.
> I'll make a patch for this.
Actually, we should deprecate everything except defer.
Later, Juan.
next prev parent reply other threads:[~2023-05-18 15:28 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 [this message]
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
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=87sfbtbqwc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).