DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Adrian Moreno <amorenoz@redhat.com>, dev@dpdk.org
Cc: chenbo.xia@intel.com, zhihong.wang@intel.com,
	xiao.w.wang@intel.com, maxime.coquelin@redhat.com
Subject: Re: [dpdk-dev] [PATCH v4 0/2] net/virtio: add vhost-user protocol features support
Date: Wed, 8 Jul 2020 12:28:33 +0100	[thread overview]
Message-ID: <6e6bf325-7f41-145a-f1f9-bdc83b527602@intel.com> (raw)
In-Reply-To: <20200703155727.1320821-1-amorenoz@redhat.com>

On 7/3/2020 4:57 PM, Adrian Moreno wrote:
> This series adds Vhost-user protocol features support
> to Virtio-user PMD's Vhost-user backend.
> 
> The first patch introduces protocol features
> negotiation, and the second one reply-ack feature.
> 
> ---
> Changes since v3:
> - [Chenbo] Do not process MQ if VHOST_USER_F_PROTOCOL_FEATURES is
>   unsupported
> 
> Changes since v2:
> - Added the new vhost-user messages to vhost_msg_strings[]
> 
> Changes since v1:
> - Rebased on top of virtio-next
> - Dropped patch 3 as it depends on a new SET_STATUS request being
> merged into Qemu. Will submit independently.
> - [Chenbo] Do not send SET_PROTOCOL_FEATURES request if not supported by
>   backend
> 
> 
> Maxime Coquelin (2):
>   net/virtio: add vhost-user protocol features support
>   net/virtio: add reply-ack support to Virtio-user
> 

Reviewed-by: Chenbo Xia <chenbo.xia@intel.com>

Series applied to dpdk-next-net/master, thanks.

      parent reply	other threads:[~2020-07-08 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03 15:57 Adrian Moreno
2020-07-03 15:57 ` [dpdk-dev] [PATCH v4 1/2] " Adrian Moreno
2020-07-05 13:52   ` Xia, Chenbo
2020-07-03 15:57 ` [dpdk-dev] [PATCH v4 2/2] net/virtio: add reply-ack support to Virtio-user Adrian Moreno
2020-07-05 13:53   ` Xia, Chenbo
2020-07-08 11:28 ` Ferruh Yigit [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=6e6bf325-7f41-145a-f1f9-bdc83b527602@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=amorenoz@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=xiao.w.wang@intel.com \
    --cc=zhihong.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).