DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: lhffjzh <lhffjzh@126.com>, 'Thomas Monjalon' <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"maintainers@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 14:33:34 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A80D97C@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <049801d0530f$b866bce0$293436a0$@com>

Good to know that!

> -----Original Message-----
> From: lhffjzh [mailto:lhffjzh@126.com]
> Sent: Saturday, February 28, 2015 12:34 PM
> To: Zhang, Helin; 'Thomas Monjalon'
> Cc: dev@dpdk.org; maintainers@dpdk.org
> Subject: RE: [dpdk-dev] Why only rx queue "0" can receive network packet by
> i40e NIC
> 
> Hi Helin,
> 
> Thanks a lot for your great help, all of rx queue received network packet after I
> update rss_hf from "ETH_RSS_IP" to " ETH_RSS_PROTO_MASK ".
> 
> static struct rte_eth_conf port_conf = {
>     .rxmode = {
>         .mq_mode        = ETH_MQ_RX_RSS,
>         .max_rx_pkt_len = ETHER_MAX_LEN,
>         .split_hdr_size = 0,
>         .header_split   = 0, /**< Header Split disabled */
>         .hw_ip_checksum = 1, /**< IP checksum offload enabled */
>         .hw_vlan_filter = 0, /**< VLAN filtering disabled */
>         .jumbo_frame    = 0, /**< Jumbo Frame Support disabled */
>         .hw_strip_crc   = 0, /**< CRC stripped by hardware */
>     },
>     .rx_adv_conf = {
>         .rss_conf = {
>             .rss_key = NULL,
>             .rss_hf = ETH_RSS_PROTO_MASK,
>         },
>     },
>     .txmode = {
>         .mq_mode = ETH_MQ_TX_NONE,
>     },
>     .fdir_conf.mode = RTE_FDIR_MODE_SIGNATURE, };
> 
> 
> Regards,
> Haifeng
> 
> -----Original Message-----
> From: Zhang, Helin [mailto:helin.zhang@intel.com]
> Sent: Saturday, February 28, 2015 11:18 AM
> To: lhffjzh; 'Thomas Monjalon'
> Cc: dev@dpdk.org; maintainers@dpdk.org
> Subject: RE: [dpdk-dev] Why only rx queue "0" can receive network packet by
> i40e NIC
> 
> Hi Haifeng
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of lhffjzh
> > Sent: Saturday, February 28, 2015 9:48 AM
> > To: 'Thomas Monjalon'
> > Cc: dev@dpdk.org; maintainers@dpdk.org
> > Subject: Re: [dpdk-dev] Why only rx queue "0" can receive network
> > packet
> by
> > i40e NIC
> >
> > 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?
> Could you help to list the DPDK version you are using now?
> Two possible reasons:
> 1. UDP rss is not enabled on your board correctly.
> 	I40e has different rss flags from ixgbe, so I am wondering if you use it
> correctly.
> 	In addition, this will be unified from 2.0. So I care about the DPDK version.
> 2. The UDP stream is occasionally hit the hash key of queue 0.
> 	You'd better to try to send your UDP stream with random 5-tuples, to get
> the
> 	hash value hit different queues randomly.
> 
> Regards,
> Helin
> 
> >
> >
> > 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)?
> >
> 

  reply	other threads:[~2015-02-28 14:33 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
2015-02-28  3:17                         ` Zhang, Helin
2015-02-28  4:33                           ` lhffjzh
2015-02-28 14:33                             ` Zhang, Helin [this message]
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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A80D97C@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=lhffjzh@126.com \
    --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).