DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [Bug 287] netvsc PMD/dpdk/azure: Driver lockup with multi-queue configuration
Date: Thu, 30 May 2019 09:05:44 -0700	[thread overview]
Message-ID: <20190530090544.32dcde9b@hermes.lan> (raw)
In-Reply-To: <bug-287-3@http.bugs.dpdk.org/>

On Thu, 30 May 2019 00:10:21 +0000
bugzilla@dpdk.org wrote:

> https://bugs.dpdk.org/show_bug.cgi?id=287
> 
>             Bug ID: 287
>            Summary: netvsc PMD/dpdk/azure: Driver lockup with multi-queue
>                     configuration
>            Product: DPDK
>            Version: 18.11
>           Hardware: x86
>                 OS: Linux
>             Status: CONFIRMED
>           Severity: normal
>           Priority: Normal
>          Component: ethdev
>           Assignee: dev@dpdk.org
>           Reporter: mohsinmazhar_shaikh@trendmicro.com
>   Target Milestone: ---
> 
> I am running an app using dpdk 18.11 netvsc PMD
> (https://doc.dpdk.org/guides/nics/netvsc.html) on "Ubuntu 18.04 LTS" VM on
> azure running kernel 4.18.0-1018
> (https://launchpad.net/ubuntu/+source/linux-azure/4.18.0-1018.18). The app uses
> multi-queue with 2 cores doing RX/TX. The lockup only occurs when doing a
> connections/second test i.e. exercising the netvsc interface. When the lockup
> occurs the netvsc interface and it's corresponding mellanox slave both can't
> rx/tx packets.
> 

Thanks for the report, busy this week, may have time to address it next week.


      reply	other threads:[~2019-05-30 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  0:10 bugzilla
2019-05-30 16:05 ` Stephen Hemminger [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=20190530090544.32dcde9b@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=dev@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).