From: Mohammed Gamal <mmorsy@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Mohammed Gamal <mgamal@redhat.com>,
dev@dpdk.org, maxime coquelin <maxime.coquelin@redhat.com>,
Yuhui Jiang <yujiang@redhat.com>, Wei Shi <wshi@redhat.com>
Subject: Re: [dpdk-dev] Problems running netvsc multiq
Date: Fri, 30 Nov 2018 14:06:52 -0500 (EST) [thread overview]
Message-ID: <1879110132.59852748.1543604812639.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20181130102756.41332fc2@xeon-e3>
----- Stephen Hemminger <stephen@networkplumber.org> wrote:
> On Fri, 30 Nov 2018 12:04:41 +0100
> Mohammed Gamal <mgamal@redhat.com> wrote:
>
> > Hi All,
> > I am having the following errors when I run testpmd with the netvsc
> > driver and --txq 2 and --rxq 2 options:
> >
> > testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=155456,
> > size=2176, socket=0
> > testpmd: preferred mempool ops selected: ring_mp_mc
> > Configuring Port 0 (socket 0)
> > hn_dev_configure(): >>
> > hn_rndis_link_status(): link status 0x40020006
> > hn_subchan_configure(): open 1 subchannels
> > vmbus_uio_get_subchan(): invalid subchannel id 0
> > hn_subchan_configure(): open subchannel failed: -5
> > hn_dev_configure(): subchannel configuration failed
> > Port0 dev_configure = -5
> > hn_dev_rx_queue_release(): >>
> > hn_dev_rx_queue_release(): >>
> > hn_dev_tx_queue_release(): >>
> > hn_dev_tx_queue_release(): >>
> > Fail to configure port 0
> > EAL: Error - exiting with code: 1
> > Cause: Start ports failed
> >
> > Multiq support was enabled and kernel module was loaded. The full
> > command line was:
> > ./testpmd -l 0-1 -n 2 --log-level=8 --log-level='pmd.*,8' --log-
> > level='bus.vmbus,8' -- --port-topology=chained --forward-mode=rxonly --
> > stats-period 1 --eth-peer=0,00:15:5d:1e:20:c0 --txq 2 --rxq 2
> >
> > I am running latest upstream kernel from the Linus tree and latest DPDK
> > upstream from git.dpdk.org.
> >
> > Could you also reproduce this? If not, what could I be misssing?
> >
> > Regards,
> > Mohammed
>
> Investigating now.
> Does single queue work for you?
Yes it does.
next prev parent reply other threads:[~2018-11-30 19:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 11:04 Mohammed Gamal
2018-11-30 18:27 ` Stephen Hemminger
2018-11-30 19:06 ` Mohammed Gamal [this message]
2018-12-04 16:48 ` Stephen Hemminger
2018-12-04 16:56 ` Mohammed Gamal
2018-12-05 22:12 ` Stephen Hemminger
2018-12-05 22:32 ` Stephen Hemminger
2018-12-07 11:15 ` Mohammed Gamal
2018-12-07 17:31 ` Stephen Hemminger
2018-12-07 19:18 ` Stephen Hemminger
2018-12-08 8:10 ` Mohammed Gamal
2018-11-30 20:24 ` [dpdk-dev] [PATCH] bus/vmbus: fix race in sub channel creation Stephen Hemminger
2018-12-03 6:02 ` Mohammed Gamal
2018-12-03 16:48 ` Stephen Hemminger
2018-12-04 11:59 ` Mohammed Gamal
2018-12-05 22:11 ` [dpdk-dev] [PATCH v2 1/4] " Stephen Hemminger
2018-12-05 22:11 ` [dpdk-dev] [PATCH v2 2/4] net/netvsc: enable SR-IOV Stephen Hemminger
2018-12-05 22:11 ` [dpdk-dev] [PATCH v2 3/4] net/netvsc: disable multi-queue on older servers Stephen Hemminger
2018-12-05 22:11 ` [dpdk-dev] [PATCH v2 4/4] bus/vmbus: debug subchannel setup Stephen Hemminger
2018-12-19 2:02 ` [dpdk-dev] [PATCH v2 1/4] bus/vmbus: fix race in sub channel creation Thomas Monjalon
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=1879110132.59852748.1543604812639.JavaMail.zimbra@redhat.com \
--to=mmorsy@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=mgamal@redhat.com \
--cc=stephen@networkplumber.org \
--cc=wshi@redhat.com \
--cc=yujiang@redhat.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).