DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Matan Azrad <matan@mellanox.com>,
	Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org, Xueming Li <xuemingl@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] common/mlx5: add virtio queue protection domain
Date: Fri, 19 Jun 2020 08:01:53 +0200	[thread overview]
Message-ID: <32e4e2da-ca5a-0db6-2cb2-45f47a8ac53f@redhat.com> (raw)
In-Reply-To: <685db593-9ee3-a2d1-fbd6-6621e5e29fb1@redhat.com>

Hi Ferruh,

On 6/18/20 6:30 PM, Maxime Coquelin wrote:
> 
> 
> On 6/2/20 5:51 PM, Matan Azrad wrote:
>> Starting from FW version 22.27.4002, it is required to configure
>> protection domain (PD) for each virtq created by DevX.
>>
>> Add PD requirement in virtq DevX APIs.
>>
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Matan Azrad <matan@mellanox.com>
>> Signed-off-by: Xueming Li <xuemingl@mellanox.com>
>> ---
>>  drivers/common/mlx5/mlx5_devx_cmds.c | 1 +
>>  drivers/common/mlx5/mlx5_devx_cmds.h | 1 +
>>  drivers/common/mlx5/mlx5_prm.h       | 4 +++-
>>  3 files changed, 5 insertions(+), 1 deletion(-)
>>
> 
> 
> Applied to dpdk-next-virtio/master


Finally not, this version has also been superseded.
I removed it from my tree.

Maxime

> Thanks,
> Maxime
> 


  reply	other threads:[~2020-06-19  6:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 15:51 Matan Azrad
2020-06-02 15:51 ` [dpdk-dev] [PATCH 2/2] vdpa/mlx5: adjust " Matan Azrad
2020-06-18 14:59   ` Maxime Coquelin
2020-06-18 15:13   ` Maxime Coquelin
2020-06-18 16:30   ` Maxime Coquelin
2020-06-18 14:56 ` [dpdk-dev] [PATCH 1/2] common/mlx5: add " Maxime Coquelin
2020-06-18 16:30 ` Maxime Coquelin
2020-06-19  6:01   ` Maxime Coquelin [this message]
2020-06-19  6:20     ` Maxime Coquelin

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=32e4e2da-ca5a-0db6-2cb2-45f47a8ac53f@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=matan@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@mellanox.com \
    --cc=xuemingl@mellanox.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).