From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 63] AWS ENA driver does not work with zero rx queues.
Date: Thu, 21 Jun 2018 11:06:17 +0000 [thread overview]
Message-ID: <bug-63-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=63
Bug ID: 63
Summary: AWS ENA driver does not work with zero rx queues.
Product: DPDK
Version: 18.02
Hardware: All
OS: Other
Status: CONFIRMED
Severity: major
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: daria.kolistratova@intel.com
Target Milestone: ---
(Program received signal SIGFPE, Arithmetic exception.) which was caused by:
0x00000000006f703c in ena_rss_init_default (adapter=0x7fffef399200)
at
/home/ec2-user/projects/src/github.com/intel-go/nff-go/dpdk/dpdk-18.02/drivers/net/ena/ena_ethdev.c:571
571 val = i % nb_rx_queues;
nb_rx_queues is 0, cause our application does not receive and we do not use rx
queues.
After fix of SIGFPE, we cant init port cause ena_com_ind_tbl_convert_to_device
function returns error at line:
(if (io_sq->direction != ENA_COM_IO_QUEUE_DIRECTION_RX)
return ENA_COM_INVAL;)
cause place for rx queue is not initialized and 0 means tx queue.
Application may have no rx queues, please look at this case.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-06-21 11:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-63-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.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).