DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Chas Williams <3chas3@gmail.com>, dev@dpdk.org
Cc: mtetsuyah@gmail.com, yliu@fridaylinux.org,
	Robert Shearman <robert.shearman@att.com>,
	stable@dpdk.org, Chas Williams <chas3@att.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/vhost: set the vq consistently
Date: Wed, 11 Apr 2018 17:02:11 +0200	[thread overview]
Message-ID: <d29aab4d-3222-ccb7-9c45-94c9d64be91a@redhat.com> (raw)
In-Reply-To: <6ec8aef7-4eac-811b-b520-47ca50206665@redhat.com>



On 04/11/2018 04:46 PM, Maxime Coquelin wrote:
> 
> 
> On 03/29/2018 06:05 PM, Chas Williams wrote:
>> From: Robert Shearman <robert.shearman@att.com>
>>
>> The vid and port of the vq were only set on queues created during initial
>> device setup.
>>
>> Fixes: ee584e9710b9 ("vhost: add driver on top of the library")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Robert Shearman <robert.shearman@att.com>
>> Signed-off-by: Chas Williams <chas3@att.com>
>> ---
>>   drivers/net/vhost/rte_eth_vhost.c | 15 +++++++++++++++
>>   1 file changed, 15 insertions(+)
>>
> 
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

It does not apply because a patch from Junjie seems to address the same
problem:

net/vhost: fix crash when creating vdev dynamically

Can you check dpdk-next-virtio/master and confirm this patch is no more
required?

Thanks,
Maxime

      reply	other threads:[~2018-04-11 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29 16:05 Chas Williams
2018-03-29 16:05 ` [dpdk-dev] [PATCH 2/2] net/vhost: insert/strip VLAN header in software Chas Williams
2018-04-11 14:52   ` Maxime Coquelin
2018-04-12  7:14   ` Maxime Coquelin
2018-05-08  1:31   ` Yao, Lei A
2018-04-11 14:46 ` [dpdk-dev] [PATCH 1/2] net/vhost: set the vq consistently Maxime Coquelin
2018-04-11 15:02   ` 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=d29aab4d-3222-ccb7-9c45-94c9d64be91a@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=3chas3@gmail.com \
    --cc=chas3@att.com \
    --cc=dev@dpdk.org \
    --cc=mtetsuyah@gmail.com \
    --cc=robert.shearman@att.com \
    --cc=stable@dpdk.org \
    --cc=yliu@fridaylinux.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).