From: Luca Boccassi <bluca@debian.org>
To: Adrian Moreno <amorenoz@redhat.com>, stable@dpdk.org
Cc: maxime.coquelin@redhat.com
Subject: Re: [dpdk-stable] [PATCH 17.11 0/2] Backport GPA dirty page logging
Date: Thu, 09 Jan 2020 19:40:48 +0000 [thread overview]
Message-ID: <53529fbc3e1b3ad52a9f2b9c08e6ea2d3418348b.camel@debian.org> (raw)
In-Reply-To: <20200109175842.24905-1-amorenoz@redhat.com>
On Thu, 2020-01-09 at 18:58 +0100, Adrian Moreno wrote:
> The backport had the following conflicts:
>
> 094b643d9b vhost: un-inline dirty pages logging functions
> lib/librte_vhost/vhost.h: Because b473ec1131ee has not been
> backported the rte_smp_wmb() is still assumed to be called before
> calling vhost_log_cache_sync(). So, remove (from destination:
> vhost.c) to avoid calling the barrier twice
>
> 1fc3b3f06a vhost: convert buffer addresses to GPA for logging
> lib/librte_vhost/vdpa.c: Deleted file
> lib/librte_vhost/vhost.c: Positional conflict for not having
> 084fac96ca
> lib/librte_vhost/virtio-net.c: The RX paths differ a lot but the
> changes are simple, use the new iova-aware logging functions
>
> Adrian Moreno (1):
> vhost: convert buffer addresses to GPA for logging
>
> Maxime Coquelin (1):
> vhost: un-inline dirty pages logging functions
>
> lib/librte_vhost/rte_vhost.h | 2 +-
> lib/librte_vhost/vhost.c | 174
> ++++++++++++++++++++++++++++++++++
> lib/librte_vhost/vhost.h | 161 ++++++++-----------------------
> lib/librte_vhost/virtio_net.c | 18 ++--
> 4 files changed, 227 insertions(+), 128 deletions(-)
>
Thanks, applied
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2020-01-09 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 17:58 Adrian Moreno
2020-01-09 17:58 ` [dpdk-stable] [PATCH 17.11 1/2] vhost: un-inline dirty pages logging functions Adrian Moreno
2020-01-09 17:58 ` [dpdk-stable] [PATCH 17.11 2/2] vhost: convert buffer addresses to GPA for logging Adrian Moreno
2020-01-09 19:40 ` Luca Boccassi [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=53529fbc3e1b3ad52a9f2b9c08e6ea2d3418348b.camel@debian.org \
--to=bluca@debian.org \
--cc=amorenoz@redhat.com \
--cc=maxime.coquelin@redhat.com \
--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).