From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: bluca@debian.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v16.11 LTS] vhost: avoid concurrency when logging dirty pages
Date: Wed, 18 Apr 2018 17:10:49 +0200 [thread overview]
Message-ID: <397a2dee-db89-318a-6b51-be0f01be4e34@redhat.com> (raw)
In-Reply-To: <20180418072408.18143-1-maxime.coquelin@redhat.com>
On 04/18/2018 09:24 AM, Maxime Coquelin wrote:
> [ backported from upstream commit 394313fff39d0f994325c47f7eab39daf5dc9e11 ]
>
> This patch aims at fixing a migration performance regression
> faced since atomic operation is used to log pages as dirty when
> doing live migration.
>
> Instead of setting a single bit by doing an atomic read-modify-write
> operation to log a page as dirty, this patch write 0xFF to the
> corresponding byte, and so logs 8 page as dirty.
>
> The advantage is that it avoids concurrent atomic operations by
> multiple PMD threads, the drawback is that some clean pages are
> marked as dirty and so are transferred twice.
>
> Fixes: 6bf02ab821fb ("vhost: make page logging atomic")
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
>
> Conflicts:
> lib/librte_vhost/vhost.h
> ---
>
> Hi Luca,
>
> This patch is backported from upstream master,
> I propose it as the backport requires some conflicts to be fixed.
>
> Cheers,
> Maxime
>
Hi Luca,
Please don't apply the patch, I have just been made aware by QE that
migration with more than one queue pair never converges, so I need to
rework it.
Cheers,
Maxime
prev parent reply other threads:[~2018-04-18 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 7:24 Maxime Coquelin
2018-04-18 15:10 ` Maxime Coquelin [this message]
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=397a2dee-db89-318a-6b51-be0f01be4e34@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=bluca@debian.org \
--cc=stable@dpdk.org \
/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).