From: "lhffjzh" <lhffjzh@126.com>
To: "'Thomas Monjalon'" <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, maintainers@dpdk.org
Subject: Re: [dpdk-dev] Why only rx queue "0" can receive network packet by i40e NIC
Date: Sat, 28 Feb 2015 09:47:50 +0800 [thread overview]
Message-ID: <046801d052f8$9090a530$b1b1ef90$@com> (raw)
In-Reply-To: <1566601.Xkl8jJDb44@xps13>
Hi Thomas,
Thanks very much for your reminder, you give me many help in this mail list.
The issue with detailed information just as below. but I don't know
who is the dpdk i40e maintainers? is maintainers@dpdk.org?
Hardware list:
2 i40e 40G NICs
Xeon E5-2670 v2(10 cores)
32G memory
I loopback 2 i40e NICs by QSFP cable, one NIC send UDP network packet by
DPDK,
and another for receiving. I bind 4 processor's logical cores with 4 rx
queue
"0,1,2,3" on receiving NIC, when I start to send packet, only rx queue "0"
can receive
the UDP packet, the others queue always receive nothing. but it is work well
on ixgbe
10G NICs, I can receive network packet from all rx queues. does anyone
kindly know why?
Regards,
Haifeng
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Friday, February 27, 2015 6:55 PM
To: lhffjzh
Cc: dev@dpdk.org
Subject: Re: Why only rx queue "0" can receive network packet by i40e NIC
2015-02-27 16:47, lhffjzh:
> Hi All,
>
> We use 4 cores loop 4 rx queues on one i40e port, but only rx queue "0"
can
> receive network packet, do anyone kindly know why? BTW, all of network
> packet has same destination ip address but has more than 200 different
> source ip address.
It's possible that you don't have any answer for 2 reasons:
- you replied in a thread dedicated to Cisco enic questions
- you didn't describe your usage enough to understand your problem
I suggest to use the button "new email" instead of "reply all" to
start a new question with enough details.
Did you noticed you put some Cisco guys in CC instead of putting the
Intel responsible for i40e (see MAINTAINERS file)?
next prev parent reply other threads:[~2015-02-28 2:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 17:26 [dpdk-dev] [PATCH v6 0/6] enicpmd: Cisco Systems Inc. VIC Ethernet PMD Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 1/6] enicpmd: License text Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 2/6] enicpmd: Makefile Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 3/6] enicpmd: VNIC common code partially shared with ENIC kernel mode driver Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 4/6] enicpmd: pmd specific code Sujith Sankar
2014-11-27 14:49 ` Wodkowski, PawelX
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 5/6] enicpmd: DPDK-ENIC PMD interface Sujith Sankar
2014-12-29 8:15 ` Wu, Jingjing
2014-12-30 4:45 ` Sujith Sankar (ssujith)
2015-01-06 9:41 ` Thomas Monjalon
2015-01-30 8:53 ` Wu, Jingjing
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 6/6] enicpmd: DPDK changes for accommodating ENIC PMD Sujith Sankar
2014-11-25 19:51 ` [dpdk-dev] [PATCH v6 0/6] enicpmd: Cisco Systems Inc. VIC Ethernet PMD David Marchand
2014-11-26 22:11 ` Thomas Monjalon
2014-11-27 4:27 ` Sujith Sankar (ssujith)
2014-11-27 15:31 ` Thomas Monjalon
2015-01-20 11:25 ` David Marchand
2015-01-21 5:03 ` Sujith Sankar (ssujith)
2015-02-26 11:49 ` Thomas Monjalon
2015-02-26 13:08 ` Wiles, Keith
2015-02-27 8:09 ` Sujith Sankar (ssujith)
2015-02-27 8:47 ` [dpdk-dev] Why only rx queue "0" can receive network packet by i40e NIC lhffjzh
2015-02-27 9:03 ` lhffjzh
2015-02-27 10:55 ` Thomas Monjalon
2015-02-28 1:47 ` lhffjzh [this message]
2015-02-28 3:17 ` Zhang, Helin
2015-02-28 4:33 ` lhffjzh
2015-02-28 14:33 ` Zhang, Helin
2015-07-23 0:47 ` Jeff Venable, Sr.
2015-07-23 0:56 ` Zhang, Helin
2015-07-30 1:58 ` Jeff Venable, Sr.
2015-07-31 15:35 ` Zhang, Helin
2015-02-27 10:46 ` [dpdk-dev] [PATCH v6 0/6] enicpmd: Cisco Systems Inc. VIC Ethernet PMD Thomas Monjalon
2015-03-11 9:05 ` Sujith Sankar (ssujith)
2015-05-11 9:25 ` Thomas Monjalon
2014-11-25 20:11 ` Neil Horman
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='046801d052f8$9090a530$b1b1ef90$@com' \
--to=lhffjzh@126.com \
--cc=dev@dpdk.org \
--cc=maintainers@dpdk.org \
--cc=thomas.monjalon@6wind.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).