qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Hao Xiang <hao.xiang@bytedance.com>
Cc: Shivam Kumar <shivam.kumar1@nutanix.com>,
	"farosas@suse.de" <farosas@suse.de>,
	"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"marcandre.lureau@redhat.com" <marcandre.lureau@redhat.com>,
	"bryan.zhang@bytedance.com" <bryan.zhang@bytedance.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [External] Re: [PATCH v3 13/20] migration/multifd: Prepare to introduce DSA acceleration on the multifd path.
Date: Fri, 2 Feb 2024 18:03:04 +0800	[thread overview]
Message-ID: <Zby92DfN6a7NWgvu@x1n> (raw)
In-Reply-To: <CAAYibXjRaqPaTiPPL0AhK4BP2acOYJE1sr38G12saQwrZuihZw@mail.gmail.com>

On Mon, Jan 22, 2024 at 04:37:09PM -0800, Hao Xiang wrote:
> > > +static void set_normal_pages(MultiFDSendParams *p)
> > > +{
> > > +    for (int i = 0; i < p->pages->num; i++) {
> > > +        p->batch_task->results[i] = false;
> > > +    }
> > > +}
> > Please correct me if I am wrong but set_normal_pages will not be a part of the final patch, right? They are there for testing out the performance against different zero page ration scenarios. If it’s so, can we isolate these parts into a separate patch.
> 
> set_normal_pages is used for performance testing and testing only. It
> won't introduce any "incorrect" behavior and I would love to see it
> being part of the upstream code. But the argument that testing change
> should remain private is always correct. So I am totally OK with
> isolating the parts into a separate patch.

IMHO we can allow that to be production code; as long as the new zeropage
detection parameter can allow user to choose "none" (as I mentioned in
another reply), then it's not a test code only but allow the user to
disable zeropage detections when the user wants.  Thanks,

-- 
Peter Xu



  reply	other threads:[~2024-02-02 10:04 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04  0:44 [PATCH v3 00/20] Use Intel DSA accelerator to offload zero page checking in multifd live migration Hao Xiang
2024-01-04  0:44 ` [PATCH v3 01/20] multifd: Add capability to enable/disable zero_page Hao Xiang
2024-01-08 20:39   ` Fabiano Rosas
2024-01-11  5:47     ` [External] " Hao Xiang
2024-01-15  6:02   ` Shivam Kumar
2024-01-23  0:33     ` [External] " Hao Xiang
2024-01-23 15:10       ` Fabiano Rosas
2024-01-23 21:00         ` Hao Xiang
2024-02-01  4:27         ` Peter Xu
2024-01-04  0:44 ` [PATCH v3 02/20] multifd: Support for zero pages transmission Hao Xiang
2024-01-04  0:44 ` [PATCH v3 03/20] multifd: Zero " Hao Xiang
2024-01-15  7:01   ` Shivam Kumar
2024-01-23  0:46     ` [External] " Hao Xiang
2024-02-01  5:22   ` Peter Xu
2024-02-01 23:24     ` [External] " Hao Xiang
2024-01-04  0:44 ` [PATCH v3 04/20] So we use multifd to transmit zero pages Hao Xiang
2024-01-04  0:44 ` [PATCH v3 05/20] meson: Introduce new instruction set enqcmd to the build system Hao Xiang
2024-01-04  0:44 ` [PATCH v3 06/20] util/dsa: Add dependency idxd Hao Xiang
2024-02-01  5:34   ` Peter Xu
2024-01-04  0:44 ` [PATCH v3 07/20] util/dsa: Implement DSA device start and stop logic Hao Xiang
2024-01-04  0:44 ` [PATCH v3 08/20] util/dsa: Implement DSA task enqueue and dequeue Hao Xiang
2024-01-04  0:44 ` [PATCH v3 09/20] util/dsa: Implement DSA task asynchronous completion thread model Hao Xiang
2024-01-04  0:44 ` [PATCH v3 10/20] util/dsa: Implement zero page checking in DSA task Hao Xiang
2024-01-04  0:44 ` [PATCH v3 11/20] util/dsa: Implement DSA task asynchronous submission and wait for completion Hao Xiang
2024-03-08 10:10   ` Jonathan Cameron via
     [not found]     ` <CAAYibXhSdeTod4VNyE5ZsZAjQteRdBZEhh5UieNs8s6Ji+X5og@mail.gmail.com>
2024-03-08 21:50       ` [External] " hao.xiang
2024-01-04  0:44 ` [PATCH v3 12/20] migration/multifd: Add new migration option for multifd DSA offloading Hao Xiang
2024-01-04  0:44 ` [PATCH v3 13/20] migration/multifd: Prepare to introduce DSA acceleration on the multifd path Hao Xiang
2024-01-15  6:46   ` Shivam Kumar
2024-01-23  0:37     ` [External] " Hao Xiang
2024-02-02 10:03       ` Peter Xu [this message]
2024-01-04  0:44 ` [PATCH v3 14/20] migration/multifd: Enable DSA offloading in multifd sender path Hao Xiang
2024-01-04  0:44 ` [PATCH v3 15/20] migration/multifd: Add test hook to set normal page ratio Hao Xiang
2024-02-01  5:24   ` Peter Xu
2024-02-01 23:10     ` [External] " Hao Xiang
2024-01-04  0:44 ` [PATCH v3 16/20] migration/multifd: Enable set normal page ratio test hook in multifd Hao Xiang
2024-01-04  0:44 ` [PATCH v3 17/20] migration/multifd: Add migration option set packet size Hao Xiang
2024-01-04  0:44 ` [PATCH v3 18/20] migration/multifd: Enable set packet size migration option Hao Xiang
2024-01-04  0:44 ` [PATCH v3 19/20] util/dsa: Add unit test coverage for Intel DSA task submission and completion Hao Xiang
2024-01-04  0:44 ` [PATCH v3 20/20] migration/multifd: Add integration tests for multifd with Intel DSA offloading Hao Xiang
2024-03-08  1:47 ` [PATCH v3 00/20] Use Intel DSA accelerator to offload zero page checking in multifd live migration liulongfang via

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=Zby92DfN6a7NWgvu@x1n \
    --to=peterx@redhat.com \
    --cc=bryan.zhang@bytedance.com \
    --cc=farosas@suse.de \
    --cc=hao.xiang@bytedance.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shivam.kumar1@nutanix.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).